> Node: Microsoft Teams Trigger (`microsoft_teams_trigger`) · Webhook trigger · v1 > Category: Communication · Credentials: Microsoft Teams OAuth2 (`microsoftTeamsOAuth2Api`) > Updated: 2026-08-16 # Microsoft Teams Trigger > Triggers on Microsoft Teams events such as new messages, channels, chats, and team members ## Overview Receives webhook notifications from Microsoft Graph change notifications when events occur in Microsoft Teams. Supports triggering on new channel messages, new chat messages, new channels, new chats, and new team members. Microsoft Graph uses a subscription-based webhook model: subscriptions are created via the Graph API with a notificationUrl pointing to this webhook endpoint. When the subscription is first created, Microsoft sends a validation request with a validationToken query parameter that must be echoed back as plain text. Subsequent notifications arrive as POST requests with an array of change notification objects in the body. Each notification includes the resource path, subscription ID, tenant ID, and resource data. Supports scoping to specific teams, channels, or chats, or watching all available resources. Requires OAuth2 authentication with appropriate Microsoft Graph permissions (ChannelMessage.Read.All, Chat.Read.All, Team.ReadBasic.All, Subscription.ReadWrite.All). Useful for building chat bots, team activity monitors, notification pipelines, and collaboration automation workflows. **Category:** Communication **Tool Name:** `microsoft_teams_trigger` **Version:** 1 **Appearance:** Icon: `lucide-MessageSquare` | Color: `#5059c9` ## Node Type **Trigger** — webhook (receives incoming HTTP callbacks) ## Input / Output | Direction | Port(s) | |-----------|--------| | Input | None (trigger node) | | Output | `Output` | ## Credentials This tool requires **Microsoft Teams OAuth2** credentials. See the [Credentials Guide](https://busybot.net/credentials/microsoft-teams-oauth2-api/) for setup instructions. ### Parameters | Parameter | Type | Required | Default | Description | |-----------|------|----------|---------|-------------| | Microsoft Account | `credential` | No | — | Connect your Microsoft account via OAuth2. | | Trigger On | `options` | No | `newChannelMessage` | Select the event to trigger the workflow. | | | | | | Options: `newChannel` (a new channel is created), `newChannelMessage` (a message is posted to a channel), `newChat` (a new chat is created), `newChatMessage` (a message is posted to a chat), `newTeamMember` (a new member is added to a team) | | Watch All Teams | `boolean` | No | `false` | Whether to watch for the event in all the available teams. _(shown when Trigger On is `newChannel`, `newChannelMessage`, `newTeamMember`)_ | | Team ID | `string` | Yes | — | The ID of the team to watch. Enter a Team ID (UUID format, e.g. 61165b04-e4cc-4026-b43f-926b4e2a7182) or extract from a Teams URL. _(shown when Trigger On is `newChannel`, `newChannelMessage`, `newTeamMember` and Watch All Teams is `false`)_ | | Watch All Channels | `boolean` | No | `false` | Whether to watch for the event in all the available channels. _(shown when Trigger On is `newChannelMessage` and Watch All Teams is `false`)_ | | Channel ID | `string` | Yes | — | The ID of the channel to watch. Enter a Channel ID (e.g. 19:-xlxyqXNSCxpI1SDzgQ_L9ZvzSR26pgphq1BJ9y7QJE1@thread.tacv2). _(shown when Trigger On is `newChannelMessage`, Watch All Teams is `false` and Watch All Channels is `false`)_ | | Watch All Chats | `boolean` | No | `false` | Whether to watch for the event in all the available chats. _(shown when Trigger On is `newChatMessage`)_ | | Chat ID | `string` | Yes | — | The ID of the chat to watch. Enter a Chat ID (e.g. 19:7e2f1174-e8ee-4859-b8b1-a8d1cc63d276@unq.gbl.spaces). _(shown when Trigger On is `newChatMessage` and Watch All Chats is `false`)_ | ## Output Data Microsoft Graph delivers an array of change notifications, and each notification becomes its own output item: - `_trigger` — always `microsoft_teams_webhook` - `_timestamp` — ISO 8601 timestamp of when the request arrived - `_webhookEvent` — the notification's change type (`created`) - `subscriptionId` — the Graph subscription that produced the notification - `resource` — the Graph resource path the change happened on, e.g. `teams/{teamId}/channels/{channelId}/messages/{messageId}` - `tenantId` — the Microsoft 365 tenant the change came from - `clientState` — the client state value carried on the subscription - `subscriptionExpirationDateTime` — when the subscription expires - `changeType` — the change type Graph reported - `resourceData` — the changed resource stub, with `id`, `@odata.type` and `@odata.id` plus any additional fields Graph includes Reference the payload downstream by expression, e.g. `{{ $json.resourceData.id }}`. Change notifications identify what changed rather than carrying the full message body, so follow this trigger with a Microsoft Graph read step when you need the message content. Graph's validation handshake is answered automatically and produces no items. ## Usage Examples - Start a workflow when a new message is posted in a Teams channel - Trigger a notification when someone sends a chat message - Automate onboarding actions when a new member joins a team - Monitor when new channels are created in a team - React to new chats being started with the authenticated user ## Example Configuration Watch every team for new channels: ```json { "type": "microsoft_teams_trigger", "parameters": { "event": "newChannel", "watchAllTeams": true } } ``` Watch one team for new members: ```json { "type": "microsoft_teams_trigger", "parameters": { "event": "newTeamMember", "watchAllTeams": false, "teamId": "61165b04-e4cc-4026-b43f-926b4e2a7182" } } ``` Watch every channel in one team for messages: ```json { "type": "microsoft_teams_trigger", "parameters": { "event": "newChannelMessage", "watchAllTeams": false, "teamId": "61165b04-e4cc-4026-b43f-926b4e2a7182", "watchAllChannels": true } } ``` Watch a single channel for messages: ```json { "type": "microsoft_teams_trigger", "parameters": { "event": "newChannelMessage", "watchAllTeams": false, "teamId": "61165b04-e4cc-4026-b43f-926b4e2a7182", "watchAllChannels": false, "channelId": "19:-xlxyqXNSCxpI1SDzgQ_L9ZvzSR26pgphq1BJ9y7QJE1@thread.tacv2" } } ``` Watch every chat for messages: ```json { "type": "microsoft_teams_trigger", "parameters": { "event": "newChatMessage", "watchAllChats": true } } ``` Watch one specific chat: ```json { "type": "microsoft_teams_trigger", "parameters": { "event": "newChatMessage", "watchAllChats": false, "chatId": "19:7e2f1174-e8ee-4859-b8b1-a8d1cc63d276@unq.gbl.spaces" } } ``` Fire when a new chat is created: ```json { "type": "microsoft_teams_trigger", "parameters": { "event": "newChat" } } ``` ### Trigger Behavior - **Activation:** When the workflow is activated, a webhook endpoint is registered with the service. - **Deactivation:** The webhook is automatically unregistered when the workflow is deactivated. - **Payload:** The incoming webhook payload is parsed and output as workflow items. - **Verification:** Supports signature verification where applicable. ## Tips Entry point that fires when Microsoft Graph sends a change notification for subscribed Microsoft Teams events. Select the event type (new channel message, new chat message, new channel, new chat, or new team member). For team-scoped events, optionally watch all teams or select a specific team. For channel messages, optionally watch all channels or select a specific channel. For chat messages, optionally watch all chats or select a specific chat. Handles the Microsoft Graph validation handshake automatically by echoing the validationToken. Requires HTTPS webhook URL and OAuth2 credentials with appropriate Microsoft Graph permissions. ### Important Notes - **ID Formats**: Team IDs use UUID format, while Channel IDs and Chat IDs use Microsoft's thread-based format - **Conditional Logic**: Parameters are shown/hidden based on event selection and previous parameter values - **Scope Hierarchy**: The configuration follows a hierarchical scope: All Teams → Specific Team → All Channels → Specific Channel - **Event Dependencies**: Some parameters only apply to specific events - ensure the event selection matches the desired monitoring scope