Hi @rkumar 

Help us have more info by posting screenshots showing these:

• which Zap app trigger and event you are using
• how your Zap trigger step is configured in EDIT mode

Salesforce outbound message is the trigger event

From salesforce its firing only once 

@rkumar 

Were messages sent to multiple Contacts in a bulk action in Salesforce?

Open an individual Zap Run to see the DATA IN/OUT for each Zap step to help you troubleshoot: https://zapier.com/app/history/

Check if the data points have the same or different values.

@rkumar 

Help links for using the Salesforce New Outbound Message Zap trigger: https://help.zapier.com/hc/en-us/articles/8496020846605-Tips-and-tricks-with-Salesforce-triggers-and-actions

All zaps got same data and running at same time .. running more than 50 times for no reason 

@rkumar 

Zap trigger: Salesforce - New Outbound Message

Triggers when a new outbound message is received in Salesforce.

This is an instant triggered that is fired by Salesforce using webhooks.

Generally if there are Zap Runs with the same timestamp, then that means a bulk event happened in the origin app to trigger the Zap Runs at the same time.

You can troubleshoot by opening an individual Zap Run to see the DATA IN/OUT for each Zap step: https://zapier.com/app/history/

@rkumar 

You can try opening a ticket with Zapier Support for more troubleshooting: https://zapier.com/app/get-help

My Zap Json

Hi @rkumar 

Thanks for sharing that file, unfortunately we’re won’t be able to easily determine the issue based on a JSON export of your Zap. It’s better to send screenshots of the Zap’s setup (with any personal information like names, emails, addresses etc. obscured).

If it’s the same email message that the Zap is triggering for every time I’m wondering whether it could be a Zap Loop.  From your initial screenshot it looks as though there’s a Webhooks step in the Zap. So could it be that it’s that action that’s sending information back to Salesforce that’s then causing it to trigger the Zap? 

If that’s not the case, I think your best best will be to contact the Support team to have this investigated further. They’ll be able to dig into the logs for your Zap to better determine why it’s triggering unexpectedly.

Please do keep us updated on how you get on with this, very interested to know what the underlying cause is!

I was able to take support help and its resolved.. Issue was one of the step it was getting many records and zap was running for each record .  handled it by adding condition to get single record .

Though it does not sound correct behaviour but zapier handling multiple records differently