Each workflow pairs a Shopify or Gorgias trigger with a record that sends the SOP behind it back for review.
The most useful Slack Workflow Builder examples for a Shopify store are small ones. Think refund approvals, support escalations, high-risk order claims, seasonal hire intake, a scheduled ops check, a variance form, and a flag for "this step changed." None of the seven needs code.
One rule makes them worth keeping. Every workflow should write a decision record, and that record should prompt a re-check of the SOP behind it. Workflows drift quietly. When a step inside Gorgias or Shopify changes, the automation keeps firing and the written procedure stops being true.
One thing to know first: Workflow Builder is a paid Slack feature, included in the Pro, Business+ and Enterprise subscriptions.
Slack Workflow Builder is Slack's built-in, no-code automation tool. A workflow starts from a trigger, then runs the steps chosen for it, in order.
A workflow can start in several ways. Someone clicks a link inside Slack, a schedule comes round, a message with a keyword is posted, someone joins a channel, or someone adds an emoji reaction. A step can send a message inside Slack. Through a connector, it can also act in an outside tool such as Google Sheets.
Two building blocks matter for record-keeping. A variable can carry the name of whoever started the workflow into a later step, so an approval gets a name attached to it. A button pauses the workflow until someone clicks it. That turns a decision into something logged, not just discussed in a thread.
Whoever sets up a step that posts to a channel needs posting permission in that channel. By default, any Full Member except a Frontline Member can build a workflow, and owners or admins can narrow that to certain people or groups. The person who builds a workflow becomes its manager automatically and can add others.
Slack's own feature page says "80% of those who build Slack workflows are non-technical", citing its internal data. Treat Workflow Builder as an ops tool, not an engineering project.
Each example below names the trigger, the steps, where the record lands, and what should send you back to the procedure it automates.
Trigger: a link pinned in the support channel. Steps: a form for order number, amount and reason, then a branch on the amount, a button for the approver, and a step that adds a row to a sheet. Slack supports conditional logic with up to 15 conditions, so one workflow can hold several approval tiers.
The record is the sheet row: date, requester, amount, approver. When the refund threshold moves, re-check the SOP the same day, because the branch has to move with it. The refund processing SOP for the Gorgias to Shopify handoff covers what the procedure itself should say.
The refund procedure behind the approval workflow: who can approve what, and how the Gorgias and Shopify steps line up.
Gorgias is not one of Slack's built-in connectors, and its Slack help article offers two ways in. The first is an incoming webhook used in a Gorgias HTTP integration. Gorgias says that route posts every incoming ticket, "regardless of the Channel or Tags used". That is a firehose, not an escalation feed.
The second route can filter, so use it here. Slack gives each channel its own email address. A Gorgias Rule, for example one that fires when a ticket is tagged "escalation", can send an email to that address. The message lands in the channel only for the tickets the rule picks.
Then add a Slack workflow on an emoji reaction in that channel. Whoever reacts claims the ticket, and the workflow posts their name and adds a row to a sheet. One catch from Gorgias's own community tips: replies in Slack stay in Slack. Whoever answers still has to open Gorgias to reply to the customer. The procedures behind Gorgias macros and tags are worth writing down on their own, which Gorgias SOPs covers.
Shopify recommends reviewing high-risk orders against its fraud analysis before you fulfill them, and using Shopify Flow to automate how those orders are handled. Keep Flow for the holds, as the Shopify fraud prevention SOP sets out. Flow also has a built-in "Send Slack message" action, once Flow is connected to your Slack account, so it can post each high-risk order to an orders channel.
The Slack workflow only records who made the call. Trigger: an emoji reaction in the orders channel. An agent reacts to claim the review. The workflow posts who claimed it, then sends a form with hold, cancel or fulfill and a one-line reason. The record is the form response and the posted claim. Re-check the fraud SOP once the reason codes in that form stop matching what people actually pick.
Trigger: someone joining a channel. Steps: a message listing the three procedures they need first, then a form they submit after running one of them. The form asks what they did and where they got stuck. That answer is evidence they ran the task, which a welcome message alone never gives you. The knowledge transfer plan template for Shopify teams covers what a new hire's handover should include.
Trigger: a schedule, set to a date, time and cadence, so it starts without anyone remembering to run it. Steps: post the week's checks to the ops channel, then collect one form response per check. The record is the form data. This is the workflow most likely to turn into theater, so keep it to checks someone actually acts on the same morning.
Trigger: a link in your fulfillment channel. Steps: a form for SKU, expected count, counted number and location, then a Google Sheets step that writes the row. The sheet matters because form data is easy to lose track of. Only the workflow's creator and managers can download form responses, and an admin can switch that download off for the workspace. A sheet row stays readable either way.
Trigger: an emoji reaction you choose, used in a channel you pick when you build the workflow. One step: add a row to a drift queue sheet with the flagged message, who flagged it and the date. This is the cheapest workflow on the list, and it keeps the other six honest. Anyone who notices that a screen or a rule has moved reacts with the emoji, and the row lands in the queue.
Because the thread will not hold it. A decision record is a short, permanent note of what was decided, by whom, on what date, and under which version of the procedure. A channel message announces a decision. It is not a record of one.
Workflow Builder gives three places to put the output, and they are not equal:
| Where the output lands | What it is good for | What it loses |
|---|---|---|
| Channel message | Fast visibility, who started it | Scrolls away; nothing to query later |
| Form responses | Structured answers | Download may be switched off by an admin |
| Sheet row (connector step) | One queryable line per decision, kept outside Slack | Needs the third-party account authenticated before the step can run |
A sheet row works well because a workflow step can write straight to a spreadsheet. One row per decision is enough: date, order or ticket, amount, decider, SOP version.
That last field is the one teams skip. Add the procedure version as a column the workflow fills in, so every record states which version of the rules the decider followed. Weeks later, that is the difference between an audit trail and a guess.
Slack itself is still not where the procedure should live. The SOP version control post covers what a version diff should show. Moving SOPs off Google Docs and Slack covers what to require from wherever your SOPs actually live. A workflow record feeds that system. It is not the system.
Try it on one of your own procedures.
Record a process once, AI writes the structured SOP. 3 free SOPs, no credit card.
Connector steps are the fragile part. Slack needs the third-party account authenticated before a connector step can run. A native Slack step, like sending a message, keeps working. The Gorgias bridge from example 2 is fragile in its own way, because it depends on a Gorgias Rule nobody in Slack can see.
Two failure modes worth watching:
Slack's activity view shows which workflow runs finished, which are still running, and which hit an error. Check it when a sheet goes quiet.
Give the workflow the same owner as the SOP it automates. The owner is a person, not a role, and that person should be a manager on the workflow itself. The builder becomes a manager automatically, so add the SOP owner yourself when someone else built it.
Four signals worth acting on:
Neither Slack nor Shopify publishes a recommended cadence for this review. Our suggested starting point for a small ops team is monthly, adjusted once the queue shows how often rows actually arrive.
The re-check itself compares the live procedure against the written one. A workflow record gives that check its dates; it does not do the comparison. The gap between the two has a name, SOP drift, and every dated decision a workflow logs makes it faster to find.
ReccordSOP is built for that comparison. Record your screen doing the task, and it turns the recording into a step-by-step SOP with a screenshot for each step. Re-record the same task later, and it shows which steps changed instead of overwriting the old version. It documents a process; it does not run the process, watch your store settings, or make decisions for you.
Build example 7 first. The emoji flag that writes a row to a drift queue needs nothing beyond a spreadsheet, and it starts collecting evidence about which procedures are already wrong. Then build the refund approval, because that is the one where a stale threshold costs real money.
Read the queue after two weeks. Every row points at an SOP worth a second look.
Slack Workflow Builder is Slack's built-in, no-code automation tool. Each workflow begins with a trigger and then runs the steps set up for it. A trigger can be a link clicked inside Slack, a schedule, a message containing a keyword, someone joining a channel, or an emoji reaction. Steps can act inside Slack or, through a connector, in a third-party service such as Google Sheets.
No. Slack includes Workflow Builder as a paid feature in its Pro, Business+ and Enterprise subscriptions. On those plans, any Full Member except a Frontline Member can build workflows by default, and owners or admins can limit that to certain people or groups.
Yes, but the data is pushed in from the other side. Shopify Flow, a free Shopify app, has a built-in Send Slack message action that can post orders and alerts to a channel. Gorgias can post through an incoming webhook, which sends every new ticket, or through a Gorgias Rule that emails a Slack channel only when its conditions match. A Slack workflow can then react to those messages.
A workflow that starts from a link can only be started from inside Slack. Clicked anywhere outside Slack, the link won't work. A process that needs to start from outside Slack should use the webhook trigger, which Slack describes as the way to let external events start a workflow. Owners and admins can restrict who may create webhook workflows.
3 free SOPs to start. No credit card required. See if drift detection keeps your docs honest.
Start for freeI built ReccordSOP after watching too many DTC ops teams lose months to undocumented workflows. These SOPs are battle-tested with Shopify operators running $1M to $50M brands.
Last reviewed November 5, 2026
A refund starts in your helpdesk and ends in your store. The seam between them is where refund procedures quietly break.
Not a guide to copying files. A checklist for what the next system has to do that the free ones never did.
A Flow tagging rule rarely breaks inside the workflow. It breaks in the filter, app or macro that reads the tag. Here is what to write down so the rule stays true.
We use essential cookies for sign-in and a small amount of analytics to improve the product. Privacy policy.