Teams - Trigger on New Chat Message Timeout

We have an issue with trying to get our workflows to trigger when they rely on a Teams message being sent. We’ve confirmed that our connection is setup fine, and I can use n8n to push a message down to that chat, so it’s just the passive listening that doesn’t seem to be triggering.

The ‘workflow’ is just the single node:

Our n8n is on-prem and run through a docker instance, and we are on version 1.110.1. We have N8N_REINSTALL_MISSING_PACKAGES set to true, so we should have no outdated/missing packages. I can see there was a Github ticket about this, #17260, and it supposedly fixed this issue, but we’re still experiencing problems with timeouts each time we test listening with it.

We’ve granted the following credentials to our teams connection, and I have refreshed the connection on our test system:

ChannelMessage.Read.All
Chat.Read
Chat.ReadBasic
Chat.ReadWrite
Chat.ReadWrite.All
ChatMessage.Read
ChatMessage.Send
Group.ReadWrite.All

Mail.Read

offline_access

openid
Subscription.Read.All
Team.Read Basic.All
User.Read
User.ReadWrite.All

Is anyone else having this issue, and have they been able to resolve it?

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.