> For the complete documentation index, see [llms.txt](https://docs.dinmo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dinmo.io/integrations/destination-platforms/zuora.md).

# Zuora

Sync business data from your data warehouse to your Zuora: Step-by-step guide

## Supported Destinations Services

DinMo supports the following destination services:

* [Synchronize Accounts](/integrations/destination-platforms/zuora/synchronize-accounts.md)
* [Synchronize Subscriptions](/integrations/destination-platforms/zuora/synchronize-subscriptions.md)
* [Send Usage Data](/integrations/destination-platforms/zuora/send-usage-data.md)

Please refer to the dedicated documentation page for more information.

## Authentification to Zuora

Regardless of the selected destination service, DinMo will always connect to Zuora using an **OAuth Client.**

{% hint style="info" %}
You will first need to create the OAuth client for the user in Zuora, so that you can then enter it in DinMo.
{% endhint %}

### Steps in Zuora

To create an OAuth client for a user, follow these steps:

* Click your user name at the top right and navigate to **Administration > Manage Users**.

<figure><img src="https://3204318043-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxzBTp1t4OfqV67nXkVse%2Fuploads%2Fgit-blob-f7ada51f8fe54b9dcc3588d867b4e618698b7128%2FCleanShot%202025-07-02%20at%2010.31.35%402x.png?alt=media" alt=""><figcaption></figcaption></figure>

* Locate the user in the table and click on it.

{% hint style="warning" %}
The user must be Active and have a Platform role that includes the “API Write Access” permission.
{% endhint %}

* In the **New** **OAuth Clients** section, enter a name for the OAuth client.\
  If you have the Multi-entity feature enabled, select which entities the OAuth client will be permitted to access.
* Click **create**.

Zuora displays the Client ID and Client Secret for the OAuth client.

{% hint style="warning" %}
This is the only time you can see the Client Secret.\
**You will need the Client ID and Client Secret to connect to DinMo, make sure to save it carefully.**
{% endhint %}

### Steps in DinMo

Once the OAuth client has been created, you can return to DinMo, directly in the destinations tab.

Select Zuora as the new platform and enter the **Client ID** and **Client Secret** you retrieved in the previous step.

<figure><img src="https://3204318043-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxzBTp1t4OfqV67nXkVse%2Fuploads%2Fgit-blob-a07df26406aa8778d0d5d9112b8504996fd3a8e9%2Fimage.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

And it's done! Now you can configure [each service destination](#supported-destinations-services).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dinmo.io/integrations/destination-platforms/zuora.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.