Short answer: Drop the "Slack → List Users" 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 |
|---|---|---|---|
Limit limit | string | Optional | Number of users to return per page (max 200) |
{"limit": "100"}
{"ok": true,"members": [{"id": "U1234567890","name": "john","profile": {"email": "john@company.com","display_name": "John"},"real_name": "John Doe"}]}
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.