Slack Workflow Builder Examples: 12 Workflows to Copy, With Triggers and Steps

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, New, Build Workflow. It is included on paid plans, and by default any member can build a workflow.

What a workflow cannot do is keep you present. Your dot goes grey 10 minutes after your last input in the Slack window, and no workflow step changes that. Slack Green keeps your status active during the working hours you set, from the cloud.

Workflow Builder triggers

Every workflow starts with one trigger. Slack's create a workflow guide lists these:

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.

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.

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

• • 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.

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


• • 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.

Slack ships a time-off template that starts close to this. Pair it with an out-of-office status on the days themselves.

4. IT or help desk request

• • 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.

5. Emoji escalation

• • 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.

Anyone can escalate with one click, and the on-call channel gets a clean feed.

6. Keyword routing

• • Trigger: When a message containing "refund" is posted in #sales.
• • Steps: Send a message to #finance with the message link.

Keep the keyword list short. A broad keyword fires on every casual mention.

7. Incident channel

• • 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.

8. Weekly meeting agenda

• • 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.

9. Feature requests into a spreadsheet

• • 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.

Connector steps need an account connected to the other service, and your admins may need to approve the connector first.

10. Kudos board

• • 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.

11. Tell the requester when a list item is done

• • 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.

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

• • Trigger: From a webhook, with text variables such as service, severity and description.
• • Steps: Send a message to #alerts that uses the three variables.

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.

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

In Workflow Builder, New offers templates next to Build Workflow. A template fills in the trigger and steps and you edit the details before publishing. Start from a template when one is close, such as the time-off request, and build from scratch for anything with your own form fields or branches.

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

Where is Workflow Builder in Slack?

On desktop, click Agents & tools in the sidebar, then Workflows. If you do not see it, look for Tools, which may sit under More.

Can a workflow run on a schedule?

Yes. Choose On a schedule as the trigger and set the date, time and how often it repeats.

Can Workflow Builder use if/then logic?

Yes, through branches that route on a value from an earlier step.

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 input in Slack, and no workflow step makes you active. To set a status from code, see set Slack status with the API.