Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Question

Zap routing LinkedIn lead form data to the wrong path despite phone number containing +1

  • October 13, 2023
  • 1 reply
  • 33 views
James Blackwell

Hey guys, I’m facing a really weird issue. I’ve routing LinkedIn Lead form data into GHL through paths in Zapier. 

It’s very basic statements that IF phone number does not contain “+1” don’t send it to the US account. But the zap is still going into that path when the field clearly contains +1 in the number. See screenshots attached. 

2 Attachments
This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

1 reply

ken.a
Forum|alt.badge.img+6
  • ken.aZapier Staff
  • Zapier Staff
  • October 16, 2023

Hi there @James Blackwell,

Welcome to the Community! 🎉

Taking a look at your screenshots, it seems that the data mapped to the first dropdown menu in the Filter step is currently linked to the “Yes” data. This could be the reason it's taking the wrong path.

If you initially mapped the first dropdown menu in the Filter step from the trigger step, I'd recommend loading a fresh sample of data and remapping that field with the correct phone number data.

Hopefully, this helps. 😊

Terms & ConditionsAccessibility statement