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.

Hey all, we’ve had multiple Copper <> Zapier integrations running for a couple of years now without fault. However in the past couple of months, one of our Zaps has started firing like crazy, causing us to go over our Zap task limit incredibly quickly.

 

The Zap currently fires whenever an Opportunity is updated, and goes through 10 steps to update a similar database in Smartsheet. Whenever a small change is made to the Opportunity (such as stage or revenue change), it is firing Zapier at least 5 times, sometimes 15+, each a couple of seconds apart. I’ve looked through but can’t work out why this is happening — the Copper information is identical from what I can see each time.

 

Any help?

Hi @jameshutchinson 

The trigger is supposed to trigger everytime something is changed in opportunity. However, it shouldn’t run several times for a single update unless their is additional fields updated by other automation. You should contact Copper support for this issue, it is called Webhook.

 

You can also try adding filter after the trigger, that will help you consume less tasks. Also check if you can use one of these triggers instead of update opportunity trigger:

 

Hi @jameshutchinson 

The trigger is supposed to trigger everytime something is changed in opportunity. However, it shouldn’t run several times for a single update unless their is additional fields updated by other automation. You should contact Copper support for this issue, it is called Webhook.

 

You can also try adding filter after the trigger, that will help you consume less tasks. Also check if you can use one of these triggers instead of update opportunity trigger:

 

Cheers, I’ve changed the trigger to Opportunity Stage, and will test to see if that reduces the triggers first.

Hi there, @jameshutchinson! 👋

I just wanted to pop in here to check how you’re getting on with that Updated Opportunity Stage trigger? Has it helped to prevent the Zap from triggering too much? Keen to make sure you’re all set here!

Reply


Terms & Conditions