Capabilities
| Resource | Sync | Provision |
|---|---|---|
| Users | ||
| Roles |
Gather Zuora credentials
Select the API user to use for the integration, or create one with
permission to read users and roles.
Under that user’s OAuth Clients, create a new client. Copy the
generated Client ID and Client Secret.
Configuration fields
| Field | Required | Description |
|---|---|---|
tenant-base-url | Yes | Your tenant’s Zuora platform REST base URL, e.g. https://rest.zuora.com. |
oauth-client-id | Yes | OAuth client ID for the Zuora platform API user. |
oauth-client-secret | Yes | OAuth client secret paired with the client ID. |
Synced resource types
- Users: Zuora platform users from the SCIM 2.0 user directory.
- Roles: Zuora platform roles, with one assignment entitlement per role.
- Role assignments: user-to-role memberships, emitted as grants on each role.
Special notes
- The connector reads users and roles from the Zuora platform identity layer (SCIM 2.0), not the Zuora Revenue data-integration API. The Revenue API does not expose users or roles.
- Each Zuora tenant is pinned to a data center, so the tenant base URL is required and there is no single shared base URL.
- The OAuth token endpoint is derived from the tenant base URL. Access tokens are short-lived and refreshed automatically.
- On rate limit responses, the connector follows the
Retry-Afterheader.
Configure the Zuora RevPro connector
- Cloud-hosted
- Self-hosted
Follow these instructions to use a built-in, no-code connector hosted by C1.Done. Your Zuora RevPro connector is now pulling access data into C1.
Enter the Zuora credentials:
- Tenant Base URL: your tenant’s REST base URL.
- Client ID: the OAuth client ID.
- Client Secret: the OAuth client secret.