Authentication
1
Connect Your Account
Go to the Credentials page and connect your Microsoft Teams work/school account. You’ll be prompted to sign in with your organization’s Microsoft 365 credentials.
2
Grant Permissions
Approve the requested permissions when prompted. The node requires access to send channel messages and view team information.
3
Select Team and Channel
Choose the Team and Channel from the dropdown menus. Only teams you’re a member of and channels you have access to will appear.
Node Configuration
Required Inputs
| Parameter | Description |
|---|---|
| Team | The Teams team to send to. Select from teams you’re a member of. |
| Channel | The channel within the selected team. Appears after selecting a team. |
| Message | The text content of your message. Supports plain text. |
Thread Replies
To reply within an existing thread instead of posting a new message:1
Enable Thread Reply
Toggle Reply In Thread? in the node settings under “Show more options”.
2
Provide Thread ID
Connect the Thread ID input to a Thread ID output from a Teams Message Reader node, or provide a known thread ID.
Output
| Output | Description |
|---|---|
| Posted Thread ID | The unique identifier of the sent message. Use this to reply to the message in subsequent workflow steps or future runs. |
Batch Mode
The Teams Message Sender supports Loop Mode for sending multiple messages efficiently.Sending Multiple Messages
Connect a list to the Message input to send messages in batch:Sending to Multiple Threads
Combine with Loop Mode on both Message and Thread ID inputs to reply to multiple threads:- Automated responses to multiple conversations
- Bulk notifications to existing threads
- Processing and responding to support requests
Common Use Cases
Automated Notifications
Send alerts and updates to your team channel:- Monitor external systems and post updates
- Send daily/weekly summaries
- Alert on important events
Conversation Response Bot
Respond to messages in Teams channels:- Teams Message Reader: Get incoming messages with Thread IDs
- Ask AI: Generate appropriate responses
- Teams Message Sender: Reply to the original thread using Thread ID
Cross-Platform Notifications
Bridge communications between platforms:- Sync important messages between Slack and Teams
- Notify Teams channels of Slack activity
- Create unified communication workflows
Scheduled Reports
Post regular updates to channels:- Daily standup summaries
- Weekly metrics reports
- Automated status updates
Important Considerations
- Channel Membership: You must be a member of the channel to send messages. Private channels require an invite.
- Message Format: Messages are sent as plain text. For rich formatting, consider using the Microsoft Teams MCP node.
- Rate Limits: Microsoft Graph API has rate limits. When sending many messages, the node handles rate limiting automatically with retries.
- Thread Replies: When replying to a thread, the Thread ID must be valid and from the same channel.
- Message Length: Teams supports messages up to 28KB in size. Longer messages may be truncated.
Why Enterprise Only?
Microsoft Teams is designed as an enterprise collaboration platform integrated with Microsoft 365. The Microsoft Graph API endpoints for sending channel messages require specific permissions that are only available for work and school accounts: Required Permission:ChannelMessage.Send
This permission requires:
- A Microsoft 365 business or education subscription
- An Azure AD tenant (automatically created with Microsoft 365)
- User authentication with delegated permissions
- Access to Teams workspaces (Teams is not available for personal accounts)
- An Azure AD tenant to support delegated permissions
- The underlying infrastructure that supports channel message APIs
Advanced Teams Features
Need more advanced Teams capabilities like sending rich cards, managing channels, or working with adaptive cards? Use the Microsoft Teams MCP node to create custom Teams integrations with natural language prompts.