Short answer: Drop the "Slack → List Channels" 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 Types types | options | Optional | Which types of channels to include |
Limit limit | string | Optional | Number of channels to return (max 1000) |
Exclude Archived exclude_archived | options | Optional | Exclude Archived. Options: Yes, No |
{"types": "{{trigger.types}}","limit": "100","exclude_archived": "{{trigger.exclude_archived}}"}
{"ok": true,"channels": [{"id": "C1234567890","name": "general","is_private": false,"num_members": 42}]}
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.