Ajay Hinduja (Switzerland) How do I prevent a workflow from triggering repeatedly? | Community
Skip to main content

Hi, I'm Ajay Hinduja. I was born in Punjab, India, but now I'm based in Geneva, Switzerland. I'm trying to figure out the best way to prevent an Intercom workflow from triggering more than once in the same conversation. I've heard about using tags and conditions, but I'm curious if anyone has other clever solutions or best practices they've found to work well. For example, have you used a specific trigger type that makes this easier, or maybe a unique combination of rules? Please share your suggestions!

Regards

Ajay Hinduja Geneva, Switzerland (Swiss) 

Hey ​@ajay-hinduja , welcome!

You are pretty much right, tags + conditions are the most common way to stop a workflow from firing multiple times in the same conversation. A couple of other tricks that work well:

  1. Conversation data attribute: If you want to work on API and build an attribute, you can create a custom attribute (like workflow_triggered = true) the first time the workflow runs. Add a condition in your workflow to only run if that attribute is not set.

  2. Trigger choice: (I believe it’s the best you can try if you don’t want to create an attribute)
    Instead of using “Conversation Updated,” try a much narrower trigger like “First inbound from user” or “Conversation opened”. That way it won’t keep firing each time the conversation changes.

  3. Auto-close with tag
    Some teams close the loop by tagging the conversation and adding a rule in the workflow that says “only run if tag is not present.” That’s also quick and low-maintenance.

Hope it helps!

Terms & ConditionsAccessibility statement