Microsoft Teams Node performance is poor when fetching channel messages

Feedback
1

Hi n8n community! :waving_hand:I’ve been enjoying n8n overall, but I’m experiencing some performance issues with the Microsoft Teams node that I’d like to get feedback on.

Issue Summary: When fetching channel messages using the Microsoft Teams node, I’m seeing inconsistent behavior based on channel age and message volume.

Scenarios tested:

  1. Old channel (3+ years) with limit: 100 → Gets stuck indefinitely, never completes

  2. Old channel (3+ years) with limit: 1 → Gets stuck indefinitely, never completes

  3. New channel with limit: 1 → Works perfectly

  4. New channel with “return all” → Works well (only ~3 messages)

Questions for the community:

  • Has anyone else experienced similar issues with the Microsoft Teams node on older channels?

  • Is this likely a limitation of the Microsoft Graph API v2, or could it be related to the n8n node implementation?

  • I noticed there don’t seem to be filtering options available - would date/time filters help mitigate this issue?

Technical context:

  • The problematic channel has been active for 3+ years

  • Issue occurs specifically when trying to limit results on high-volume, older channels

  • New channels work fine regardless of limit settings

Any insights, workarounds, or similar experiences would be greatly appreciated!

2

Never mind, found the problem myself. Just made a PR

3

Hey @dennypradipta, I feel you on the Microsoft Teams node acting up with older channels :persevering_face:. Sounds like the node might be choking on high-volume data from the Graph API, which can be sluggish with older channels due to how it paginates or handles large datasets. I’ve seen similar issues discussed on the n8n community where the Teams node takes forever (or stalls) when fetching from busy channels, but works fine for newer ones with less history :chart_decreasing:.

Try using an HTTP Request node to hit the Graph API directly (e.g., /teams/{teamId}/channels/{channelId}/messages?$top=1) with a date filter like $filter=lastModifiedDateTime gt 2022-01-01T00:00:00Z to limit the scope. This could bypass the node’s limitations and confirm if it’s an API issue. If it works, the node’s implementation might need tweaking. Check your API scopes too (needs ChannelMessage.Read.All). Anyone else hit this wall with Teams? :hammer_and_wrench: Share your fixes!

4

Yeah, currently I use the API way instead of the Microsoft Teams node. The DX sucks but hey, if it works it ain’t stupid :smiley: