Slack Actions (Collaboration)
Send Slack Message
What it does: Sends a message to a Slack channel or user.
Inputs
- Channel (required) — Where to send: channel ID or name (e.g. #general), or user ID for a DM. Use a variable for dynamic routing (e.g. from trigger).
- Message (required) — The message text. Supports Slack formatting (e.g. bold, italic). Can include variables.
- Thread TS (optional) — Timestamp of a parent message to reply in that thread. Omit to post a new top-level message.
- Blocks (optional) — Slack Block Kit JSON for rich layout (sections, buttons, inputs). Overrides or supplements the Message text when provided.
Outputs
Message ID and channel/timestamp so you can reference the message later (e.g. for “Wait for Slack Message” or threading).
Output schema
- messageId / ts — Unique message timestamp ID. Use for thread replies or follow-up steps.
- channel — Channel (or DM) ID where the message was sent.
- timestamp — When the message was posted (ISO or epoch).
Wait for Slack Approval
What it does: Sends an approval request in Slack (e.g. with Approve/Reject buttons or a prompt) and pauses the automation until the user approves or rejects. Use for human-in-the-loop approvals in Slack. Inputs: channel, prompt/message, optional timeout. Outputs: approval decision (e.g. approved true/false), optional comment. See your step configuration for the exact schema.
Wait for Slack Message
What it does: Pauses the workflow until the user responds in Slack (human-in-the-loop).
Inputs
- Channel (required) — Channel or user ID to send the prompt to and listen for a reply (e.g. the same channel as the trigger, or a DM).
- Prompt (required) — The message to send to the user (e.g. “Please confirm: approve or reject?”). Can include variables.
- Timeout (optional) — How long to wait for a response (e.g. 300 seconds). After timeout, the step may fail or return a default depending on product.
- Expected response format (optional) — Hint for the user (e.g. “Reply with a number 1–5”) or for parsing. Behavior is product-specific.
Outputs
The user’s reply text (and optionally message ID/timestamp) for use in conditions or next steps.
Output schema
- response / text — The reply message text from the user.
- messageId / ts (optional) — The reply message’s timestamp ID.
- userId (optional) — Who replied.
Content Reviews
What it does: Waits for a Slack content review: the workflow sends content (e.g. draft message or document) to a channel or user for review; the reviewer can approve, reject, or edit. The step resumes with the review result and optionally the edited content. Use for human-in-the-loop content approval. See your step configuration for inputs and output schema.
Get Slack Data Input / Get Interactive Slack Data Input
What it does: Collects structured data from the user via Slack—form fields, or interactive components (buttons, dropdowns).
Inputs
- Channel (required) — Channel or user ID to send the form or message to.
- Form fields / Interactive components (required) — Definition of what to collect: text fields, dropdowns, buttons, etc. Configure in the step (e.g. “Name (text)”, “Priority (dropdown: High, Medium, Low)”).
- Prompt (required) — Introductory message shown above the form or components (e.g. “Fill in the details below”). Can include variables.
Outputs
The user’s answers as key-value pairs (field name → value) or selected option(s) for use in later steps.
Output schema
- fieldName — One key per form field or component. Values are strings (text input), selected option (dropdown), or button value. Use the variable picker to see exact output names (e.g.
#StepName.Name,#StepName.Priority).