Short answer: Drop the "Slack → Create Canvas" 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 |
|---|---|---|---|
Canvas Title title | string | Required | Title shown at the top of the Canvas. |
Content (Markdown) markdown | string | Required | Canvas body in Markdown. |
Share to Channel (optional) channel | string | Optional | Slack channel ID (starts with C for public, G for private group, D for DM). Find via List Channels. Not the channel name with #. |
{"title": "{{trigger.title}}","markdown": "{{trigger.markdown}}","channel": "e.g. C0123456789"}
{"ok": true,"raw": {},"canvas_id": "F0123ABC"}
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.