DocumentationWorkflowsApps and services
Teams node
Send channel or direct-chat messages in Microsoft Teams. Learn how to configure it, map inputs and outputs, run a test and resolve common errors.
8 min readUpdated
What this node does
Send channel or direct-chat messages in Microsoft Teams.
Use Teams as a clearly defined step in an anymize workflow.
- Processes one input.
- Provides one output for following steps.
- Runs as a regular step in the flow.
Set up the node
- 01Open a workflow and add Teams from the node catalog.
- 02Select your microsoft connection. You can create it directly in the workflow if needed.
- 03Complete the required fields and map values from previous steps.
- 04Run the node with a small test record and inspect its output.
- 05Connect the successful output and activate the workflow after an end-to-end test.
Operations and modes
Choose the required function in Action. The panel then shows the relevant settings.
- Send channel message
- Send direct chat
Settings
| Field | Meaning | Area |
|---|---|---|
| Action | Choices: Send channel message, Send direct chat | Standard |
| Team | The ID of the team (format 19:…). You'll find it in team management or via an upstream step. | Standard |
| Channel | The ID of the channel (format 19:…) in the selected team. | Standard |
| Chat | The ID of the direct chat the message should go to. | Standard |
| Message | Configure this value in the node panel. | Standard |
| Format | Plain text or formatted HTML. | Standard |
| Run once per item | Off (default): the node runs once for the whole input. On: if it receives several items (e.g. from Split Out), it runs once PER item, and {{ $json }} is that one item each time. This is how you work through a file list entry by entry. | Standard |
| If one item fails | "Skip" writes an `error` field for the failed item and keeps processing the rest, instead of losing the whole run to a single unreadable file. | Standard |
| Pause between items (milliseconds) | Wait before every run except the first. 1000 = 1 second per item. Useful when the other side would otherwise throttle you. Maximum 300000 (5 minutes). | Standard |
Inputs and outputs
| Input | Meaning | Type |
|---|---|---|
| Standard | Receives the complete result from the previous step. | JSON |
| Output | Meaning | Type |
|---|---|---|
| Standard | Makes the result available to the next step as JSON. | JSON |
This node can process lists item by item. Error handling and the delay between items are available in advanced settings.
Example and test run
Deploy notification: begin with a small, recognizable record. Inspect the output and only map fields that are present there.
Test-run example
{
"channel_id": "19:abc123@thread.tacv2",
"content": ":rocket: Prod-Deploy abgeschlossen"
}Access and security
This node uses a connected microsoft account. Review the requested permissions and grant only the required access.
Store keys and credentials in the protected connection manager. Never paste them into normal workflow fields, test data or descriptions.
Troubleshooting
- No output: inspect the latest run and confirm that the previous node returned the expected fields.
- Empty variable: open the previous step output and use a field name from the real test data.
- Connection rejected: reconnect the service and grant the permissions required by this step.
- List processed once: enable per-item execution in advanced settings.