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.

Hi all! I have noticed that when I trigger a task for my Seamless.AI to Zapier Integration, I seem to be getting many errors that stop the action. These errors are due to Error : Invalid data for the field Phone. Detail : expected_data_type phoneI fugured out that this is occuring because Seamless.AI often takes time to populate the phone number and email information on their side, sometimes up to a minute or so. 

So, essentially, this Zap is being triggered too early so the field that should have a phone number in it, instead says “Researching...” and causes an error.

Is there any way to delay the Zap from triggering?

@jsalser Does Seamless.AI have a Search that is equivelant to the trigger?  If so you could

  1. Add a Dealy after the trigger to allow time for Seamless.AI to populate the phone number and email information on their side
  2. Add a Search to re-read the data using the ID from the trigger.

For example,

Trigger: New contact created. 

Action: Delay 5 minutes

Search: Find contact

Actions: any other steps required for the workflow.

 

@Mercology Thanks! I’ll take a look at that!

Hi @jsalser!

Just checking in with you to see if you’d managed to get things working using the suggestion above (or in some other way), or whether you could still use some help here. Please let us know :)

@nicksimard thanks for checking in... But tbh we scratched this project. It was too problem ridden and glitch. Figured out that issue was not with zapier, but rather with seamless. 

Terms & Conditions