This connector is in beta. This means it’s undergoing ongoing testing and development while we gather feedback, validate functionality, and improve stability. Beta connectors are generally stable, but they may have limited feature support, incomplete error handling, or occasional issues. We recommend closely monitoring workflows that use this connector and contacting our Support team with any issues or feedback.
Capabilities Resource Sync Provision Users Groups
The Zuora connector syncs users and security groups via the SCIM 2.0 API.
This connector supports the following provisioning operations:
User account provisioning : Create new SSO users (federated identity) via SCIM POSTEnable/Disable user lifecycle : Enable or disable user accounts via SCIM PATCHGroup membership : Add and remove users from security groups via SCIM PATCH (grant/revoke)
Requirements
An OAuth 2.0 Client (client_id + client_secret) with admin scope
Gather Zuora credentials Create an OAuth 2.0 Client
Log in to Zuora as an administrator.
Navigate to Platform → API → OAuth Clients .
Click Create OAuth Client .
Select Client Credentials as the grant type.
Grant the client admin scope.
Copy the Client ID and Client Secret immediately.
That’s it! Next, move on to the connector configuration instructions.To complete this task, you’ll need:
The Connector Administrator or Super Administrator role in ConductorOne
Your Zuora domain and the OAuth 2.0 client credentials generated above
Follow these instructions to use a built-in, no-code connector hosted by ConductorOne.
In ConductorOne, navigate to Integrations > Connectors and click Add connector .
Search for Zuora and click Add .
Choose how to set up the new Zuora connector:
Add the connector to a currently unmanaged app
Add the connector to a managed app
Create a new managed app
Set the owner for this connector and click Next .
Find the Settings area of the page and click Edit .
Enter your Zuora domain in the Zuora Domain field (for example, https://one.zuora.com).
Paste the OAuth 2.0 Client ID and Client Secret .
The connector’s label changes to Syncing , followed by Connected . You can view the logs to ensure that information is syncing.
That’s it! Your Zuora connector is now pulling access data into ConductorOne.Follow these instructions to use the Zuora connector, hosted and run in your own environment. Resources
GitHub repository : Access the source code, report issues, or contribute to the project. Step 1: Set up a new Zuora connector
In ConductorOne, navigate to Integrations > Connectors > Add connector .
Search for Baton and click Add .
Choose how to set up the new Zuora connector.
Set the owner for this connector and click Next .
In the Settings area, click Edit then Rotate to generate a new Client ID and Secret.
Step 2: Create Kubernetes configuration files Secrets configuration # baton-zuora-secrets.yaml apiVersion : v1 kind : Secret metadata : name : baton-zuora-secrets type : Opaque stringData : BATON_CLIENT_ID : <ConductorOne client ID> BATON_CLIENT_SECRET : <ConductorOne client secret> BATON_ZUORA_DOMAIN : <Zuora domain, e.g. https://one.zuora.com> BATON_ZUORA_CLIENT_ID : <Zuora OAuth Client ID> BATON_ZUORA_CLIENT_SECRET : <Zuora OAuth Client Secret> BATON_PROVISIONING : "true"
Deployment configuration # baton-zuora.yaml apiVersion : apps/v1 kind : Deployment metadata : name : baton-zuora labels : app : baton-zuora spec : selector : matchLabels : app : baton-zuora template : metadata : labels : app : baton-zuora baton : "true" baton-app : zuora spec : containers : - name : baton-zuora image : public.ecr.aws/conductorone/baton-zuora:latest imagePullPolicy : IfNotPresent env : - name : BATON_HOST_ID value : baton-zuora envFrom : - secretRef : name : baton-zuora-secrets
Step 3: Deploy the connector
Create a namespace in which to run ConductorOne connectors (if desired),
then apply the secret config and deployment config files.
Check that the connector data uploaded correctly. In ConductorOne, click
Applications . On the Managed apps tab, locate and click the name of
the application you added the Zuora connector to. Zuora data should be found
on the Entitlements and Accounts tabs.
That’s it! Your Zuora connector is now pulling access data into ConductorOne.
