How to Integrate Recharge with Gorgias (Subscriptions)
Subscription support is its own genre of ticket. A shopper doesn't want to know where their one-off order is — they want to skip next month's box, swap the coffee they're bored of for the darker roast, push their charge date back a week, or cancel before Friday's billing run. Every one of those requests lives in Recharge, but the conversation lives in Gorgias, and if your agents have to bounce between two tabs to answer, handle time balloons and mistakes creep in. The Recharge integration for Gorgias pulls a customer's subscriptions straight into the ticket sidebar and lets agents act on them without leaving the conversation. This guide covers the real setup steps, exactly what syncs, which actions you get from a ticket, and where the native app runs out of road.
What the Recharge integration actually does
Recharge is the recurring-billing engine behind a huge share of Shopify subscription brands, and Gorgias is where those brands answer email, chat, and social tickets. Connecting the two does one core thing: it renders a Recharge widget in the Gorgias ticket sidebar, alongside the Shopify customer card, so the person answering the ticket can see the subscriber's state and change it in place.
Per the official Gorgias Recharge documentation, once connected the sidebar surfaces a customer's active subscriptions, their subscription details and status, the scheduled charge dates, and the underlying Recharge account information — all keyed to the same customer the ticket is already about. It also exposes macro variables, so a saved reply can drop the customer's actual next charge date or product into the response instead of a placeholder. If you're new to how that side panel is assembled from connected apps, the Gorgias customer sidebar explained is a good primer.
Before you start: the Shopify prerequisite
The single most important thing to know before you begin is that the Recharge integration requires an active Shopify store connection. Recharge sits on top of Shopify checkout, and Gorgias authenticates the Recharge widget by first selecting the Shopify store the subscriptions belong to. If your Gorgias account isn't already connected to Shopify, set up the Gorgias-Shopify integration first — the Recharge connect flow will ask you to pick that store partway through.
Step 1: Connect Recharge from the Gorgias App Store
The integration installs from inside Gorgias — you don't start in Recharge. Following the connection steps in the Gorgias docs:
- In Gorgias, go to Settings → App Store → All Apps.
- Search for "Recharge" and select it from the results.
- On the app page, click Connect App.
- When prompted, select your Shopify store — the same store your subscriptions run on.
- Complete the Shopify login authentication to authorize the connection.
That last handshake is what links Gorgias to the right Recharge account through Shopify. When it finishes, the Recharge widget starts appearing in the sidebar for any ticket where Gorgias can match the customer.
The screen above is the connect page — the App Store entry with the Connect button and the Shopify prompt — not a ticket with live subscription data. The populated widget only renders once the Shopify handshake completes and a real subscriber's ticket is open, which needs a connected store this walkthrough environment doesn't have. What follows describes what that widget shows and does, drawn from the Gorgias documentation.
Step 2: Configure what the sidebar widget shows
Once connected, you tune the widget rather than accept the default. In the ticket view, the Recharge widget sits in the right-hand sidebar; click the cog / gear icon at the top-right of the sidebar to open its settings. From there you decide which fields are visible and in what order — active subscriptions up top, charge dates and status beneath, order history collapsible. The goal is to put the two or three data points an agent needs for the most common request (next charge date, product, subscription status) above the fold, so nobody scrolls to answer a skip request.
Step 3: Enable the actions agents run from a ticket
Viewing data is half the value; the other half is acting on it without opening Recharge in a second tab. From the Recharge widget, agents can perform the subscription changes that make up most subscription tickets:
- Skip the next order — the single most common request; one click and the shopper isn't charged for that cycle.
- Swap product or variant — flavor, size, or product switches for the upcoming order.
- Update the next charge date — push billing forward or back.
- Update the shipping address — for subscribers who've moved.
- Cancel a subscription — with a cancellation reason captured, and reactivate to undo.
- Refund a charge — partial or full.
Two honesty notes straight from the Gorgias Recharge docs that will save you a support headache. First, the refund action only appears on orders, not subscriptions, and only works if the order was processed through the Recharge checkout — orders fulfilled at checkout must be refunded or canceled via Shopify instead. Second, an order that passed through Recharge must be canceled using the Recharge cancel action, not the Shopify one, or the cancellation won't take. Train agents on those two rules and you avoid the classic "I clicked cancel and it didn't stick" ticket.
Step 4: Add Recharge data to your macros
Because the integration exposes macro variables, your saved replies can pull live subscription context. A "your next box is on the way" macro can insert the customer's real next charge date; a churn-save macro can reference the exact product and price they're on. This is the difference between a template that reads like a form letter and one that reads like the agent already looked. Build these once and every subscription reply gets faster and more accurate.
AI Agent Actions — and the single-subscription limit
Gorgias also ships native AI Agent Actions for Recharge, which let its automation handle two subscription tasks end-to-end. Per the Gorgias AI Agent Action docs, those are Cancel Subscription (with reason collection) and Skip Shipment (which only works before the next order is created). You enable them in AI Agent settings → Support Actions templates, select Recharge as the app, and click Create and Enable — no extra integration setup beyond the connection you already made.
There's a real ceiling here worth flagging: the Gorgias AI Agent can only skip or cancel if the shopper has a single subscription. The moment a customer has multiple subscriptions, the automation escalates the ticket to a human rather than guessing which one to touch. For a coffee brand where everyone's on one plan that's fine; for a supplement brand where regulars stack three or four subscriptions, a large slice of exactly the tickets you hoped to automate will fall back to your agents.
The honest limits — and where an AI layer picks up
Give the native integration its due: it's the right foundation, it's built and maintained by Gorgias and Recharge, and having subscription data plus real actions in the sidebar genuinely cuts handle time. It belongs on any shortlist of the best Gorgias integrations for subscription brands. But notice the seams.
The widget shows and executes — an agent still has to read the ticket, decide it's a skip request, find the right subscription, and click. On the automation side, the built-in AI Actions cover cancel and skip but stop at a single subscription, and they don't reach the trickier subscription conversations — the "why was I charged twice," the swap that depends on inventory, the WISMO on a subscription order, the retention reply that needs a real reason, not a dropdown. Those still land on a person.
This is the seam where an AI agent layer on top of Gorgias fits. The broader category of AI agents for customer service exists to do the reasoning a sidebar widget can't. Macha is one such layer: it connects to the Gorgias you already use as a native connector and works on the same tickets — it does not replace Gorgias, Recharge, or the native widget. Macha reads a subscriber's Recharge context, understands intent (skip vs swap vs cancel vs "where's my order"), and drafts or sends a grounded reply — including for customers with multiple subscriptions, where the native AI Action bows out. Where it needs to actually change a subscription or fetch live data, a custom tool turns the Recharge or Shopify API into something the agent can call. Credits are consumed per AI action, not per resolution — see the pricing breakdown for how that works.
The clean division of labour: keep Recharge as the system of record for subscriptions and Gorgias as the place tickets live, and layer an agent on top for the reasoning-and-writing work the widget leaves to humans. If you're still deciding whether Gorgias is the right desk underneath all this, what is Gorgias covers the platform end to end.
FAQ
How do I connect Recharge to Gorgias? In Gorgias, go to Settings → App Store → All Apps, search for Recharge, click Connect App, select your Shopify store, and complete the Shopify login. The Recharge widget then appears in the ticket sidebar.
Do I need Shopify connected first? Yes. The Recharge integration requires an active Shopify store connection — the connect flow asks you to select your Shopify store as part of authentication, because Recharge sits on top of Shopify checkout.
What can agents do with Recharge from a Gorgias ticket? Skip the next order, swap a product or variant, update the next charge date, update the shipping address, cancel (with a reason) and reactivate subscriptions, and refund charges. Note that refunds only apply to orders processed through the Recharge checkout, and Recharge orders must be canceled via the Recharge action, not Shopify.
Can Gorgias AI automatically cancel or skip a Recharge subscription? Yes, via native AI Agent Actions (Cancel Subscription and Skip Shipment), enabled under AI Agent settings → Support Actions. But the automation only works when the shopper has a single subscription — customers with multiple subscriptions are escalated to a human.
Can I add AI to Gorgias-plus-Recharge without replacing either? Yes. An AI agent layer like Macha connects to Gorgias as a native connector and runs on top of your existing helpdesk and the Recharge widget — it doesn't replace them. It reads subscription context, handles intent-based replies (including multi-subscription cases), and leaves Gorgias and Recharge as the systems of record.
Ready to let your team resolve subscription tickets instead of just clicking through them? Start a free trial of Macha and connect it to your Gorgias in minutes.
Add AI agents to your Gorgias
Macha resolves tickets end to end on Gorgias — no migration, no code.
Zendesk
Freshdesk
Gorgias
Front
Shopify
Stripe
Slack
Notion
Google Workspace
Confluence

