Short answer: Drop the "Slack → Archive Channel" 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 | string | Required | Slack channel ID (starts with C for public, G for private group, D for DM). Find via List Channels. Not the channel name with #. |
{"channel": "e.g. C01234567"}
{"ok": true}
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.