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
- Trigger: Scheduled at 9:00 AM every weekday
- Step 1: Send a form to #engineering asking "What did you complete yesterday? What are you working on today? Any blockers?"
- Step 2: Collect responses for 2 hours
- 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
Related Tools
Slack
Team messaging platform with Workflow Builder for creating automated processes without code.
Workflow AutomationZapier
Automate workflows between apps without coding—connect 9,000+ tools with simple, reliable automation.
Workflow AutomationMake
Automate your work with visual workflow builder and AI agents
Workflow AutomationActivepieces
No-code workflow automation with self-hosting and AI-powered features
Workflow AutomationRelated 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
Keystroke vs n8n in 2026: Agent-Built TypeScript vs the Visual Canvas
Keystroke, launched in July 2026 by Y Combinator W24 company Sprint Labs, is a code-first automation platform where AI coding agents write workflows as TypeScript in the user's repository. n8n, founded in 2019, is the most widely deployed source-available visual workflow platform, with 200,000+ users and a $2.5 billion valuation. This comparison covers the agent-authored versus canvas building models, durable execution, licensing (Elastic License 2.0 vs the Sustainable Use License), verified July 2026 pricing including Keystroke's usage metering, and the maturity gap between a days-old platform and an established ecosystem.
QuantumBPM vs Camunda 2026: Single-Binary Challenger vs the BPMN Incumbent
QuantumBPM (launched 2026, Coroid s.r.o., Slovakia) packages a BPMN 2.0 runtime and DMN 1.5 decision engine into one Go binary backed by Temporal and PostgreSQL. Camunda (Berlin, founded 2013) is the category incumbent: Camunda 7 (Apache 2.0, in maintenance) and the Zeebe-based Camunda 8 platform. This comparison covers product structure, architecture, DMN TCK conformance with recording dates, deployment, pricing, and vendor maturity, verified July 2026.
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.