Slack Workflow Builder Examples: 12 Workflows to Copy, With Triggers and Steps
Twelve Slack Workflow Builder examples with trigger and steps, plus Slack's own list of 46 workflow templates read in a Free workspace on October 4, 2026, mapped to the examples.
On this page
Slack Workflow Builder turns a repeated task into a trigger plus a few steps. The most useful examples are a scheduled daily standup, a welcome message when someone joins a channel, a time-off request with manager approval, a help desk form that posts to a triage channel, an emoji reaction that escalates a message, and a webhook that posts alerts from another tool. Each one is below with its trigger and steps, ready to rebuild. To open Workflow Builder on desktop, click Agents & tools in the sidebar (older layouts say Tools or Automations), then Workflows, then New Workflow. It needs a paid plan: on a Free workspace that button carries a PRO badge, as we saw on October 4, 2026.
Slack's own workflow templates, read on October 4, 2026
A Free workspace still shows the full template gallery under Agents & tools, then Workflows, then Templates. You can read it but not use it. The banner says "Free teams do not have access to workflow templates", and clicking a template does nothing. We counted 46 templates.
13 of them work inside Slack alone, and they are the best starting points for the examples further down:
| Template | What Slack says it does | Closest example below |
|---|---|---|
| Weekly check in | Sends a weekly message asking for updates from the team | 1. Daily standup |
| Scheduled message | Schedules a recurring message to ask for status or project updates | 1, 8 |
| Welcome message | Greets channel newcomers and asks them to share an intro | 2. Welcome message |
| New hire onboarding | Lets newcomers join team channels from a link | 2 |
| Support response | Uses emoji reactions to respond to and manage support requests | 4. Help desk |
| Emoji reaction notification | Sends a reacting person a link to the message | 5. Emoji escalation |
| Message flag | Uses emoji to flag messages for action | 5 |
| Team kudos | Asks people to send kudos when they react with an emoji | 10. Kudos board |
| Weekly kudos | Sends a weekly message to celebrate team wins | 10 |
| Timesheet submission | Collects timesheets with a form | 3. Time-off request |
| Feedback submission to channel | Posts feedback in an easy-to-read format | 9. Feature requests |
| Ask me anything | Starts a half-hour AMA with a rotating host | 8. Weekly agenda |
| Giphy meeting reminders | Sends a GIF with a weekly meeting reminder | 8 |
The other 33 connect another service: Google Sheets (3), Google Calendar (2), Gmail, Google Tasks, Microsoft Outlook (2), Jira Cloud, GitHub, GitLab, Bitbucket, Linear, Asana, ClickUp, Workast, Notion, Miro, Guru, Box (2 with Box Sign), Dropbox, DocuSign, Salesforce, Zendesk, Intercom, PagerDuty, FireHydrant, Zoom, Twilio, Mailchimp and Smartsheet. Four carry an Advanced label: Mailchimp, Bitbucket, Smartsheet and one of the Google Sheets templates. There is no time-off or approval template in the list.
Workflow Builder triggers
Every workflow starts with one trigger. Slack's create a workflow guide lists these:
| Trigger | Starts when | Good for |
|---|---|---|
| From a link | Someone clicks Start Workflow in Slack | Forms: requests, kudos, bug reports |
| On a schedule | At the date, time and repeat you set | Standups, agendas, weekly check-ins |
| When a person joins a channel | Anyone joins the channel you pick | Welcome messages, channel rules |
| When an emoji reaction is used | Someone uses a chosen emoji in a chosen channel | Escalations, claiming a task |
| When a message is posted | A message contains keywords you set | Routing "outage" or "refund" posts |
| When a list item is updated | A list item, or one field of it, changes | Telling a requester their item is done |
| From a webhook | Another service sends a POST to your URL | Alerts from monitoring, CI, forms |
A link trigger only works inside Slack. Pin the link in the channel, bookmark it, or put it in a canvas.
After the trigger come steps: Slack steps (send a message, collect a form, create a channel, add people), connector steps that act in other services such as Google Sheets or Zoom, and custom steps your developers build. Buttons pause the workflow until someone clicks. Variables carry answers from earlier steps into later ones.
A webhook trigger gives the workflow a hooks.slack.com/triggers/ URL. How it differs from an app incoming webhook is in how to create a Slack webhook.
12 Slack Workflow Builder examples
1. Daily standup
- • Trigger: On a schedule, every weekday at 9:30.
- • Steps: Send a message to #standup with a Share update button. The button opens a form with three questions: yesterday, today, blockers. A final step posts the answers to the channel with the person as a variable.
- • Trigger: When a person joins #customer-support.
- • Steps: Send a message to the person who joined, with the channel's purpose, where the runbook lives, and who to ask.
- • Trigger: From a link, pinned in #team.
- • Steps: A form for dates, type and a note. A message to the manager with a Review button that opens a second form with Approve or Deny. A branch on that answer sends the requester one of two replies, and the approved branch also posts to #team-calendar.
- • Trigger: From a link in #it-help.
- • Steps: A form for the category, urgency and details. A message to a private #it-triage channel with a Claim button. After the click, a message tells the requester who has it.
- • Trigger: When the 🚨 reaction is used in #support.
- • Steps: Send a message to #on-call with a link to the original message and the person who reacted.
- • Trigger: When a message containing "refund" is posted in #sales.
- • Steps: Send a message to #finance with the message link.
- • Trigger: From a link, or from an emoji reaction on an alert.
- • Steps: A form for a short title, severity and owner. Create a channel for the incident. Add the owner and responders. Send the details as the first message and ask people to pin it.
- • Trigger: On a schedule, Monday at 10:00.
- • Steps: Send a message asking for agenda items with an Add topic button and a form. Each answer posts to the meeting channel, so the agenda builds itself before the meeting.
- • Trigger: From a link in #product-feedback.
- • Steps: A form for the request and the customer. A Google Sheets connector step adds a row. A message confirms it to the channel.
- • Trigger: From a link in #kudos.
- • Steps: A form with a person picker and a message. Post it to #kudos, mentioning the person as a variable.
- • Trigger: When a list item is updated, on the Status field.
- • Steps: A branch on the new value. If it is Done, send a message to the person in the item's Requester field.
- • Trigger: From a webhook, with text variables such as
service,severityanddescription. - • Steps: Send a message to #alerts that uses the three variables.
People answer in one place and the channel stays readable. For a plain repeating post without a form, a recurring scheduled message is lighter.
2. Welcome message for a channel
This beats a pinned message nobody opens, because it arrives as a direct message at the moment it is useful.
3. Time-off request with approval
The template list has no time-off template, so build this one from scratch; Timesheet submission gives you a form to start from. Pair it with an out-of-office status on the days themselves.
4. IT or help desk request
5. Emoji escalation
Anyone can escalate with one click, and the on-call channel gets a clean feed.
6. Keyword routing
Keep the keyword list short. A broad keyword fires on every casual mention.
7. Incident channel
8. Weekly meeting agenda
9. Feature requests into a spreadsheet
Connector steps need an account connected to the other service, and your admins may need to approve the connector first.
10. Kudos board
11. Tell the requester when a list item is done
When to track work in a list and when to write it in a canvas is in Slack canvas vs lists.
12. Alerts from another tool through a webhook
Slack generates the request URL when you publish. It starts with https://hooks.slack.com/triggers/. Test it with a POST whose JSON keys match your variables:
curl -X POST "https://hooks.slack.com/triggers/T000/000/xxxx" \
-H "Content-Type: application/json" \
-d '{"service": "api", "severity": "high", "description": "Error rate over 5%"}'
Three limits from Slack's webhook workflow article: up to 20 variables, no nested JSON, and one request per second. If a variable you defined is missing from the request, the workflow fails. Anyone with the URL can start the workflow, so keep it out of public repositories. To connect Jira without a webhook, the Jira Cloud app has its own commands; see Slack Jira integration.
GitHub Actions can start one of these workflows through the same kind of webhook trigger, using webhook-type: webhook-trigger; the YAML is in how to send a Slack message from GitHub Actions.
Never appear "away" on Slack again
Cloud-based. No downloads. Works 24/7 even when your laptop is off.
Conditional logic: branches
A branch sends the workflow down different paths depending on a value, such as a form answer or a list field. Use one where you would otherwise build two nearly identical workflows: approved or denied, hardware or software request, high or low severity. Add it from the step list in Workflow Builder; Slack's help center covers it under adding conditional branches.
Is Slack Workflow Builder free?
No. Slack's help center lists Workflow Builder as available on paid plans. On a paid plan, every member can build workflows and members and guests can use them by default. Admins can limit who builds, which connector steps are allowed, and who can create webhook workflows. If you cannot see the option, ask an owner or admin.
Workflow templates vs building from scratch
A template fills in the trigger and steps, and you edit the details before publishing. Start from one when it is close, such as Weekly check in for a standup or Welcome message for a channel greeting, and build from scratch for anything with your own form fields or branches, such as the time-off approval.
For a one-line automation, a workflow may be more than you need. /remind handles simple repeating nudges (examples here), and every other built-in command is in Slack slash commands.
FAQ
Can I use Workflow Builder on the Free plan?
No. New Workflow and every template are locked on Free. For a repeating message, /remind works on Free.
Can people outside my company use my workflow?
In Slack Connect channels, if you allow connected external organizations in the workflow's settings.
Can a workflow set my Slack status or keep me active?
Status and presence are separate. Presence follows your keyboard and mouse input, and no workflow step makes you active. To set a status from code, see set Slack status with the API.
Stop Jiggling Your Mouse.
Join hundreds of remote workers who never worry about their Slack status. Set it up once, stay green forever.
Related Articles
Slack Bot Scopes: The Scope Each API Method Needs, Measured on 44 Methods
We gave a Slack bot one scope, called 44 common Web API methods, and read the needed field of every missing_scope error. Then we added the scopes and called them again. The table shows which scope clears each method.
Slack File Size Limit: 1 GB Is Exactly 1,073,741,824 Bytes, Tested
We uploaded files of 50 MB, exactly 1 GiB and 1 GiB plus one byte to Slack through its upload API. The limit is 1,073,741,824 bytes, and a failed upload can still leave a broken file behind.
Slack Dark Mode: Where the Setting Is, and Which Custom Emoji Disappear
Slack's dark mode is under Preferences > Appearance > Color Mode, with Light, Dark and System. We switched modes in Slack web with three test emoji and measured which ones vanish.