Microsoft Teams
The Microsoft Teams block sends messages to Teams channels or users, replies to threads, reads channel messages, reacts to messages, and creates online meetings — all from your workflow.
Team Notifications: Post rich Adaptive Card messages (title, facts table, image, footer) to a channel the moment something happens in your workflow — a new order, a failed job, a fresh lead.
Key Features
- Send Message (default): Post an Adaptive Card message to a channel or directly to a user
- Rich Cards: Add a title, key–value facts, an attachment image, and styled footer lines
- Thread Replies: Reply to an existing message in a channel thread
- Read Messages: Fetch recent messages from a channel
- Discovery: List the teams you belong to and the channels in a team
- Reactions: Add a reaction (e.g.
like,heart) to a message - Meetings: Create an online Teams meeting with subject, start, and end time
Want workflows that start from a Teams message instead? Use the Microsoft Teams trigger.
Operations
| Operation | What it does |
|---|---|
| Send Message (default) | Sends an Adaptive Card message to a channel or a user |
| Reply To Thread | Posts a reply under an existing channel message |
| Get Messages | Fetches recent messages from a channel (with a limit) |
| List Teams | Lists the teams the connected account belongs to |
| List Channels | Lists the channels of a team |
| Add Reaction | Adds a reaction to a message |
| Create Meeting | Creates an online Teams meeting |
Configuration
| Parameter | Type | Required | Description |
|---|---|---|---|
| Action | Select | Yes | One of the operations above (defaults to Send Message) |
| Recipient Type | channel / user | Send Message | Post to a channel or send a chat message to a user |
| Team ID | Select/Text | Channel operations | The target team |
| Channel ID | Select/Text | Channel operations | The target channel |
| User ID | Text | Send to user | The recipient when Recipient Type is user |
| Message | Text | Send / Reply | The message text (supports variables) |
| Title | Text | No | Card title for Send Message |
| Facts | Key–value list | No | Rows shown as a facts table on the card |
| Attachment Message / Attachment URL | Text | No | Extra text and an image URL for the card |
| Footer Items | List | No | Footer lines with weight, spacing, and subtle styling |
| Message ID | Text | Reply / Add Reaction | The parent message to reply or react to |
| Reaction Type | Text | Add Reaction | e.g. like, heart |
| Limit | Text | Get Messages | Maximum number of messages to fetch |
| Meeting Subject | Text | Create Meeting | Title of the meeting |
| Start / End Date Time | Text | Create Meeting | ISO dates, e.g. 2026-09-01T15:00:00Z |
Setting up the credential
Microsoft Teams uses your own Azure app registration, so the tokens stay under your organization's control:
- In the Azure Portal (opens in a new tab), open Microsoft Entra ID → App registrations → New registration and create an app.
- In the block settings, click to add a Microsoft Teams credential. The modal shows a Redirect URI (
https://<your-builder>/api/microsoft-teams/oauth/callback) — copy it and add it as a Web redirect URI on your Azure app. - In Azure, create a client secret (Certificates & secrets) and note the Directory (tenant) ID and Application (client) ID from the app's Overview page.
- Back in the modal, enter a Label, the Tenant ID, Client ID, and Client Secret, then click Connect.
- Sign in with your Microsoft account and consent to the requested permissions. The credential is saved once consent completes.
The signed-in account must be a member of the teams and channels you want the block to post in.
Example: order alerts channel
- A Webhook Trigger receives a new order from your store.
- A Microsoft Teams block with Send Message posts to the
#orderschannel: title "New order", facts forOrder ID: {{order_id}}andAmount: {{amount}}. - The fulfillment team reacts and replies in the thread — and a second workflow can pick that up via the Teams trigger.
Output
The block returns the Microsoft Graph response for the operation — for example, the sent message's ID for Send Message / Reply To Thread, the array of messages for Get Messages, the team or channel lists for the List operations, and the meeting details (including the join link) for Create Meeting. Downstream blocks can reference these values, such as keeping a message ID to reply to it later.