Gorgias Flows Explained (2026): Self-Service Automation

What a Flow actually is

Per the Gorgias Flows documentation, Flows are "automated Q&A conversation scenarios that operate across multiple channels and assist shoppers with personalized guides, answers, and recommendations." In plain terms: a Flow is a decision tree. You define a starting question, the buttons a shopper can tap, where each button leads, and how the conversation ends — a returns portal link, a tracking lookup, a handoff to a human.

Because they run before a ticket exists, Flows are Gorgias' first line of deflection. A well-built shipping-policy Flow answers the same WISMO-adjacent question a hundred times a day without an agent ever touching it. They are also multichannel: a Flow you build once can surface in the chat widget, the Help Center, and the contact form, so the customer meets it wherever they reach for help.

Inside the Flow Builder

The Flow Builder is a no-code visual canvas with a tree-type layout that reflects the multiple paths you can build for your customers, depending on the topic. You drag and connect blocks; the tree fans out as you add branches. The core building blocks are:

• Triggers — what starts the Flow (the entry point a shopper sees).
• Options — the decision branches. Each option is a button; each button routes to a different sub-path. This is where "Do you want to track an order or start a return?" splits into two entirely different conversations.
• Messages / Quick Responses — the text, links, and answers the Flow shows along the way.
• Ends — how a branch concludes: a link out, a resolved conversation, or an escalation to your team.

One practical detail from the Flow Builder docs: using Save on an incomplete Flow keeps it as a Draft, so it won't appear under Channels until you finish and publish it. That's your safety net for building live without exposing a half-finished tree to customers. The Gorgias Automate playbook also recommends keeping a Flow to around five steps — past that, drop-off climbs and shoppers bail to a human anyway.

Quick Responses: the one-step Flow

Not every question needs a tree. A Quick Response Flow is a one-step Flow that gives an instant answer to a frequently asked question — the shopper taps "Shipping times" and immediately gets your shipping-policy blurb, no branching required. Per Gorgias' Self-Service Quick Response Flows documentation, these are the fastest wins: high-volume, low-complexity FAQs (returns window, sizing, order cutoff times) resolved in a single tap. Gorgias Chat can surface up to six Flows at once in the widget, so most stores lead with their top six FAQ Quick Responses and reserve the multi-step trees for returns and order lookups.

Decision branches and the "Advanced" layer

Simple Flows are static: button in, canned answer out. But Flows can also do things. The Advanced step type opens an editor where a Flow can fire an HTTP request to an external API — the kind of app Gorgias doesn't natively integrate — capture the response, and store fields from it as JSONPath variables the rest of the Flow can reference. Gorgias' own examples include calling Klaviyo, LoyaltyLion, and Recharge.

That is genuinely powerful for a no-code tool: a returns Flow can ask for an order number, hit your returns platform's API, branch on whether the order is inside the returns window, and route accordingly — all inside the tree. It's also where the ceiling starts to show, which we'll get to. For the broader picture of how self-service, macros, and rules fit together in Gorgias, what Gorgias is and the self-service overview are the right primers; and because Flows live in the chat widget, how Gorgias Chat works is worth reading alongside this.

The gating nobody warns you about

Here is the part that surprises teams evaluating Gorgias. Flows are gated to the Automate / Automation Add-On subscription — they are not part of the base help desk. And the wider AI Agent product that houses Automate Flows is Shopify-only. On a fresh Gorgias trial without a connected store, navigating to the AI Agent / Flows area doesn't open the builder at all — it hits an enablement wall reading "You don't have a store connected… AI Agent is currently available only with Shopify," with a Connect My Shopify Store button. That's exactly the screen shown above: not a flow canvas, but the honest gate you'll meet if you're on BigCommerce, Magento, WooCommerce, or simply haven't connected a store yet.

So before you plan a self-service strategy around Flows, confirm two things: (1) you're on a plan/add-on that includes Automate, and (2) your store is Shopify and connected. Both are documented, but neither is obvious from the marketing.

Where Flows stop

Flows are genuinely good at what they're for, and it's worth crediting that clearly: for high-volume, predictable questions, a well-built Flow is fast, cheap, and deterministic — the customer gets an answer in one tap and you never pay an agent for it. Keep them. But a decision tree is, by definition, a tree you drew in advance, and that's the seam where it runs out of road:

• It only answers what you scripted. A Flow can't reason about a question you didn't anticipate. Anything off the branch falls through to a human or a dead end.
• Free-text questions don't fit buttons. Shoppers who type "the sweater I ordered last Tuesday came with a hole and I need a replacement before the weekend" aren't going to tap through a six-button tree.
• Every real integration is a hand-built HTTP step. Powerful, yes — but you're wiring, testing, and maintaining API calls and JSONPath variables by hand, per Flow.
• The Shopify + Automate gate is real. If your stack isn't Shopify, the richest Flows (order actions, returns) simply aren't available to you.

There's also a billing shape worth knowing. Gorgias' AI automation is billed per resolved interaction — roughly $1.00 per automated interaction on monthly plans (about $0.90 annual), and per Gorgias' own model each AI Agent interaction also counts as a help desk ticket and is billed as one. That's a fair way to price outcomes, but it means every automated conversation carries a per-interaction and a per-ticket cost.

Where an AI agent layer fits — on top of Flows, not instead

This is exactly the seam an AI agent layer is built for, and it's worth being clear-eyed about the whole AI-agents-for-customer-service category before reaching for one. Macha is one such layer: it runs on top of the Gorgias you already use through the live Macha↔Gorgias connector — it does not replace Gorgias, your Flows, or your help desk. Keep your Quick Response Flows deflecting the top FAQs at the widget; let Macha's agents take the free-text, reasoning-heavy tickets that fall off the tree — the customer with the damaged sweater, the multi-part subscription question, the WISMO that needs a real order lookup.

Two honest contrasts matter here. First, integrations: instead of hand-wiring an HTTP step per Flow, Macha reaches your systems through a custom tool that turns a REST API into something an agent can call and reason over. Second, billing: Macha's credits are consumed per AI action, not per resolution or per interaction — a genuinely different model from Gorgias' per-interaction AI pricing, and one that doesn't double-charge a conversation as both an "interaction" and a "ticket" (the full breakdown is on the pricing page). If you want the mechanics of connecting the two, the Macha–Gorgias integration guide and the Gorgias AI Agent explainer go deeper, and the Gorgias pricing breakdown covers the add-on math.

The clean division of labour: Flows own the predictable, button-shaped deflection at the front door; an AI agent layer owns the messy, free-text, integration-heavy work the tree can't reach. You don't pick one — you stack them.

FAQ

What are Gorgias Flows? Flows are automated, click-through Q&A conversations you build in Gorgias' no-code Flow Builder. A shopper taps a button, follows a decision branch, and reaches a scripted resolution — a returns link, a tracking lookup, or a handoff — usually in the chat widget, Help Center, or contact form, before a ticket is ever created.

Where do I build a Flow in Gorgias? In the Automate / AI Agent area under Flows, using the visual Flow Builder — a tree-layout canvas of Triggers, Options (decision branches), Messages/Quick Responses, and Ends. Saving an incomplete Flow keeps it as a Draft, so it won't go live under Channels until you publish it.

Do Gorgias Flows require an add-on or Shopify? Yes on both counts. Flows are gated to the Automate / Automation Add-On subscription, and the wider AI Agent product that houses them is Shopify-only — on a store-less or non-Shopify account you'll hit an enablement wall ("AI Agent is currently available only with Shopify") instead of the builder. Confirm your plan and store before planning around Flows.

What's the difference between a Flow and a Quick Response? A Quick Response is a one-step Flow: tap once, get an instant FAQ answer (shipping times, returns window). A full Flow is a multi-step decision tree with branching. Gorgias Chat can surface up to six Flows at once, so most stores lead with Quick Responses and reserve trees for returns and order lookups.

Can I add AI to Gorgias without replacing it? Yes. An AI agent layer like Macha connects to Gorgias through the live native connector and runs on top of your existing help desk and Flows — it doesn't replace them. Flows keep deflecting the predictable FAQs; Macha handles the free-text, reasoning-heavy tickets that fall off the tree, with credits billed per AI action rather than per resolution.

Ready to layer AI on top of your Gorgias Flows instead of rebuilding them? Start a free trial of Macha and connect it to your Gorgias in minutes.