I’ve been noticing for a while that I have to unpublish and republish my workflow whenever a new subscription to the Teams Trigger has been made by n8n. It works for a very short while after the new subscription but after a while the Teams trigger just stops listening.
I’ve tried just selecting the chat ‘group’ and I have tried listening to the group by ID. But the same problem occurs on both. Which leads me to suspect the Teams Trigger either listens via an old subscription and doesnt refresh to the new subscription or the Teams trigger just breaks shortly after a new subscription.
Anyone had similar issues or have a working solution?
The trigger relies on Microsoft Graph webhook subscriptions, and if the subscription fails to renew or validate, n8n will still look “active“ but it actually stops receiving event. Republishing the workflow recreates the subscription, which is why it works again briefly.
Maybe you can check your n8n version, make sure you’re on the latest version.
Ensure your webhook url is stable, public, and HTTPS (no sleeping containers, expiring tunnels, or blocked validation requests)
If you using self-host, double check your reverse proxy isnt blocking or slowing down Microsoft’s validation call.
Helllo, thanks for the warm welcome and your reply.
I’m running a self hosted n8n and I’m on version 2.1.4 at the moment. This issue has been going on for a while on earlier versions aswell.
The Microsoft Teams Trigger node I’m using is on the latest version (1).
The Microsoft Teams Trigger node looks like its refreshing the subscription since my workflow is outputting an error (workflow doesnt expect a subscription output).
A while back i checked before i reactived the flow via https://graph.microsoft.com/v1.0/subscriptions and I saw a later expirydate for the Teams resource already. Which tells me it is renewing.
But just to be sure I’ll check this again when this error occurs and come back to this thread.
The Teams Trigger is not updating the subscription to a new date/time. I’ve made my own scheduled PATCH workflow now which updates the Teams subscriptions (to the channels/groups) automatically each night by +72 hours. This should resolve my issue.
