Hi @Commissionly
If you are noticing this when testing the Zap trigger manually, then try turning the Zap ON and testing, then check your Zap Runs: https://zapier.com/app/history/
Also, you can add a Filter as Step 2 of the Zap: https://zapier.com/apps/filter/help
Hi Troy
Why would the api call be different if I turned the Zap on? Do you send the call with different parameters when the Zap is turned on?
A filter would mean that the every movement of a salesforce opportunity into a different stage would be sent through to the Zap and would chew through the tasks in a few days.
The need fo the filter would also indicate that the original api call is not working correctly.
Is there a way to check the details of the api call that is being sent? If my settings are correct can this be tested by your support team? Do Salesforce maintain the integration or is this a homebrew built by Zapier?
Thanks
Hi @Commissionly
Sometimes the behavior of Zap steps can different when being manually tested vs when the Zap is turned ON.
Only Zap steps that successfully process count as Tasks.
Trigger steps do NOT count as Tasks.
So if a Filter is Step 2, and the triggered Zap run filters out, then it would use 0 Tasks.
I do not work at Zapier.
I don’t know which party maintains the Salesforce Zap app integration as that’s not publicly listed.
If you need deeper help, you can open a ticket with Zapier Support: https://zapier.com/app/get-help