Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

My Slack workflow does not run or cannot do what I need

Short answer

Workflow Builder starts from a link, a schedule or Slack actions such as an emoji reaction or joining a channel, and it is available on paid plans. If a workflow does not run, check who may use it, whether connector steps need approval or sign-in, and who manages it. Complex branching or data work may outgrow it.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • The workflow never starts, or only for some people.
  • A step asks for approval or a sign-in nobody completes.
  • The person who built it left, and nobody can edit it.
  • I need conditions, loops or data from another system.
  • It posted for a while, then stopped.

Why does this happen?

  1. The trigger is not what people expect

    Slack documents three kinds of start: a link anyone can click or share, a set schedule, and Slack actions such as an emoji reaction, joining a channel or creating a channel. A workflow set to one of these will not run on another.

  2. Access is restricted

    By default Full Members can create workflows, members and guests can use them, and Frontline Members are excluded from building. Admins can control access to Workflow Builder and which features members may use.

  3. Connector steps need approval or sign-in

    Slack says connector steps may need app approval or account authentication before use, and admins manage which connector steps and custom steps members can add.

  4. Nobody manages the workflow

    After publishing, the creator and any workflow managers can view activity, edit or delete the workflow and change who can use it. Slack's article does not describe a transfer of ownership, so a workflow with no active manager can become stuck.

  5. The job is bigger than a no-code builder

    Workflows that must read and write records in other systems, handle errors, retry or branch in detail are easier to test and log in code. This is a design judgment, not a Slack limit.

What can I do about it today?

  1. Open the workflow's activityA manager can view it. See whether it ran, when it last ran and where it stopped.
  2. Check who can use itConfirm the people trying it are allowed, and that guests or external users are not the missing piece.
  3. Look for steps waiting on approvalIf a connector step needs an admin or a sign-in, finish it. Ask your Slack admin instead of sharing logins.
  4. Add a second managerIf the creator is the only manager, add another so it survives a departure.
  5. Write down what it should doA short plain list of inputs, steps and outputs. It shows whether you need a bigger tool.

When should I bring someone in?

  • The workflow has to update other systems reliably.
  • You need approvals, retries, logs or conditions Workflow Builder does not give you.
  • The only person who knew it has left.

How do I handle it?

  1. Read the workflow, not the memory of itI list its trigger, steps, who can use it and who manages it.
  2. Confirm the cause on the Slack side firstAccess, approval and ownership are checked before anything is rebuilt.
  3. Keep simple workflows where they areA reminder or a form is fine in Workflow Builder. I leave those alone.
  4. Describe the code option plainlyFor heavy flows I describe what a small Slack app with logs and tests would do, and what it would cost you to own it, so you can decide.
  5. Hand over with an ownerWhatever the choice, it ends with a named owner and a short note.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Does Workflow Builder have a step limit?

Slack's article does not state numeric limits such as step counts or run quotas. Check your own workspace's documentation or admin.

Can I transfer a workflow to another person?

Slack's article does not describe transferring ownership. It does say workflow managers can be added or removed.

When should I stop using it?

When the workflow must work reliably with other systems, with retries, logs and tests, a small coded app is easier to maintain.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.