> For the complete documentation index, see [llms.txt](https://docs.n8n.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.n8n.io/integrations/builtin/trigger-nodes/n8n-nodes-base.microsoftteamstrigger.md).

# Microsoft Teams Trigger

Learn how to use the Microsoft Teams Trigger node in n8n. Follow technical documentation to integrate Microsoft Teams Trigger node into your workflows.

Use the Microsoft Teams Trigger node to respond to events in [Microsoft Teams](https://www.microsoft.com/en-us/microsoft-teams/group-chat-software) and integrate Microsoft Teams with other applications.

On this page, you'll find a list of events the Microsoft Teams Trigger node can respond to and links to more resources.

{% hint style="info" %}
**Credentials**

Refer to the [Microsoft credentials documentation](/integrations/builtin/credentials/microsoft.md) for authentication information for this node. This node also supports the [Microsoft Entra Service Principal credentials](/integrations/builtin/credentials/microsoftentraserviceprincipal.md) for app-only access with no signed-in user: select **Service Principal (App-Only)** in the **Authentication** dropdown.
{% endhint %}

{% hint style="info" %}
**Government Cloud Support**

If you're using a government cloud tenant (US Government, US Government DOD, or China), make sure to select the appropriate **Microsoft Graph API Base URL** in your Microsoft credentials configuration.
{% endhint %}

## Events <a href="#events" id="events"></a>

* **New Channel**
* **New Channel Message**
* **New Chat**
* **New Chat Message**
* **New Team Member**

## Required scopes

Each event subscribes to a Microsoft Graph resource and needs one of the delegated permissions in the table, least privileged first:

| Event                   | Delegated permission                               |
| ----------------------- | -------------------------------------------------- |
| **New Channel**         | `Channel.ReadBasic.All`                            |
| **New Channel Message** | `ChannelMessage.Read.All`                          |
| **New Chat**            | `Chat.ReadBasic`, `Chat.Read`, or `Chat.ReadWrite` |
| **New Chat Message**    | `Chat.Read` or `Chat.ReadWrite`                    |
| **New Team Member**     | `TeamMember.Read.All`                              |

Listing teams in the node needs `Team.ReadBasic.All`, and listing channels needs `Channel.ReadBasic.All`. `ChannelMessage.Read.All` and `TeamMember.Read.All` need admin consent from a Microsoft Entra administrator. The `Team`, `Channel`, and `Chat` permissions don't.

From n8n 2.45.0, the **Teams OAuth2** credential covers every event by default: `TeamMember.Read.All` is one of its [default scopes for Microsoft Teams](/integrations/builtin/credentials/microsoft.md#default-scopes-for-microsoft-teams).

The credential's default `User.Read.All` and `Group.ReadWrite.All` scopes are higher-privileged alternatives that also cover the team list, the channel list, and the **New Channel** subscription. The credential needs no extra grant for those. `User.Read.All` and `Group.ReadWrite.All` need admin consent.

A credential connected before n8n 2.45.0 requests `TeamMember.Read.All` when you reconnect it. A Microsoft Entra administrator must consent to the scope before you reconnect, or the sign-in fails. Refer to [New scopes need a new approval](/integrations/builtin/credentials/microsoft.md#new-scopes-need-a-new-approval) in the Microsoft credentials documentation for how an administrator approves it on n8n Cloud. If the credential uses **Custom Scopes**, add the scope to **Enabled Scopes** if it isn't there, then reconnect. Before n8n 2.45.0, turn on **Custom Scopes** (available from n8n 2.6.0) in the credential, add the scope to **Enabled Scopes**, and reconnect.

With the **Microsoft OAuth2 (Graph)** credential, enter the scopes in the credential's **Scope** field. Include `openid offline_access` so the credential can refresh its tokens. For example, to use every event with the least privileged scopes:

```
openid offline_access Team.ReadBasic.All Channel.ReadBasic.All Chat.Read ChannelMessage.Read.All TeamMember.Read.All
```

The **Service Principal (App-Only)** credential uses application permissions instead. Refer to [Required application permissions by node](/integrations/builtin/credentials/microsoftentraserviceprincipal.md#required-application-permissions-by-node) in the Microsoft Entra Service Principal credentials documentation for the permission each event needs. Chat events aren't available with this credential.

## Subscription renewal

{% hint style="info" %}
**Feature availability**

Automatic subscription renewal in the Microsoft Teams Trigger node is available from n8n 2.45.1.
{% endhint %}

When you publish a workflow, the Microsoft Teams Trigger node creates a Microsoft Graph change notification subscription for each resource it watches. Microsoft Graph expires Teams subscriptions after three days. The trigger renews a subscription when Microsoft Graph sends a lifecycle notification for it, so a published workflow keeps receiving events with no action from you.

Before n8n 2.45.1, the trigger doesn't renew its subscriptions, so it stops receiving events about three days after you publish the workflow. On those versions, [unpublish the workflow](/build/understand-workflows/save-and-publish-workflows.md#how-to-unpublish-a-workflow) and publish it again. The trigger then receives new events for about three more days.

After you upgrade, the trigger also renews subscriptions that earlier n8n versions created, as long as they haven't expired. If the workflow stopped receiving events before the upgrade, unpublish it and publish it again. If you built a scheduled workflow that renews the subscriptions or republishes the trigger workflow, unpublish the trigger workflow and publish it again after you upgrade. Then you can unpublish that scheduled workflow.

From n8n 2.45.1, lifecycle notifications (`reauthorizationRequired` and `subscriptionRemoved`) no longer reach the workflow as items. Before n8n 2.45.1, every lifecycle notification starts an execution. If your workflow filters them out with an [If](/integrations/builtin/core-nodes/n8n-nodes-base.if.md) node on `lifecycleEvent`, you can remove that branch after you upgrade.

Renewal works only while your n8n instance is reachable. If a subscription expires while n8n is down or unreachable, the trigger stops receiving events. Unpublish the workflow and publish it again to re-create the subscription.

The trigger doesn't renew subscriptions for a workflow that has no stored subscription secret, for example after a loss of its static data or a workflow import. The subscriptions expire and the trigger stops receiving events. The instance log shows `Microsoft Teams Trigger: skipped lifecycle notifications: no stored secret, republish the workflow`. To fix it, unpublish the workflow and publish it again.

Renewal can also fail for other reasons, for example a Microsoft Graph rate limit, an expired refresh token, or revoked consent. The trigger doesn't retry, and the workflow shows no failed execution. The instance log shows one of these lines:

* `Microsoft Teams Trigger: failed to renew subscription`
* `Microsoft Teams Trigger: failed to re-create subscription`
* `Microsoft Teams Trigger: failed to list subscriptions or resolve resources, skipped re-create`

If no renewal succeeds before the subscription expires, the trigger stops receiving events. If the trigger fails to re-create a subscription, it has already stopped receiving events for that resource.

For an expired refresh token, reconnect the credential. For revoked consent, a Microsoft Entra administrator must grant consent again before you reconnect an OAuth2 credential. If you connected the credential before n8n 2.45.0, the reconnect also requests `TeamMember.Read.All`, which needs admin consent, as described in [Required scopes](#required-scopes). Then unpublish the workflow and publish it again to re-create the subscription.

With the default log settings, these log lines don't include the workflow ID or the error message. If you self-host n8n, set `N8N_LOG_FORMAT` to `json` to include them. Refer to [Logs environment variables](/deploy/host-n8n/configure-n8n/basic-configuration/use-environment-variables/logs.md) for more information.

If the trigger stops receiving events and you can't find one of these log lines, unpublish the workflow and publish it again.

## Related resources <a href="#related-resources" id="related-resources"></a>

n8n provides an app node for Microsoft Teams. Refer to the [Microsoft Teams node documentation](/integrations/builtin/app-nodes/n8n-nodes-base.microsoftteams.md) for more information.

View [example workflows and related content](https://n8n.io/integrations/microsoft-teams-trigger/) on n8n's website.

Refer to the [Microsoft Teams documentation](https://learn.microsoft.com/en-us/graph/api/resources/teams-api-overview?view=graph-rest-1.0) for details about their API.