Recurly

Connect AI agents to Recurly subscription billing. Agents create accounts and subscriptions, cancel plans, and pull invoices and plan catalogs to keep billing operations and revenue reporting in sync.

10 actions Basic auth available

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

A signed order form arrives from the CRM with plan, quantity, and billing contact

Get Account checks whether the customer already exists by account code; Create Account provisions them if not

List Plans confirms the plan code and current pricing match what sales sold

The agent compares the order's terms against the plan's list pricing and flags any override

A pricing override or nonstandard quantity goes to the finance lead, who approves the exact unit amount before billing exists

Create Subscription attaches the plan to the account with the approved terms

The confirmation posts to the deal channel, and the CRM record gets the subscription ID written back

What This Integration Enables

Subscription billing is a state machine where every wrong transition invoices someone. Recurly runs the machine; FlowRunner agents operate it with the discipline recurring revenue deserves. On the read side, agents answer billing questions inside workflows, pulling accounts, subscriptions, invoices, and the plan catalog without a human logging in. On the write side, they provision accounts and subscriptions from signup and CRM events, and they cancel plans, the operation with the most direct revenue consequence in this connector, only through a gated path a person has confirmed. - Onboard customers by creating accounts and attaching subscriptions from signup forms and closed deals - Answer billing questions in support and finance workflows with account, subscription, and invoice lookups - Export invoices by state and type into sheets and accounting systems for revenue reporting and reconciliation - Sync the plan catalog so quoting and provisioning always reference current codes and pricing - Route every cancellation and pricing override through human approval

Without FlowRunner

Provisioning by relay race Sales closes, someone re-keys the order into billing, and the customer's first invoice reflects a typo

Billing questions interrupt finance "What did we invoice them in March" means someone logging into Recurly mid-close

Churn discovered in the revenue report Cancellations happen quietly, and retention learns about them at month end

With FlowRunner

Signup to subscription without re-keying Accounts and subscriptions are created from the CRM record, with overrides approved before they bill

Billing data flows to where questions are asked Invoices and account state sync to sheets and accounting on schedule, and lookups run inside support workflows

Cancellation is an event, not a surprise Every Cancel Subscription flows through a gate and fires the retention play the same day

Use Case Scenarios

Closed Won to first invoice without a keyboard

A deal closes in the CRM. The agent creates the Recurly account with the CRM's customer ID as the account code, validates the plan against List Plans, and, because this deal carries a negotiated discount, routes the unit amount override to finance in [Slack](/integrations/slack). On approval, Create Subscription provisions billing and the subscription ID lands back on the CRM record. The first invoice matches the order form because no one retyped it.

The revenue export that reconciles itself

Nightly, an agent pages List Invoices for new and updated invoices, pulls full line-item detail with Get Invoice for anything unusual, and appends the batch to [Google Sheets](/integrations/google-sheets) while mirroring customers and invoices into [QuickBooks Online](/integrations/quickbooks). At close, the accounting system and Recurly already agree, and the controller reviews exceptions instead of exporting CSVs.

The cancellation that triggered a save instead of a shrug

A churn request lands in the support queue. The agent pulls the account's history, subscription age, invoice record, and open balance, and posts the full picture to the retention channel with the requested cancellation mode. The retention lead makes one call: offer the downgrade path, or approve termination at renewal so the customer keeps what they paid for. Only after that decision does Cancel Subscription run. The churn still happens sometimes; it stops happening silently.

Human-in-Loop Highlight

Cancel Subscription ships with two modes, and the difference between them is money and goodwill. Terminate at Renewal lets the subscription run out its paid period; Terminate Now expires it immediately, cutting off a customer who may have eleven prepaid months remaining. An agent that picks the wrong mode, or cancels the wrong subscription on a fuzzy account match, has either refunded revenue prematurely or breached what the customer paid for, and neither un-happens cleanly. So no FlowRunner workflow cancels on its own judgment. The agent assembles the evidence, the exact subscription from Get Subscription, its billing period, the account's invoice history, and a person chooses the subscription, the mode, and the moment. The same gate covers Create Subscription when a unit amount override is in play, because a wrong price does not fail, it invoices. In billing, the expensive errors all look like successful API calls.

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

10 actions

Accounts

List Accounts Lists customer accounts, most recent first, filterable by email and subscription state, cursor-paginated. Each account carries its code, email, name, and billing state.
Get Account Retrieves one account by account code or internal ID; plain values are treated as codes automatically, so workflows can address customers by the ID they assigned. Returns contact details, billing state, and metadata.
Create Account Creates a customer account with a unique code you assign, typically the email or your own customer ID, which later anchors subscriptions and invoices. The provisioning step for every onboarding workflow.

Subscriptions

List Subscriptions Lists subscriptions site-wide, most recent first, filterable by state and cursor-paginated, with each subscription's plan, account, billing period, and status.
Get Subscription Retrieves one subscription by ID or UUID with plan, account, current billing period, pricing, add-ons, and lifecycle timestamps. The evidence pull that precedes any cancellation decision.
Create Subscription Attaches a plan to an existing account with plan code, account code, and currency, optionally with quantity, unit amount override, or a trial. Overrides pass through the approval gate.
Cancel Subscription Cancels an active subscription: Terminate at Renewal lets it expire at period end with no further charges, Terminate Now expires it immediately. The revenue-consequential operation this page's gate governs.

Invoices

List Invoices Lists invoices site-wide, most recent first, filterable by type and state, cursor-paginated, with number, totals, currency, state, and owning account. The export backbone for revenue reporting.
Get Invoice Retrieves one invoice by ID or number with full line items, subtotal, tax, discount, total, balance, and state. The detail pull for reconciliation exceptions and billing questions.

Catalog

List Plans Lists the configured subscription plans with code, name, interval, and pricing, filterable by state. The source of truth quoting and provisioning workflows validate against.

Frequently Asked Questions

What can FlowRunner do with Recurly?

FlowRunner agents can run List Accounts, Get Account, and Create Account in Recurly, plus 7 more actions.

Does connecting Recurly to FlowRunner require OAuth?

No. Recurly connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.

Can Recurly trigger a FlowRunner workflow automatically?

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

Start building with Recurly

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

Start Building Free Talk to us