> 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.appstrategy.com/apprules-r-documentation/platform/platform-features/system-settings/data-sources/connection-settings/crm/zohocrm.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.