Connecting Microsoft Teams to N8N issue (invalid token)

Questions
1

Describe the problem/error/question

I’ve already tried nearly every method and followed every documentation regarding connecting Teams to N8n and just cannot resolve this issue.

Firstly, I am using n8n cloud (NOT self hosted), and despite the credentials having been successfully connected, my teams trigger nodes (And other Teams related nodes) will just not run. It will either give me an Invalid Token error or 403 error, which I know is related to authentication. However, all credentials are correct and I am also subscribed to Microsoft 365 personal plan. And yes, I’ve tried the various things I need to do on Azure portal (registering an app and setting up the API permissions as well), however as this is on n8n cloud, this should not be necessary. I just do not know what is wrong so if someone could assist that would be greatly appreciated… :frowning:

What is the error message (if any)?

Problem running workflow

Invalid Token

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: 1.120.3
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): n8n cloud
  • Operating system: Windows 11 Home x64
2 Likes
2

I’m facing the issue, any update on that?

1 Like
3

my teams was working fine (never through azure) until recently now authentication is not working telling me invalid client :slight_smile:

Trying to re-authenticate opens a teams window just to tell me the below

{“error”:“invalid_client”,“error_description”:“AADSTS7000222: The provided client secret keys for app ‘aad843ca-42a7-4219-a3f9-91bcf621d795’ are expired. Visit the Azure portal to create new keys for your app: How to register an app in Microsoft Entra ID - Microsoft identity platform | Microsoft Learn , or consider using certificate credentials for added security: Microsoft identity platform certificate credentials - Microsoft identity platform | Microsoft Learn . Trace ID: acd61d8b-8479-4b32-b7f5-f2df96223f00 Correlation ID: — Timestamp: 2025-12-06 02:09:07Z”,“error_codes”:[7000222],“timestamp”:“2025-12-06 02:09:07Z”,“trace_id”:“—”,“correlation_id”:“bb14639a-9506-4a6e-b65d-2ae7220ba22f”,“error_uri”:“https://login.microsoftonline.com/error?code=7000222”}

4

We were running into the same issue. Without knowing exactly why, the old connection just wouldnt’t “reconnect“. What did work was creating a new connection (Microsoft Outlook OAuth) and replacing our previously failing connection.

5

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