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

Activepieces

No-code workflow automation with self-hosting and AI-powered features

Workflow Automation

Automatisch

Open-source Zapier alternative

Workflow Automation

Bardeen

AI-powered browser automation via Chrome extension

Workflow Automation

Calendly

Scheduling automation platform for booking meetings without email back-and-forth, with CRM integrations and routing forms for lead qualification.

Workflow Automation

Related Rankings

Best Durable Workflow Engines for Production in 2026

A ranked list of the best durable workflow engines for production deployments in 2026. Durable workflow engines persist execution state to a database so that long-running workflows survive process restarts, deployments, and infrastructure failures. The ranking covers Temporal, Prefect, Apache Airflow, Camunda, Windmill, and n8n. Tools were evaluated on production reliability, developer experience, scalability, open-source health, and documentation quality. The shortlist intentionally mixes code-first engines (Temporal, Prefect, Airflow) with hybrid visual platforms (Camunda, Windmill, n8n) to reflect how production teams actually choose workflow engines in 2026.

Best No-Code Automation Platforms in 2026

A ranked list of no-code automation platforms in 2026. The ranking covers visual workflow builders that allow non-engineering teams to connect SaaS apps, route data, and add conditional logic without writing code. Entries cover proprietary cloud platforms (Zapier, Make, Pipedream, IFTTT) and open-source visual builders (n8n, Activepieces). Scoring reflects integration breadth, pricing accessibility, visual editor ease, reliability and error handling, and self-hosting availability.

Dive Deeper

case-study

Migrating 23 Make Scenarios to Self-Hosted n8n: a 3-Week Breakdown

Anonymized retrospective of a DTC ecommerce brand migrating 23 Make scenarios to a self-hosted n8n instance over three weeks. Tooling cost dropped from $348/month on Make Teams to roughly $12/month on a Hetzner VPS, but credential and webhook recreation consumed about 40% of total project time.

comparison

Trigger.dev vs Inngest 2026: OSS Durable Runners Compared

Trigger.dev (2022, London) is a fully Apache 2.0 durable runner with task-based authoring, machine-size selection, and first-class self-host. Inngest (2021, San Francisco) is a developer-first event-driven step platform with an open-source dev server and a managed cloud (50K step runs/month free, $20/month Hobby). This 2026 comparison covers license, programming model, pricing, observability, and self-host options.

comparison

Inngest vs Temporal 2026: Durable Functions vs Durable Workflows

Inngest (2021, San Francisco) is a developer-first durable functions platform with TypeScript and Python SDKs, 50,000 step runs/month free, and Hobby pricing from $20/month. Temporal (2019) is the heavyweight durable workflow engine with seven-language SDK coverage, Cassandra-backed scale, and Cloud pricing from roughly $200/month at low volume or $2.5-4.5K/month self-host. This 2026 comparison covers programming model, pricing, scale ceiling, and operational footprint.