# Zoho

![zoho-logo-512px.png](https://assets.relyanceuat.xyz/images/docs/6115524916493/6115359260813.png)
Zoho is a unique and powerful suite of online software. It contains word processing, spreadsheets, presentations, databases, note-taking, wikis, web conferencing, customer relationship management (CRM), project management, invoicing and other applications for collaboration and online productivity.

In order to integrate Zoho with Relyance AI you will need to authorize Relyance AI using an **OAuth2** flow.

#### In the Relyance AI application:

1. Login to your Relyance account.
2. Navigate to the **Settings** Menu in the bottom left-hand side.
3. Select **Integrations**.
4. Click on the **Vendor Integration** tab.
5. Find the **Zoho** integration card and click it to open its connections.
6. Under **Authentication Method**, choose **Oauth2 / API Token**.

![Zoho-1.png](https://assets.relyanceuat.xyz/images/docs/6115524916493/6115554570125.png)

8. Click **Authenticate**.
9. **This will bring up a login page on the Zoho site.**
10. **Login to Zoho.**
11. At this point, you should see the following result on the Vendor Integrations page:

![Zoho-2.png](https://assets.relyanceuat.xyz/images/docs/6115524916493/6115723850637.png)

12. Congratulations, you are now connected to **Zoho**.

<!-- failure-modes:begin (generated from the integration catalog; do not hand-edit) -->

## If the connection reports Connected but returns nothing

These are the ways this integration comes back empty without reporting an error. Generated from the integration catalog, so it tracks what the connection actually asks for.

1. **A feature you enabled returns nothing.** Some scopes belong to a feature rather than to the connection: **Data subject requests** needs `ZohoCRM.modules.contacts.DELETE`. Turning the feature on after the connection exists does not widen the grant it already holds, so re-authenticate the connection.
2. **Authorised, then empty.** The connection carries an authorisation, not a password: it stops returning data if the account that granted it loses access, its own permissions narrow, or the grant is revoked at the vendor. None of that reports an error here -- the connection keeps its last status until the next scan.

<!-- failure-modes:end -->

<!-- auth-methods:begin (generated from the integration catalog; do not hand-edit) -->

## Authentication methods and fields

Pick one of these under **Authentication Method** on the connection wizard's **Authentication** step. This table is generated from the integration catalog, so it always matches what the form actually asks for.

| Method | Required | Optional |
| --- | --- | --- |
| **Oauth2 / App Token** | — | — |

<!-- auth-methods:end -->

<!-- terraform-examples:begin (generated from the integration catalog; do not hand-edit) -->

## Manage this integration with Terraform

Connections for this integration can be managed as code with the [Relyance Terraform provider](https://registry.terraform.io/providers/Relyance/relyance/latest). Non-secret fields go in `auth.params`; secret fields go in `auth.secrets_wo`, which is write-only — never stored in Terraform state. Rotate secrets by bumping `auth.secrets_wo_version`.

The **OAuth (browser authorization)** method uses a browser authorization flow, so the connection is created in the Relyance app. Manage it in Terraform afterwards by importing it (`terraform import relyance_integration_connection.example zoho/<connection_id>`) or reading it with the `relyance_integration_connection` data source.

<!-- terraform-examples:end -->