Short answer: Drop the "Slack → Edit 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 ID canvas_id | string | Required | ID of the Canvas to edit. |
Operation operation | options | Optional | Operation. Options: Replace all content, Append at end, Insert at start |
Content (Markdown) markdown | string | Required | Markdown content to apply. |
{"canvas_id": "{{trigger.canvas_id}}","operation": "{{trigger.operation}}","markdown": "{{trigger.markdown}}"}
{"ok": true,"raw": {}}
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.