I built a custom Zapier integration that includes a trigger for collecting new customer data from an external API. The trigger works perfectly when I connect it to a single service like ActiveCampaign or ConvertKit. However, I’m running into an issue when I try to set up multiple Zaps using the same trigger. I created separate Zaps to send the customer data to ActiveCampaign, ConvertKit, and GetResponse at the same time. The problem is that only one of these Zaps actually receives the data when the trigger fires. For instance, ActiveCampaign gets the new contact, but ConvertKit and GetResponse don’t receive anything. My polling endpoint is functioning correctly and returns the expected data format. I can’t figure out why the trigger doesn’t fire across all three Zaps simultaneously. There are no error messages or warnings in any of the Zap histories. Has anyone experienced this type of behavior with custom Zapier triggers? Is there a specific configuration or setting I might be missing that would allow multiple Zaps to use the same trigger data?
check if ur mixing instant and polling triggers - that combo causes weird firing issues. zapier also caches trigger results between zaps sometimes, so try disabling one zap temporarily to see if the others start working. could be rate limiting on their end instead of ur api.
Classic Zapier webhook deduplication issue. When multiple Zaps use the same trigger, Zapier’s deduplication messes things up and stops all instances from firing.
Zapier compares trigger data across Zaps to prevent duplicates. If the data looks identical, it’ll only fire one Zap and ignore the rest.
I hit this exact problem last year syncing customer data to multiple CRMs. Ended up ditching Zapier completely for Latenode.
Latenode lets you build one scenario that pulls from your API and pushes to all three services at once. No deduplication headaches, no juggling multiple Zaps, way more reliable.
Better error handling too - you can actually see what’s happening at each step. Set up similar workflows in 10 minutes that would’ve taken hours to debug in Zapier.
Cheaper when you’re doing multiple actions per trigger like this.
I’ve hit this exact issue with custom integrations. Zapier throttles API calls when multiple Zaps use the same trigger endpoint - basically one Zap polls and the others get held back so your server doesn’t get hammered. Switch to webhooks if you can. Each Zap gets its own webhook URL, so they all fire instantly without competing. If webhooks won’t work, stagger your polling - give each Zap different schedules so they’re not fighting over the same API window. Here’s a hack that works: create separate trigger endpoints in your code that return identical data but have different URLs. Zapier thinks they’re independent triggers instead of shared resources.
Had this same headache six months ago with a custom integration. The problem’s definitely Zapier’s trigger deduplication, but your polling endpoint needs to return unique IDs for each record. Here’s what fixed it: make sure every data object from your API has a truly unique ID field. Even when customer data looks identical, Zapier needs something like a timestamp or incremental ID to treat each trigger as separate. Also check your trigger’s deduplication field in your integration code. If you don’t explicitly define what makes each record unique, Zapier compares the entire payload - that’s why you’re seeing this behavior. Try adding a millisecond timestamp to each record or combine customer ID with current datetime. This’ll let all three Zaps fire independently even with identical customer data.