Teams
Microsoft integration · 8 node(s) including 1 trigger.
00Overview
Microsoft Teams messaging and channel operations
Every field below is exactly what you see in the Flomation editor. Fields marked ● live picker let you choose from a list pulled live from your account — no IDs to look up.
01Connecting Teams
Teams signs in with a Microsoft account you connect to Flomation — there is no API key or secret to paste. Connect the account once and every Teams node picks it up automatically. Two optional fields let you steer it:
| Field | Type | Details | |
|---|---|---|---|
| Microsoft Account (email) | string | ||
| Microsoft OAuth Credential | credential | ${credentials.MICROSOFT_TEAMS} | |
| Bot App Password | secret | Required | ${secrets.TEAMS_APP_PASSWORD} |
${credentials.GOOGLE_DRIVE}), not an environment secret. Leave both fields blank and the node just uses your connected account.02Create
Create Channel
microsoft/teams/create_channel · Action
Create a new channel in a Microsoft Teams team
| Field | Type | Details | |
|---|---|---|---|
| Team ID | string | Required | |
| Channel Name | string | Required | |
| Channel Description | string | ||
| Membership Type | string | choices: Standard, Private, Shared |
Returns: tool_result, channel_id, success, error
03List
List Channel Messages
microsoft/teams/list_channel_messages · Action
Retrieve recent messages from a Microsoft Teams channel
| Field | Type | Details | |
|---|---|---|---|
| Team ID | string | Required | |
| Channel ID | string | Required | |
| Maximum Results | integer |
Returns: tool_result, messages, count, success, error
List Channels
microsoft/teams/list_channels · Action
List all channels within a Microsoft Teams team
| Field | Type | Details | |
|---|---|---|---|
| Team ID | string | Required |
Returns: tool_result, channels, count, success, error
List Teams
microsoft/teams/list_teams · Action
List all Microsoft Teams the authenticated user has joined
Returns: tool_result, teams, count, success, error
04Reply
Reply to Teams Message
microsoft/teams/reply · Action
Send a reply to a Teams conversation using the Bot Framework
| Field | Type | Details | |
|---|---|---|---|
| Message | text | Required | |
| Service URL | string | Required | ${service_url} |
| Conversation ID | string | Required | ${channel_id} |
| Activity ID | string | ${activity_id} | |
| Bot App ID | string | Required | ${secrets.TEAMS_APP_ID} |
Returns: tool_result, message_id, success, error
05Send
Send Channel Message
microsoft/teams/send_channel_message · Action
Post a message to a Microsoft Teams channel
| Field | Type | Details | |
|---|---|---|---|
| Team ID | string | Required | |
| Channel ID | string | Required | |
| Message Content | text | Required | |
| Content Type | string | choices: HTML, Text |
Returns: tool_result, message_id, success, error
Send Chat Message
microsoft/teams/send_chat_message · Action
Send a message to a Microsoft Teams chat conversation
| Field | Type | Details | |
|---|---|---|---|
| Chat ID | string | Required | |
| Message Content | text | Required | |
| Content Type | string | choices: HTML, Text |
Returns: tool_result, message_id, success, error
06Triggers
Teams Trigger
trigger/teams · Trigger
Triggers a flow when a message is received in Microsoft Teams
| Field | Type | Details | |
|---|---|---|---|
| App ID | string | Required | ${secrets.teams_app_id} |
| Tenant ID | string | ${secrets.teams_tenant_id} (optional, single-tenant only) |
Returns: user_id, user_name, sender, channel_id, content, conversation_type, teams_channel_id, teams_team_id, activity_id, service_url, tenant_id, agent_id, channel_type
07Notes & Limitations
Behaviours and constraints worth knowing before you build with these nodes.
- Replies are sent through the Bot Framework, which means they can only be posted back into a conversation your bot has already received a message from — this node cannot start a brand-new thread on its own.
- Newly created teams and channels can take a short while to finish provisioning, so a message or listing that runs immediately afterwards may briefly fail or return incomplete results before the change propagates.
- Sending a chat message targets an existing conversation, so you must already have the chat's identifier — these nodes cannot open a new one-to-one or group chat from scratch.
- Channel and chat messages are handled as formatted HTML content, so mentions, links, and styling need proper markup rather than plain text.
- Microsoft throttles high-volume requests and asks callers to wait before retrying, so tight loops that post or list many messages in quick succession may be temporarily rate-limited.