n8n has two built-in Microsoft Teams nodes: the Microsoft Teams node, which works with channels, channel messages, chats, chat members, chat messages, online meetings, tasks and activity notifications, and the Microsoft Teams Trigger, which starts a workflow on new channels, messages, chats or team members. A few community nodes add a least-privilege variant and Teams bots built on Microsoft’s Bot Framework. This guide covers the built-in nodes and their credentials (from n8n’s documentation) and the Teams community packages on our hub (from the descriptions and READMEs their authors publish on npm, and our own download data).
Quick comparison
| Built-in Teams nodes | Teams community nodes | |
|---|---|---|
| Covers | Channels, messages, chats, chat members, online meetings, tasks, activity notifications, plus a trigger | Least-privilege scopes, Bot Framework bots that receive and send messages |
| Credential | Teams OAuth2, Microsoft OAuth2 (Graph) or Service Principal (App-Only) | OAuth2 with editable scopes, or a Bot Framework app registration |
| Comes with n8n | Yes | No, installed as a community package |
| n8n Cloud | Available | Only packages that n8n has verified |
What the built-in Microsoft Teams node can do
- Activity Notification: Send
- Channel: Create, Delete, Get, Get Many, Update
- Channel Message: Create, Delete, Get, Get Many, Get Many Replies, Reply, Undo Delete
- Chat: Create, Get, Get Many
- Chat Member: Add, Get Many, Remove
- Chat Message: Create, Delete, Get, Get Many, Send and Wait for Response, Undo Delete
- Online Meeting: Create, Create or Get, Delete, Get, Update
- Task: Create, Delete, Get, Get Many, Update
Several of these are recent: per the documentation, Chat Member, Online Meeting and some Channel Message operations arrived in n8n 2.39.0, the Chat resource in 2.41.0 and Activity Notification in 2.42.0, so check your n8n version if you don’t see one. Messages can mention users and team tags.
The Microsoft Teams Trigger
The trigger has five events: New Channel, New Channel Message, New Chat, New Chat Message and New Team Member. It works through Microsoft Graph change notification subscriptions, which Microsoft Graph expires after three days. The documentation says automatic renewal arrived in n8n 2.45.1; before that, the trigger stops receiving events about three days after you publish the workflow, and you unpublish and publish it again. Renewal also needs your n8n instance to be reachable, and a failed renewal shows no failed execution, only log messages such as Microsoft Teams Trigger: failed to renew subscription.
Credentials
From version 2 of the node, Authentication offers three options:
- Teams OAuth2 (default): its default scopes cover every resource of the node.
- Microsoft OAuth2 (Graph): a generic Microsoft Graph credential you can reuse across Microsoft nodes; you grant it the scopes the Teams node needs.
- Service Principal (App-Only): app-only access through a Microsoft Entra app registration, with no signed-in user. Channels, online meetings and tasks work; chats, chat members and chat messages don’t, and channel messages can be read but not created or replied to.
On n8n Cloud, the documentation says a Microsoft Entra administrator has to approve the managed Teams OAuth2 credential for your organization before other users can connect it. If you connected a Teams OAuth2 credential before n8n 2.39.0, reconnect it so it picks up the online meetings scope. Setup steps are in n8n’s Microsoft credentials page.
Microsoft Teams community nodes
Our Microsoft Teams hub lists the Teams packages that pass our quality rule (weekly npm downloads as of 28 October 2026):
| Package | Weekly downloads | Latest version | Author’s description |
|---|---|---|---|
| n8n-nodes-msteams-lite | 32 | 0.2.2 (23 February 2026) | Microsoft Teams (Lite) nodes with a minimal permission set |
| @joshuanode/n8n-nodes-teamsbot | 21 | 0.0.4 (29 March 2026) | Microsoft Teams Bot Framework nodes, single-tenant ready |
| n8n-nodes-msteams-bot | 19 | 0.3.1 (11 March 2026) | Microsoft Teams Bot Framework: send, receive and manage messages |
Versions and dates come from the npm registry.
n8n-nodes-msteams-lite
Its README says the built-in node covers more operations, while this one focuses on permissions: an editable scope field so you request only the scopes you use, and a narrower team member scope that can’t grant the owner role. Its trigger adds Fetch Full Message, which returns the message content instead of only notification metadata, and Ignore Own Messages, which drops messages from the connected user so a workflow doesn’t trigger itself. It covers creating one-on-one and group chats, creating, getting and listing chat messages, including replies into an existing chat, and creating channels.
Teams bots: n8n-nodes-msteams-bot and @joshuanode/n8n-nodes-teamsbot
Both work with Microsoft’s Bot Framework rather than Microsoft Graph, so messages come from a bot. Each has a trigger that receives Bot Framework activities through a webhook and an action node that sends them. n8n-nodes-msteams-bot’s README lists messages in one-on-one chats, channels (when the bot is mentioned) and group chats, sending, updating and deleting messages, typing indicators, creating conversations and getting members, with bot loop prevention. @joshuanode/n8n-nodes-teamsbot is designed for single-tenant bot registrations.
Check each node page here for the latest release and, where it has one, its GitHub repository for open issues before you build on a package.
How to choose
- Post to channels and chats, manage meetings or tasks: the built-in Microsoft Teams node.
- React to new messages, chats or team members: the built-in trigger, on n8n 2.45.1 or newer for automatic subscription renewal.
- Your organization requires the smallest set of permissions: n8n-nodes-msteams-lite.
- A chatbot that people message directly in Teams: n8n-nodes-msteams-bot or @joshuanode/n8n-nodes-teamsbot.
- Anything else in Microsoft Graph: the HTTP Request node with your Microsoft credential.
To install a package on a self-hosted instance, an owner or admin enters its npm name in Settings > Community Nodes; full steps are in How to Install n8n Community Nodes. On n8n Cloud only verified community nodes can be installed, see Verified vs Unverified n8n Community Nodes. Similar guides: Slack and Word and DOCX.
FAQ
Does n8n have a Microsoft Teams node?
Yes, two: the Microsoft Teams node for channels, messages, chats, meetings, tasks and activity notifications, and the Microsoft Teams Trigger.
Why did my Microsoft Teams Trigger stop after a few days?
Microsoft Graph expires Teams subscriptions after three days. According to n8n’s documentation, the trigger renews them automatically from n8n 2.45.1; on older versions it stops about three days after you publish the workflow, and you unpublish and publish it again. Renewal also needs n8n to be reachable.
Can I use a service principal with the Teams node?
Yes, with the Service Principal (App-Only) credential, but chats, chat members and chat messages need a signed-in user and aren’t available with it.
What is the most used Microsoft Teams community node?
n8n-nodes-msteams-lite, with 32 weekly npm downloads on 28 October 2026.
