n8n-nodes-teamsbot

This community node package adds Microsoft Teams Bot Framework support to n8n with a focus on modern single-tenant bot setups.

It includes:

• Microsoft Teams Bot Trigger: receives incoming Bot Framework activities from Teams
• Microsoft Teams Bot: action node for activity, adaptive card, attachment, conversation, proactive, and reaction APIs

n8n is a fair-code licensed workflow automation platform.

Installation

Follow the installation guide in the n8n community nodes documentation.

Operations

Microsoft Teams Bot Trigger

• Trigger on activity types:
  • conversationUpdate
  • event
  • installationUpdate
  • message
  • messageDelete
  • messageReaction
  • messageUpdate
• Optional behaviors:
  • Command router (prefix + optional command definition JSON)
  • Configurable webhook response mode (onReceived, lastNode, responseNode)
  • Conversation reference capture for proactive messaging
  • Debug output
  • Dedupe window controls
  • Ignore bot-originated activities
  • Include raw activity in output
  • Validate channel endorsements
  • Verify JWT signatures from Bot Framework OpenID/JWKS endpoints

Microsoft Teams Bot

• Activity operations:
  • Send Activity
  • Reply To Activity
  • Update Activity
  • Delete Activity
  • Send Typing Indicator
• Adaptive card operations:
  • Send Adaptive Card
  • Reply With Adaptive Card
  • Update Adaptive Card
• Attachment operations:
  • Send File Attachment
  • Send Inline Attachment
• Conversation operations:
  • Create Conversation
  • Create Direct Conversation
  • Get Conversation Details
  • Get Conversation Member
  • Get Conversation Members
  • Get Paged Conversation Members
• Proactive operations:
  • List References
  • Get Reference
  • Upsert Reference
  • Delete Reference
  • Send Proactive Message
• Reaction operations:
  • Add Reaction
  • Remove Reaction
• Helper features:
  • Mention entity helper (auto-mention sender or explicit mention fields)
  • Retry count + retry delay controls
  • Debug output for attempts and request metadata
  • Output mode control (Pass Through, Merge, Response Only) for downstream compatibility

Credentials

Create a Microsoft Teams Bot API credential with:

• Microsoft App ID
• Microsoft App Secret
• Tenant ID (required for single-tenant token acquisition)

This package requests tokens from:

https://login.microsoftonline.com/<tenant-id>/oauth2/v2.0/token

with scope:

https://api.botframework.com/.default

Usage

Minimal inbound -> outbound workflow

1. Add Microsoft Teams Bot Trigger.
2. Configure your Bot Framework messaging endpoint to the trigger webhook URL.
3. Add a Microsoft Teams Bot node after the trigger.
4. Use operation Reply To Activity or Send Activity.
5. Map:
   • Service URL -> {{$json.botContext.serviceUrl}}
   • Conversation ID -> {{$json.botContext.conversationId}}
   • Activity ID (if replying/updating/deleting) -> {{$json.botContext.activityId}}

Endpoint reminder

The trigger webhook path is:

<your-n8n-webhook-base>/<workflow-webhook-path>/webhook

Use the exact production URL when configuring the bot messaging endpoint in Azure.

Resources

• n8n community nodes documentation
• Bot Framework authentication troubleshooting
• Microsoft identity platform OAuth 2.0 client credentials flow

Version history

• 0.0.3: Added output mode control on Microsoft Teams Bot action node, defaulting to pass-through output so trigger fields (for example botContext) are preserved.
• 0.0.2: Added command routing, adaptive card helpers, mention helpers, proactive operations, attachment helpers, conversation utilities, reaction operations, and retry/debug controls.
• 0.0.1: Initial release with trigger + action nodes and single-tenant auth model.