Zuora

Connect to Zuora to manage billing, subscriptions, and revenue data.

Overview

Zuora is a subscription management and recurring billing platform that helps businesses automate the entire quote-to-revenue lifecycle. It provides comprehensive solutions for subscription billing, revenue recognition, and customer lifecycle management.

Connecting Suger to your Zuora tenant lets the Suger AI agent read your billing data — accounts, subscriptions, invoices, and payments — from a Suger workflow or chat.

Org-Level vs User-Level

Org-Level: Supported, using Zuora’s OAuth 2.0 client-credentials grant.

User-Level: Not applicable. Zuora’s REST API offers client credentials and nothing else — there is no three-legged flow an individual Suger user could consent to — so a per-user connection is impossible rather than merely absent. Every Suger user in your organization shares the org connection.

How the connection works

The OAuth client is created in your Zuora tenant. Suger exchanges its client ID and secret for a bearer token and refreshes it for you — nothing in Suger mints or caches Zuora tokens itself. The subdomain you supply builds the host used for both the token exchange and every API call, which is why it must be the subdomain alone.

Create Integration (Org-Level)

Prerequisites

• A Zuora account.
• Permission to create an OAuth client in your Zuora tenant.
• The Suger Admin role — connecting, disconnecting, and running an integration’s actions are all admin-only in Suger.

Authenticate by client credentials

1. Create an OAuth client in your Zuora tenant, under a user with the permissions you want Suger to operate with. Zuora scopes the client to that user’s role. Capture the Client ID and Client Secret — see the Zuora OAuth documentation.
2. In the Suger console, open Settings → Integrations and click Connect on Zuora.
3. Enter:

   • Subdomain — the label between https:// and .zuora.com, for example rest. Common values:

     Environment	Subdomain
     US Production	rest
     US Cloud 1 Production (NA)	rest.na
     US API Sandbox	rest.apisandbox
     US Performance Test (PT1)	rest.pt1
     EU Production	rest.eu
     EU API Sandbox	rest.sandbox.eu

   • Client ID and Client Secret — from step 1.

4. Save.

Check the connection

Suger re-checks the stored credential against Zuora rather than trusting a cached token, so a client secret revoked in Zuora is noticed even while the token it issued has not yet expired.

You see the result on the Zuora card in the Integrations list. When the stored credential stops working the card says so directly:

Connected, but this integration’s stored credential can no longer be used — agents and workflows cannot reach it. Disconnect and connect it again to restore access.

This is the same check every org integration gets — see Connection health for what it does and how to read a card that does not show it.

Suger AI Tools

When Zuora is connected, the Suger AI agent can read your billing data through Suger’s built-in tools (6 actions).

Org-level: All tools run under the org OAuth client, so its Zuora role sets the ceiling on what the agent can read.

Edit Integration

Editing is not supported. For security, if you need to rotate credentials or switch tenants, delete the integration and recreate it.

Delete Integration

To delete an integration, click the 🗑️ button next to its entry in the Integrations list. Suger discards the stored credentials with the integration record, and any workflow or agent depending on Zuora tools stops working immediately. Revoke the OAuth client in Zuora too if you want to cut access from that side.