Help Please! Infinite ticket loop when using Teams ↔ Zendesk bidirectional workflows!

[Progressive_AI]

Hi everyone,
I’m working on a bidirectional integration between Microsoft Teams and Zendesk in n8n.
I have 3 separate workflows:
Teams → Zendesk — creates a Zendesk ticket when a new message is posted in a Teams channel.
Teams comment → Zendesk update — if someone replies in an existing Teams thread, the corresponding Zendesk ticket is updated with that comment.
Zendesk → Teams — when there’s a new public comment in Zendesk, it’s posted back into the same Teams thread.
The problem is: when all three workflows are active at the same time, I get an infinite loop of ticket creation in Zendesk — they keep creating endlessly.
It seems like the updates from one side are triggering the reverse workflow and vice versa, creating duplicates and loops. I tried using IF conditions and filters to prevent this, but either I set them up wrong or it’s not enough.

Has anyone encountered a similar looping issue in bidirectional integrations?
What’s the best way in n8n to break the loop while still allowing updates in both directions?

If anyone is willing to help, please describe the solution as thoroughly and accurately as possible. I’m happy to pay a reasonable amount.

Describe the problem/error/question

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

• n8n version:
• Database (default: SQLite):
• n8n EXECUTIONS_PROCESS setting (default: own, main):
• Running n8n via (Docker, npm, n8n cloud, desktop app):
• Operating system:

[jabbson]

Hey @Progressive_AI hope all is good. Welcome to the community.

I believe this can be solved if you filter out the authors and differentiate bot replies vs human replies.

If a human replies in the thread - create a ticket
if a bot replies in the thread - don’t

So what you need to do is to introduce a conditional logic in your “Teams comment → Zendesk update” workflow where you check if the reply author’s name or id is of a bot or not. This should be enough, if this didn’t work, you probably did it wrong.

To test, I would create two comments - one by bot and one by human and see how the trigger output is different. This should give you a good idea of what to use for differentiation.