--- title: "Zuora Integration" description: "Automate subscription billing in Zuora from AI agents. Agents create customer accounts, pull consolidated account summaries with recent invoices and payments, manage subscriptions against the product catalog, browse products, and run ad-hoc ZOQL queries when no dedicated action exists." url: https://flowrunner.ai/integrations/zuora date_modified: 2026-08-01T02:40:32-07:00 --- # Zuora [Finance](https://flowrunner.ai/integrations/category/finance-accounting) Automate subscription billing in Zuora from AI agents. Agents create customer accounts, pull consolidated account summaries with recent invoices and payments, manage subscriptions against the product catalog, browse products, and run ad-hoc ZOQL queries when no dedicated action exists. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 8 actions · OAuth · available [Zuora website](https://zuora.com/) · [Platform Documentation](https://www.zuora.com/) · Capability data verified 2026-08-12 1. A deal closes won in the CRM with plan, term, and billing contact attached 2. List Catalog Products resolves the productRatePlanId for the plan the customer bought 3. Get Account confirms whether this customer already has a billing account, so no duplicate is created 4. Create Account stands up the billing account with currency, bill-to contact, and bill cycle day 5. The agent posts the provisioning summary: account, plan, term, effective date, and what will be invoiced 6. The billing owner verifies the terms match the signed contract before any charge exists 7. Create Subscription provisions the plan, runs billing, and the first invoice goes out correct ## What This Integration Enables Zuora runs subscription billing for businesses where the invoice is the product's paper trail: rate plans, charges, terms, amendments, balances. The expensive gap is between the systems where deals happen and the tenant where billing lives, because that gap is bridged by hand. This connector closes it. FlowRunner agents create customer accounts with billing settings and bill-to contacts, provision subscriptions from the product catalog, pull consolidated account summaries with recent invoices and payments in one call, and fall back to ZOQL queries when no dedicated action covers the read. The stance built into these workflows: reads flow freely, and the calls that create financial obligations pass a human checkpoint. A subscription is a contract rendered in billing software; someone should confirm the rendering matches the contract. - Onboard customers end to end: account, subscription, invoice, optionally payment collection - Answer "what does this customer owe and hold" in one Get Account Summary call - Reconcile subscriptions against CRM records and surface mismatches before customers do - Report on any queryable object with Run Query when the dedicated actions do not cover it Note: this is a gated integration requiring a provisioned Zuora tenant and an OAuth client. ### Without FlowRunner **Closed-won to first invoice takes days**: Billing setup waits in a queue while someone retypes contract terms into Zuora **Contract and invoice quietly disagree**: The plan sold and the plan billed drift apart, and the customer finds the difference first **Billing questions require a Zuora expert**: Balance, MRR, and invoice history live behind screens only the billing team navigates ### With FlowRunner **Provisioning starts at signature**: The closed deal carries its terms into account and subscription creation the same day **A person confirms terms before money moves**: The contract-to-catalog match is reviewed once, at the moment it matters **Billing data answers questions anywhere**: Account summaries and ZOQL queries feed CRMs, sheets, and support tools on demand ## Use Case Scenarios ### Closed-won becomes billed without the retyping step A deal closes in [HubSpot](https://flowrunner.ai/integrations/hubspot). The agent maps the sold plan to the catalog with List Catalog Products, creates the billing account with Create Account, and stages the subscription: rate plans, Termed with a 12-month initial term, contract effective date from the signature date. The billing owner reviews the staged terms against the order form and approves. Create Subscription provisions the plan with billing run enabled, and the subscription number writes back to the deal record. The first invoice matches the contract because a person checked exactly once, at the only moment checking matters. ### The account summary that answers support tickets A customer emails asking why they were charged. The support agent's workflow calls Get Account Summary and gets the whole picture in one response: recent invoices, payments, active subscriptions, and usage. The context posts into the support thread within seconds, so the human answering the ticket starts from the facts instead of from a login screen. For odd cases, Run Query pulls the specific invoice or payment records with a ZOQL statement, no billing specialist required. ### The weekly reconciliation that catches drift On a schedule, the agent runs Get Subscriptions By Account across active customers and compares each subscription's rate plans and term dates against what the CRM says was sold. Matches log silently to [Google Sheets](https://flowrunner.ai/integrations/google-sheets); mismatches post to the finance channel in [Slack](https://flowrunner.ai/integrations/slack) with both versions side by side. Contract-billing drift, the thing that otherwise surfaces as a churned customer or a revenue recognition problem, becomes a Tuesday list that a person clears in twenty minutes. ## Human-in-Loop Highlight Create Subscription can do three things in one call: bind a customer to rate plans and a term, generate the invoice, and, with Collect Payment enabled, charge the account's default payment method on the spot. That last step is money leaving a customer's card on an agent's initiative, and a wrong rate plan ID or a misread term does not get quietly fixed; it gets refunded, apologized for, and remembered at renewal. So FlowRunner workflows treat subscription creation as a staged act: the agent assembles the account key, the productRatePlanId set, the term type, and the effective date, then presents the whole package next to the source contract. The billing owner approves, and only then does the call execute. Everything before that line, catalog lookups, account matching, summary pulls, runs at machine speed with no gate at all. The obligation is the part that waits. 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 8 actions ### Accounts 3 - **Get Account** Retrieves full account details by account number or ID: billing and payment settings, default bill-to and sold-to contacts, balance, credit, MRR, and tax information. The lookup that precedes any write. - **Get Account Summary** Retrieves a consolidated summary in a single call: basic info, contacts, recent subscriptions, invoices, payments, and usage. The most efficient way to answer a billing question about one customer. - **Create Account** Creates a customer account with its bill-to contact and billing settings. Requires name, currency, and contact details; supports bill cycle day, auto pay, and an optional subscription at creation. Returns the generated account number and ID. ### Subscriptions 3 - **Get Subscriptions By Account** Retrieves all subscriptions on an account, with rate plans, charges, term dates, and status. Paginated. The read behind reconciliation sweeps. - **Get Subscription** Retrieves a single subscription by subscription number, returning status, term details, rate plans, and charge-level pricing for the latest version. Used to inspect exactly what a customer holds. - **Create Subscription** Creates a subscription for an existing account from the catalog: account key, contract effective date, rate plans by productRatePlanId, Termed or Evergreen term, and optional immediate invoicing and payment collection. The action this page's human gate governs. ### Catalog 1 - **List Catalog Products** Lists the product catalog with each product's rate plans and charges, including the productRatePlanId values Create Subscription needs. Paginated. ### Query 1 - **Run Query** Runs a ZOQL statement against the tenant and returns matching records. The escape hatch for reading any queryable object, Account, Subscription, Invoice, Payment, RatePlanCharge, with SQL-like syntax. Large result sets paginate via a queryLocator. ## Frequently Asked Questions ### What can FlowRunner do with Zuora? FlowRunner agents can run Get Account, Get Account Summary, and Create Account in Zuora, plus 5 more actions. ### Does connecting Zuora to FlowRunner require OAuth? Yes. Zuora connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials. ### Can Zuora trigger a FlowRunner workflow automatically? Zuora doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Zuora?** This integration exposes Zuora to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/zuora. Site index: https://flowrunner.ai/llms.txt