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

Zapier Trigger Function Executing Twice

  • October 21, 2024
  • 8 replies
  • 117 views
S

Hey everyone,

I’ve developed a CRM platform and integrated it with Zapier. I built a simple app with a trigger called "Add Contact into CRM." Right now, I’m using a Google Form as the action. When someone submits the form, Zapier sends the data to our CRM, and we successfully receive and save it in our database.
 

However, there’s an issue. After Zapier sends the data to us, it also gets an error back from our system saying, "This email is already associated with another contact." This error occurs because our system doesn't allow the same email to be saved twice. It seems like Zapier is triggering the function twice, so the first request is processed and saved correctly, but the second one is denied due to the duplicate email, and that’s what’s causing the error.

Has anyone else run into this, or do you have any ideas on how to stop the trigger from firing twice?

Thanks in advance for any help!

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

8 replies

Troy Tessalone
Zapier Orchestrator & Solution Partner
Forum|alt.badge.img+14
  • Troy TessaloneZapier Orchestrator & Solution Partner
  • Zapier Orchestrator & Solution Partner
  • October 21, 2024

Hi @Shamim 

To help you troubleshoot, check your Zap Runs history details to see the DATA IN/OUT for each Zap step: https://zapier.com/app/history/

⚡ Troy Tessalone - AutomationAce.com | Platinum Zapier Solution Partner | #1 Zapier Community Contributor
S
JammerS
Forum|alt.badge.img+6
  • JammerSZapier Staff
  • Zapier Staff
  • October 22, 2024

Hi @Shamim,

 

Keep us on the loop for this one, so we can further troubleshoot the issue that you’re encountering. Thank you.

S
S
  • Shamim
  • Author
  • New
  • October 28, 2024

Hi @Shamim 

To help you troubleshoot, check your Zap Runs history details to see the DATA IN/OUT for each Zap step: https://zapier.com/app/history/

Hi Troy!
Thanks for your reply. I looked into the history. It is showing two things in the history as mentioned in the screenshot. Can you predict (from the screenshot) if the action is executed twice?
 

 

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

Hi @Shamim,

It looks like the Zap executed once. You can learn more about that here: https://help.zapier.com/hc/en-us/articles/8496291148685-View-and-manage-your-Zap-history#h_01HD2JH786JPVZ5533T7Y4ANNC

Regarding the error that you’re getting, could you please let me know the app that you’re using? This will help me look closer at the issue.

Thanks!

S
S
  • Shamim
  • Author
  • New
  • October 29, 2024

Hi @Shamim,

It looks like the Zap executed once. You can learn more about that here: https://help.zapier.com/hc/en-us/articles/8496291148685-View-and-manage-your-Zap-history#h_01HD2JH786JPVZ5533T7Y4ANNC

Regarding the error that you’re getting, could you please let me know the app that you’re using? This will help me look closer at the issue.

Thanks!

Hi Ken.a,
Thanks for your reply. I have shared the information in personal message to you. Sharing here the details as well.

App: Calystapro
Action: Add New Contact

 



​​​​

Regards,

Shamim Hossain

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

Hi @Shamim,

Thanks for the update here.

It looks like your Zap is not executing twice. However, the Calystapro is running into an error of "The provided email address is already associated with another contact.". Could you please try submitting a form response in Google Forms and ensure that you are using a unique email address that hasn’t been entered in Calystapro before?

I'll be keeping an eye out for your response!

S
  • Shamim
  • Author
  • New
  • October 30, 2024

Hi @Shamim,

Thanks for the update here.

It looks like your Zap is not executing twice. However, the Calystapro is running into an error of "The provided email address is already associated with another contact.". Could you please try submitting a form response in Google Forms and ensure that you are using a unique email address that hasn’t been entered in Calystapro before?

I'll be keeping an eye out for your response!

Hi Ken.a,

I just have submitted a new form response (google form) with a completely new email address (the.unique.email.is.here.2024@example.com). The contact (new lead) is also saved in my CRM database (I just checked it out) but at the same time Zapier gives me the same error - “The provided email address is already associated with another contact”, which is possible only when the same actions can be happened twice.

Regards,

Shamim

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

Hi @Shamim,

Thanks for giving that a try.

If you’re certain that the Zap is creating duplicate actions I would recommend sending a screenshot of the Zap runs in the Zap History that shows the timestamp of the Zap run. Here’s an example screenshot:

d91f84dc806273b9f4910c60b7fdad85.png
(view larger)

This will help me take a closer look at the issue. Thanks!

Terms & ConditionsAccessibility statement