Short answer: Drop the "Mattermost → Send Mattermost 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 |
|---|---|---|---|
Channel ID channel_id | string | Required | Channel ID. Example: abcdef1234567890 |
Message message | string | Required | Message text (supports Markdown) |
Thread Root ID root_id | string | Optional | Post ID to reply to (creates a threaded reply) |
{"channel_id": "e.g. abcdef1234567890","message": "e.g. Build #42 deployed successfully :white_check_mark:","root_id": "e.g. post123abc"}
{"id": "post123","message": "Build deployed!","create_at": 1700000000000,"channel_id": "abcdef123"}
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.