Recharge

Automate recurring revenue operations in Recharge. Agents create, update, and cancel customer subscriptions, look up upcoming and historical charges for reconciliation and retention workflows, and browse subscription-enabled products.

9 actions API key available

Recharge website ↗ Platform Documentation ↗ Capability data verified 2026-07-28

The daily billing reconciliation sweep kicks off before the support team's shift

List Charges pulls yesterday's charges filtered by status: successful, queued, refunded, errored

Errored charges are enriched with Get Customer and Get Subscription so each failure carries its full context

The agent separates transient card declines from structural failures like expired payment methods and dead addresses

The reconciliation report lands in the finance channel, with errored charges grouped by cause and revenue at risk totaled

The retention lead reviews the at-risk list and decides who gets a dunning email, who gets a personal call, and whose subscription gets paused

The approved retention actions execute, and outcomes are logged against each subscription for next week's review

What This Integration Enables

Subscription commerce lives or dies on operations nobody sees: the charge that retries, the address that changes, the quantity bump that happens before the next billing date instead of after. Recharge holds all of that state, and this connector puts it under agent control. FlowRunner agents create, update, and cancel subscriptions, look up customers and their charge history, reconcile billing by status, and browse the subscription-enabled catalog, so recurring revenue operations become flows instead of ticket queues. The position: in a subscription business, the billing engine is the business, and automation against it should be graded by one standard, whether every dollar movement it causes was intended. That standard is why the write operations here run under review. - Enroll customers into recurring charge schedules from order and CRM events - Update quantity, price, and charge interval on existing subscriptions - Cancel with structured reasons that feed churn reporting - Reconcile successful, queued, refunded, and errored charges daily - Drive retention workflows from upcoming charges and payment failures

Without FlowRunner

Churn discovered at month end Failed charges pile up quietly, and the revenue impact surfaces in the MRR report weeks after the cards declined

Subscription changes queue behind support Every pause, quantity change, and plan tweak is a ticket waiting for someone with admin access

Reconciliation by export Matching charges to bank deposits means downloading CSVs and building the same spreadsheet every week

With FlowRunner

Failed charges triaged daily Errored billing is grouped by cause and in front of the retention team the next morning, while the customer is still recoverable

Changes flow from the systems customers touch App events, forms, and CRM triggers drive subscription updates through governed flows, with review where money moves

Reconciliation as a standing report Charges stream into the finance sheet by status every day, and the deltas are the only thing a human reads

Use Case Scenarios

Recurring enrollment from the storefront

A [Shopify](/integrations/shopify) order comes in for a subscription-eligible product. The agent resolves the customer with List Customers by email, verifies the product's subscription settings via List Products, and stages a Create Subscription with the address ID, product, price, interval, and first charge date. The retention lead approves the enrollment terms, the subscription is created, and the fulfillment team gets the new recurring order and next charge date in [Slack](/integrations/slack). Every enrollment is intentional, priced correctly, and visible to the people who ship it.

The churn interception flow

When a cancellation request arrives through support, the agent pulls Get Subscription and the customer's charge history, then presents the retention lead with context: tenure, order count, the stated reason. If a save offer applies, an Update Subscription with a pause-length interval or reduced quantity goes out for approval instead. If the customer's decision is final, Cancel Subscription executes with the structured reason Recharge requires, and [Klaviyo](/integrations/klaviyo) records the churn event and enrolls the win-back flow. Every cancellation carries a reason code, so the churn report stops saying "other."

The finance feed that ends CSV Fridays

Each morning, List Charges streams the previous day's billing by status into [Google Sheets](/integrations/google-sheets): successful totals for the revenue line, queued charges for the cash forecast, refunds and errors itemized. Week over week, the same flow computes recovery rates on retried charges. Finance reads a live reconciliation instead of building one, and the CFO's MRR number stops being a surprise assembled at month end.

Human-in-Loop Highlight

Create Subscription enrolls a real payment method into a recurring charge schedule: Recharge bills the customer on the first charge date and keeps billing every interval after, so a wrong price, a doubled quantity, or a misread interval does not produce one bad charge, it produces a repeating one, discovered by the customer on their statement. Cancel Subscription is the same weight in reverse, ending a revenue stream and, for the customer, a delivery they may be counting on. FlowRunner flows therefore put a person on both edges of the subscription lifecycle: enrollments and cancellations are staged by the agent with full context, customer, terms, history, reason, and released by the retention lead through a [human-in-the-loop](/concepts/human-in-the-loop) step. Update Subscription changes that touch price follow the same path. Lookups, reconciliation, and reporting run unattended all day, because reading the billing engine is safe. Changing what it charges a customer's card is a decision with a name attached.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

9 actions

Subscriptions

List Subscriptions Retrieves a paginated list of subscriptions, filterable by customer, address, or status: active, cancelled, expired. Each includes product, quantity, price, and charge interval. Cursor-based pagination via next_cursor.
Get Subscription Retrieves a single subscription's full details by ID: customer, shipping address, product, quantity, price, charge interval, and next scheduled charge date. The context call behind support and retention flows.
Create Subscription Creates a new subscription for a customer's shipping address, with product details, recurring charge interval, and first charge date. Recharge bills on next_charge_scheduled_at and repeats every interval. The enrollment write this page's human gate governs.
Update Subscription Updates a subscription's mutable fields, quantity, price, product title, or charge interval. Only provided fields change. Changing the next charge date goes through Recharge's dedicated set-next-charge-date endpoint, not this update.
Cancel Subscription Cancels an active subscription so no further charges are created. Requires a cancellation reason for reporting, with an optional comment. The record is retained in cancelled status for history.

Customers

List Customers Retrieves a paginated list of customers, filterable by email, each with name, email, Shopify customer ID, and subscription and charge counts.
Get Customer Retrieves a single customer's full details by Recharge customer ID, including billing and analytics counts and timestamps.

Charges

List Charges Retrieves a paginated list of charges, upcoming, queued, or historical, filterable by customer or status, each with total, line items, scheduled date, and processing status. The backbone of reconciliation and dunning flows.

Products

List Products Retrieves a paginated list of subscription-enabled products, each with title, Shopify product ID, and available subscription and discount settings. The catalog check before enrollments and upsells.

Frequently Asked Questions

What can FlowRunner do with Recharge?

FlowRunner agents can run List Subscriptions, Get Subscription, and Create Subscription in Recharge, plus 6 more actions.

Does connecting Recharge to FlowRunner require OAuth?

No. Recharge connects to FlowRunner with an API key, no OAuth flow required.

Can Recharge trigger a FlowRunner workflow automatically?

Recharge doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Recharge

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us