What we do
Tools
Industries
Department
How we workLet's talk →
Home/Slack/Slack Workflow Builder
Slack

How to Build a Slack Workflow, and When the Builder Runs Short

Every Slack workflow is one trigger followed by a list of steps. You build it in Workflow Builder, which comes with every paid Slack plan, by clicking, with no code. Most teams can do this themselves in an afternoon. Here's the route, the triggers worth knowing, why a workflow sometimes won't start, and the few jobs that need more than the builder.

Getting into the builder

Find it: on desktop, open Agents & tools in the sidebar and go to Workflows. Some workspaces still label it Automations.

Agents & tools Workflows

Start: pick a template if one is close to what you want, or start from scratch and choose the event that kicks it off.

Plan check: Workflow Builder is on Pro, Business+ and Enterprise. A free workspace doesn't get it, and branching needs the new Business+ or above.

A request-and-approve workflow, start to finish

This is the one most teams build first: someone asks for something, a manager says yes or no, and the requester hears back.

  1. 1

    Choose a link trigger

    A link trigger gives you a URL you can pin in a channel or bookmark. Anyone who clicks it starts the workflow. It's the simplest way to make a request button people can find.

  2. 2

    Collect the details in a form

    Add a form step with the questions the approver needs: what, how much, by when. Make the fields required where a missing answer would stall the decision.

  3. 3

    Send the approver a message with buttons

    Post to the manager, or to a private approvals channel, with the form answers dropped into the message as variables. Add buttons for approve and deny.

  4. 4

    Branch on the button they press

    Add step Utilities Add a branch

    Give each button its own branch. One tells the requester it's approved and posts to the team channel, the other sends a short note asking for changes. You can have up to 15 branches, with up to 5 more nested under a main branch.

    Watch for: branching needs the new Business+ plan or above. On Pro, send both outcomes as separate messages and let the approver's reply do the routing.

  5. 5

    Publish and test as someone else

    Publish, then ask a colleague to run it. Testing as the builder hides permission problems, like a channel the requester can't post in.

Which trigger to start from

Starts when Good for Watch for
Someone clicks a link or shortcut Requests, reports, sign-ups: anything a person starts on purpose. People can't use a link they can't find. Pin it or bookmark it in the channel where the request belongs.
A set time comes round Stand-up prompts, weekly check-ins, end-of-month reminders. The schedule follows the time zone set on the trigger, which may not be yours.
Someone adds an emoji reaction Turning a message into a ticket or flagging it for a lead, without anyone leaving the thread. It only listens in the channel you picked, and only for that exact emoji.
A person joins a channel Welcome notes, house rules, an intro form for new clients or staff. Busy public channels get a lot of joins. Keep the message short or it reads as spam.
A channel is created Naming checks and standard bookmarks on every new project channel. It fires for every new channel, so add a branch if it should only act on some of them.
Another service calls a webhook Letting a form tool, CRM or script start the workflow with a few values. The sender has to include every variable the workflow expects, or that run fails. See Slack webhooks for the two kinds.

Why a Slack workflow won't start, or stops halfway

It was never published, or was edited and left as a draft

How you'll know: You see your change in the builder but people still get the old version.

Fix: Changes only go live when you publish again. Open the workflow and check whether it's waiting on a publish.

The trigger is narrower than its name

How you'll know: An emoji workflow ignores reactions in the next channel over, or a scheduled one runs an hour early.

Fix: Open the trigger and read its settings, not its title: which channel, which emoji, which time zone.

A connector step was never approved

How you'll know: The Jira, Google Sheets or Salesforce step fails for everyone except you.

Fix: Connector steps run with a signed-in account, and an admin may have to approve the connector first. Check the workspace's app settings and the account each step uses.

The person running it isn't allowed to

How you'll know: New starters or shift staff say the link does nothing.

Fix: Frontline Members can't build workflows by default, and a workflow that posts to a private channel fails for anyone who isn't in it. Check their account type and channel membership before rebuilding anything.

What the builder reaches, and what it leaves out

Before going custom, check the connector steps. Slack lists 70+ apps, including Jira, Salesforce and Google Sheets, so a lot of "write this to that system" work is already a menu item. There's also an AI step that drafts an answer from Slack content you point it at.

The gaps show up in two places. First, your own systems: a job board, an ERP, a booking tool or a homegrown database that Slack has no connector for. A workflow can't check stock or a customer's balance in one of those before the approver sees the request. Second, time: each run stands alone, so a process that waits days for a second approval, or depends on what an earlier run decided, has nowhere to keep that state.

Both are solved with a custom step. A developer writes it with Slack's tools, it appears in the builder's step list, and your team keeps arranging the workflow around it without code. n-frames builds and hosts these custom steps for teams who want the workflow in Slack and the logic behind it looked after.

Questions people ask

Is Slack Workflow Builder free?

It costs nothing extra on a paid plan. Pro, Business+ and Enterprise all include it. The free Slack plan doesn't, and some parts, like branching, need the new Business+ plan or higher. Connector steps may also need a paid account in the other app.

Can a Slack workflow call an outside API?

Through connector steps, yes, for the apps Slack supports. For a system without a connector, a developer can build a custom step that calls its API and returns values to the workflow. Going the other way, a webhook trigger lets an outside system start a workflow.

What's the difference between a Slack workflow and a bot built on the API?

A workflow is assembled from Slack's triggers and steps, so anyone can change it later. A bot is code on the Web API and Events API that can do whatever you program, but somebody has to maintain it. Custom steps sit between the two, and the bot route is laid out on our Slack API page.

Can I build an approval workflow in Slack?

Yes. A form collects the request, a message with buttons goes to the approver, and on Business+ or above a branch sends each answer down its own path. Slack also has approval templates to start from. What it can't do alone is check a budget or stock figure held in another system before asking.

Why isn't my Slack workflow triggering the way I expected?

Usually the trigger is set more narrowly than you think (one channel, one emoji, a different time zone), the latest edit wasn't published, or a connector step hasn't been approved by an admin. Open the trigger settings first.

How many branches can a Slack workflow have?

Up to 15, and you can nest up to 5 more under a main branch, but not deeper than that. Branches can split on earlier answers, such as which button someone clicked or what they chose in a form.

Who can build a custom step for Slack Workflow Builder?

Any developer comfortable with Slack's platform. n-frames builds custom steps that look things up in a business's own systems (orders, jobs, stock, balances) and keeps them running, so the workflow stays editable by your team in the builder.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.