> ## Documentation Index
> Fetch the complete documentation index at: https://conductorone-docs-mcp-bridge-private-server.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Set up a Zuora RevPro connector

> C1 provides identity governance for Zuora RevPro. Integrate your Zuora tenant with C1 for unified visibility and governance over user access.

C1 provides identity governance for Zuora RevPro (Zuora Revenue). Integrate
your Zuora tenant with C1 for unified visibility and governance over user
access.

## Capabilities

| Resource | Sync                                                          | Provision |
| -------- | ------------------------------------------------------------- | --------- |
| Users    | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |           |
| Roles    | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |           |

## Gather Zuora credentials

<Warning>
  The connector authenticates with an OAuth client (client ID and client secret)
  created for a Zuora platform user. It performs read-only API calls.
</Warning>

<Steps>
  <Step>
    Sign in to your Zuora tenant and open **Settings** > **Administration** >
    **Manage Users**.
  </Step>

  <Step>
    Select the API user to use for the integration, or create one with
    permission to read users and roles.
  </Step>

  <Step>
    Under that user's **OAuth Clients**, create a new client. Copy the
    generated **Client ID** and **Client Secret**.
  </Step>

  <Step>
    Note your tenant's REST base URL. It is data-center specific, for example
    `https://rest.zuora.com`, `https://rest.na.zuora.com`,
    `https://rest.eu.zuora.com`, or `https://rest.ap.zuora.com`.
  </Step>
</Steps>

## 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-After` header.

## Configure the Zuora RevPro connector

<Tabs>
  <Tab title="Cloud-hosted">
    Follow these instructions to use a built-in, no-code connector hosted by C1.

    <Steps>
      <Step>
        In C1, navigate to **Integrations** > **Connectors** and click **Add connector**.
      </Step>

      <Step>
        Search for **Zuora RevPro** and click **Add**.
      </Step>

      <Step>
        Choose how to set up the new connector and set the owner.
      </Step>

      <Step>
        Click **Next**.
      </Step>

      <Step>
        Find the **Settings** area of the page and click **Edit**.
      </Step>

      <Step>
        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.
      </Step>

      <Step>
        Click **Save**.
      </Step>

      <Step>
        The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing.
      </Step>
    </Steps>

    **Done.** Your Zuora RevPro connector is now pulling access data into C1.
  </Tab>

  <Tab title="Self-hosted">
    Follow these instructions to run the connector in your own environment.

    <Steps>
      <Step>
        Create secrets for the Zuora client ID and client secret.
      </Step>

      <Step>
        Configure the connector environment variables:

        * **BATON\_TENANT\_BASE\_URL**: your tenant's REST base URL.
        * **BATON\_OAUTH\_CLIENT\_ID**: the OAuth client ID.
        * **BATON\_OAUTH\_CLIENT\_SECRET**: the OAuth client secret.
      </Step>

      <Step>
        Deploy the connector using your standard self-hosted connector process.
      </Step>
    </Steps>

    **Done.** Your Zuora RevPro connector is now pulling access data into C1.
  </Tab>
</Tabs>