Short answer: Drop the "Microsoft Teams → Send Teams Channel Message" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Team ID team_id | string | Required | Team ID. Example: 19:abc123@thread.tacv2 |
Channel ID channel_id | string | Required | Channel ID. Example: 19:def456@thread.tacv2 |
Message content | string | Required | Message content (supports HTML) |
{"team_id": "e.g. 19:abc123@thread.tacv2","channel_id": "e.g. 19:def456@thread.tacv2","content": "e.g. <b>Build deployed!</b> Version 2.1.0 is now live."}
{"id": "msg123","body": {"content": "Build deployed!"},"createdDateTime": "2025-01-15T12:00:00Z"}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.