Short answer: Drop the "Slack → List Channel Members" 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 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 #. |
Max members limit | number | Optional | Max number of members to return per page (1–1000). |
{"channel": "e.g. C0123456789","limit": "{{trigger.limit}}"}
{"ok": true,"raw": {},"count": 3,"members": ["U0123","U0456","U0789"]}
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.