> For the complete documentation index, see [llms.txt](https://docs.appstrategy.com/apprules-r-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appstrategy.com/apprules-r-documentation/platform/platform-features/system-settings/data-sources/connection-settings/crm/zohocrm.md).

# Zoho CRM

Connects to Zoho CRM via the configurable v2–v8 REST API (default v6) across 8 regional data centers.

### Connection Properties

#### Server

| Property    | Default | Notes                                                                                         |
| ----------- | ------- | --------------------------------------------------------------------------------------------- |
| Data Center | `US`    | Region: `US`, `EU`, `IN`, `AU`, `JP`, `CN`, `SA`, `CA`. Determines the API and accounts URLs. |
| API Version | `v6`    | Zoho CRM REST API version; `v8` for the latest features                                       |
| Timeout     | `60`    | Connection timeout, seconds                                                                   |

#### Authentication

**Auth Scheme** selects the mechanism: `OAuthRefreshToken` (default), `OAuthGrantToken`, or `AccessToken`.

| Property            | Used by           | Notes                                                                                |
| ------------------- | ----------------- | ------------------------------------------------------------------------------------ |
| OAuth Client Id     | all OAuth schemes | From your Zoho OAuth app in the Developer Console                                    |
| OAuth Client Secret | all OAuth schemes | From the same app                                                                    |
| OAuth Refresh Token | OAuthRefreshToken | Obtained once via the Zoho self-client or OAuth flow                                 |
| OAuth Grant Token   | OAuthGrantToken   | One-time token; exchanged on first connection for access and refresh tokens          |
| OAuth Access Token  | AccessToken       | Pre-obtained, valid roughly an hour — use a refresh token for long-lived connections |

#### Network

Proxy: **Proxy Auto Detect** (default `true`), **Proxy Server**, **Proxy Port**, **Proxy User**, **Proxy Password**, **Proxy Exceptions** (semicolon-separated bypass list), **Proxy Auth Scheme** (`BASIC` default, `DIGEST`, `NEGOTIATE`, `NTLM`).

Firewall: **Firewall Type** (`NONE` default, `TUNNEL`, `SOCKS4`, `SOCKS5`, `HTTP`), **Firewall Server**, **Firewall Port**, **Firewall User**, **Firewall Password**.

**SSL Server Cert** — `*` to accept any certificate, or a specific thumbprint.

#### Logging

| Property  | Default | Notes                            |
| --------- | ------- | -------------------------------- |
| Log Level | `0`     | `0` disabled, `1` log to file    |
| Log File  | —       | Leave empty for the default path |


---

# 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.appstrategy.com/apprules-r-documentation/platform/platform-features/system-settings/data-sources/connection-settings/crm/zohocrm.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.