Commerce & Payments · Integration
Zuora
Add Zuora to your product for your customers, and give your AI agents governed access to it.
Zuora is the subscription billing platform itself, reached through its own REST API with the customer's own OAuth client, rather than through the managed package some businesses additionally run inside Salesforce. Three things shape the build. The endpoint is per tenant: production, the sandbox and the European and Asia Pacific tenants each answer on a different host, so the base URL is something a customer supplies instead of a constant you compile in, and a token issued against one of them is worthless against another. Subscription change is modelled as an order in the current API, which lets several changes to the same subscription be submitted as one action that either lands whole or not at all, where the older amendment model dealt with them one at a time. And Data Query, the asynchronous way to run ZOQL over large volumes, reads an offloaded copy rather than live records, so it is the right tool for a report and the wrong one for confirming a write you made a second ago. Writes are idempotent, which means a timeout followed by a retry cannot bill anybody twice.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Zuora tenant and supply the host it answers on, since production, sandbox and the regional tenants all differ.
Submit a subscription change as an order, so several amendments to one subscription are applied together or not at all.
Read accounts, rate plans, invoices and payments so a billing question is answered inside your product rather than inside theirs.
Use Data Query for reporting volumes and the ordinary endpoints for anything you need to read back immediately.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent explains what a subscription bills next by reading its rate plan charges rather than guessing from the plan name.
An agent drafts an order for a plan change and routes it for approval before anything is submitted.
An agent reports which invoices are unpaid past terms and how much each account owes.
Example prompt
What will this account be invoiced at the next bill run, and which rate plan charges make up the total?
Set up Zuora in 4 steps
- 01Enable the Zuora connector in your fastn dashboard.
- 02Have each customer create an OAuth client inside their own tenant and tell you which environment and region it answers on.
- 03Map the account, subscription, rate plan and invoice fields you read and write, then enable the order actions and callouts you need.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Zuora integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Zuora integration without building it. Your customers connect their own Zuora account inside your product and work their orders, payments and customers there, with no per-customer code on your side.
- Handle the part that actually costs time: money and order state must never be double-applied, and reconciliation has to be possible. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Zuora update is not your on-call problem.
- One integration serves your product and your agents. The same governed Zuora connection powers in-product features and gives AI agents scoped, audited access, so you keep commerce and payment records in step with your product without wiring it twice.
Used by these teams
Compare with
Zuora for Salesforce
ChargebeeWorks well with
NetSuiteOften used alongside
Tools the same teams tend to run next to Zuora, across other categories.
Notion
Box
Docusign
QuickBooksZuora integration FAQ
How do I add a Zuora integration to my product?
Enable the Zuora connector in your fastn dashboard, then let each customer authenticate their own Zuora account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Zuora client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Zuora account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Zuora account and only ever sees their own orders, payments and customers. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Zuora integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent explains what a subscription bills next by reading its rate plan charges rather than guessing from the plan name.
Who maintains the Zuora integration?
fastn does. When Zuora changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Is the Zuora integration safe for payment and order writes?
Writes are idempotent, so a retry cannot double-charge or duplicate an order, and every call is logged per tenant so a transaction can be reconciled against the event that triggered it.
Can my product react to a new order, payment or refund immediately?
Yes, through event triggers, so fulfilment, entitlement or accounting steps run as soon as the event lands rather than on a nightly sync.
What can I build with the Zuora integration?
A common starting point: let each customer connect their own Zuora tenant and supply the host it answers on, since production, sandbox and the regional tenants all differ. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Zuora integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Zuora does not change your per-connector cost. You can start free with 3 connected accounts.
Add Zuora to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.