How to set up Slack workflow automations

Quick Answer: Open Slack Workflow Builder from the sidebar (Automations > Workflow Builder), choose a trigger (message posted, emoji reaction, schedule, or webhook), add steps like sending messages or collecting forms, then publish. Available on Slack Pro, Business+, and Enterprise Grid plans.

How to Set Up Slack Workflow Automations

Slack Workflow Builder allows teams to create automated processes directly within Slack without writing code. As of April 2026, Workflow Builder is available on Pro ($8.75/user/month), Business+ ($12.50/user/month), and Enterprise Grid plans.

Step 1: Open Workflow Builder

Click "Automations" in the left sidebar, then select "Workflow Builder." Click "New Workflow" and give it a descriptive name (for example, "New Hire Onboarding Checklist").

Step 2: Choose a Trigger

Select what starts the workflow:

  • Shortcut — User clicks a shortcut button in a channel
  • New channel message — When a message is posted in a specific channel
  • Emoji reaction — When a specific emoji is added to a message
  • Scheduled — Run on a daily, weekly, or custom schedule
  • Webhook — External service sends a POST request to a Slack URL
  • Person joined channel — When someone joins a designated channel

Step 3: Add Workflow Steps

Available steps include:

  • Send a message — Post a message to a channel or DM a user
  • Send a form — Collect information via a Slack form
  • Add a reaction — React to a message with an emoji
  • Update channel topic — Change channel topic or purpose
  • Create a channel — Spin up a new channel with a naming pattern
  • Connector steps — Trigger actions in Google Sheets, Jira, Salesforce, and other connected apps

Step 4: Use Variables

Variables pass data between steps. When a form collects a user name, that variable can be inserted into subsequent message steps. Click the "{x}" icon in any text field to insert a variable from a previous step.

Step 5: Publish and Test

Click "Publish" to make the workflow active. Test by triggering it in a test channel. Published workflows can be paused, edited, and republished without losing configuration.

Practical Example: Daily Standup Collection

  1. Trigger: Scheduled at 9:00 AM every weekday
  2. Step 1: Send a form to #engineering asking "What did you complete yesterday? What are you working on today? Any blockers?"
  3. Step 2: Collect responses for 2 hours
  4. Step 3: Post a summary message to #engineering with all responses

This replaces synchronous standup meetings with asynchronous updates, saving 15-30 minutes per day for teams across multiple time zones.

Limitations

  • Workflows cannot branch based on conditions (linear steps only)
  • Maximum 200 workflow runs per day per workflow on Pro plans
  • External app connector steps require Business+ or Enterprise Grid
  • Cannot send messages as the workflow author (messages come from "Workflow")

Related Questions

Last updated: | By Rafal Fila

Related Tools

Related Rankings

Dive Deeper