> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/crm/zoho-crm.md).

# Zoho CRM

Sync Zoho CRM leads, contacts, deals, and accounts to Google Sheets, BigQuery, and AI tools via Coupler.io for centralized sales reporting.

Zoho CRM is a cloud-based customer relationship management platform that helps you manage sales pipelines, customer interactions, and business relationships. By connecting Zoho CRM to Coupler.io, you can automatically sync your contacts, leads, deals, accounts, and custom modules to Google Sheets, Excel, BigQuery, Looker Studio, or AI destinations like Claude and ChatGPT for deeper analysis and reporting.

## Why connect Zoho CRM to Coupler.io?

* **Centralized reporting** — Pull all your CRM data into a single spreadsheet or data warehouse for unified dashboards and reports
* **Automated workflows** — Sync lead, deal, and contact data on a schedule without manual exports
* **AI-powered insights** — Send your sales pipeline, customer data, or forecasts to Claude or ChatGPT for predictive analysis and recommendations
* **Multi-environment support** — Connect to Production, Sandbox, or Developer environments depending on your testing needs

## Prerequisites

* A Zoho CRM account (Free, Standard, Professional, Enterprise, or Ultimate edition)
* Admin access or permission to generate API tokens in Zoho CRM
* Your Zoho CRM organization's base URL (e.g., `https://www.zohoapis.com` for US, `https://www.zohoapis.eu` for EU)

## Quick start

{% hint style="success" %}
Before you begin, decide which modules you want to sync (Leads, Contacts, Accounts, Deals, etc.) and whether you're connecting to Production or a test environment. This will help you choose the right configuration when you set up your data flow.
{% endhint %}

## How to connect

{% stepper %}
{% step %}
**Log in to Coupler.io** and create a new data flow. Select **Zoho CRM** as your source.
{% endstep %}

{% step %}
**Generate a Zoho CRM API token.** In your Zoho CRM account, go to **Settings** → **APIs** → **API Tokens** (or **OAuth Tokens**). Click **Create Token** and select your preferred scope (e.g., ZohoCRM.modules.READ for read-only access to modules). Copy the generated token — you'll need it in the next step.
{% endstep %}

{% step %}
**Paste your API token** into Coupler.io and select your **Environment** (Production, Developer, or Sandbox) and **Zoho CRM edition** (Free, Standard, Professional, Enterprise, or Ultimate). Your edition affects API rate limits, so choose the one matching your account.
{% endstep %}

{% step %}
**Set a start date** using the date picker if you want to limit data exports to a specific time period. If left blank, Coupler.io will sync all available data from your Zoho CRM modules.
{% endstep %}

{% step %}
**Select the modules and fields** you want to export (e.g., Leads, Contacts, Accounts, Deals). You can choose specific fields or include all available columns.
{% endstep %}

{% step %}
**Choose your destination** — Google Sheets, Excel, BigQuery, Looker Studio, or an AI destination like Claude or ChatGPT. If you're sending data to ChatGPT or Claude, you can ask them to analyze your sales pipeline or forecast revenue based on your deal data.
{% endstep %}

{% step %}
**Run the data flow** to test the connection. Once the manual run completes successfully, your Zoho CRM data will appear in your destination.
{% endstep %}
{% endstepper %}

## Supported modules and entities

Zoho CRM allows you to sync data from any standard or custom module. Common modules include:

| Module         | Description                                 | Use case                                       |
| -------------- | ------------------------------------------- | ---------------------------------------------- |
| Leads          | Potential customers who have shown interest | Track new prospects and lead scoring           |
| Contacts       | Individual people in your CRM               | Build customer communication lists             |
| Accounts       | Companies or organizations                  | Analyze account growth and customer health     |
| Deals          | Sales opportunities with pipeline stage     | Monitor sales forecasts and close rates        |
| Tasks          | Action items assigned to team members       | Track team productivity and task completion    |
| Events         | Meetings, calls, and other interactions     | Measure customer engagement frequency          |
| Products       | Items your company sells                    | Analyze revenue by product or bundle offerings |
| Custom Modules | Any modules specific to your organization   | Sync industry-specific or proprietary data     |

You can also combine data from multiple modules using **Join** (e.g., linking Deals to Accounts) or **Append** (e.g., combining Leads and Contacts into a single prospect list) transformations.

## Zoho CRM data overview

Zoho CRM provides access to a wide range of sales, customer, and interaction data. The modules you can sync depend on your Zoho CRM edition and custom configurations.

## Available modules

| Module             | Data type              | Typical fields                                                                   |
| ------------------ | ---------------------- | -------------------------------------------------------------------------------- |
| **Leads**          | Prospecting data       | Lead name, email, company, phone, source, lead score, industry, rating           |
| **Contacts**       | Customer people data   | Contact name, email, phone, mailing address, account link, related deals         |
| **Accounts**       | Organization data      | Account name, industry, website, annual revenue, employee count, billing address |
| **Deals**          | Sales opportunity data | Deal name, amount, stage, close date, owner, account link, probability           |
| **Tasks**          | Activity tracking      | Task subject, due date, owner, status, priority, related to (record link)        |
| **Events**         | Interaction log        | Event type, start time, end time, attendees, location, related record            |
| **Products**       | Inventory data         | Product name, unit price, quantity in stock, SKU, category                       |
| **Custom Modules** | Organization-specific  | Any field your admin has configured                                              |

## Common metrics and dimensions

### Sales pipeline metrics

#### Deal metrics

| Metric                 | Definition                            | Insight                                    |
| ---------------------- | ------------------------------------- | ------------------------------------------ |
| **Total deal value**   | Sum of all deal amounts in a period   | Revenue opportunity size                   |
| **Average deal size**  | Mean deal amount                      | Deal quality and average transaction value |
| **Win rate (%)**       | Deals closed won ÷ total deals ×100   | Sales effectiveness                        |
| **Pipeline value**     | Sum of open deals ÷ their probability | Expected revenue forecast                  |
| **Sales cycle length** | Days from Lead to Deal Close          | Speed of sales process                     |

#### Lead metrics

| Metric                        | Definition                                | Insight                                  |
| ----------------------------- | ----------------------------------------- | ---------------------------------------- |
| **Lead conversion rate (%)**  | Leads converted to Contacts ÷ total leads | Lead quality and nurturing effectiveness |
| **Cost per lead**             | Marketing spend ÷ new leads               | Lead acquisition efficiency              |
| **Lead source effectiveness** | Conversions by source                     | Best-performing marketing channels       |

### Customer metrics

#### Account metrics

| Metric                            | Definition                                   | Insight                              |
| --------------------------------- | -------------------------------------------- | ------------------------------------ |
| **Customer lifetime value (CLV)** | Total revenue from customer lifetime         | Strategic account importance         |
| **Account health score**          | Engagement + product usage + support tickets | Churn risk and expansion opportunity |

#### Contact metrics

| Metric                   | Definition                                        | Insight               |
| ------------------------ | ------------------------------------------------- | --------------------- |
| **Contacts per account** | Average number of contacts linked to each account | Relationship depth    |
| **Contact engagement**   | Event count, task activity per contact            | Relationship strength |

### Activity metrics

#### Task and event metrics

| Metric                      | Definition                                  | Insight              |
| --------------------------- | ------------------------------------------- | -------------------- |
| **Tasks completed (%)**     | Completed tasks ÷ total tasks               | Team execution       |
| **Activities per customer** | Total events + tasks per contact or account | Engagement intensity |
| **Response time**           | Days from task creation to completion       | Team responsiveness  |

## Common metric combinations

**Sales team dashboard:**

* Deal pipeline by stage + average deal size by owner + win rate by month
* Use **Join** to link Deals to Accounts and Owners for segmented analysis

**Lead quality report:**

* Lead count by source + conversion rate by source + average lead score
* Use **Group/Aggregate** to roll up by lead source and stage

**Account health scorecard:**

* Revenue by account + contact count per account + recent activity count
* Use **Join** to combine Account data, Contact count, and recent Event/Task records

**Forecast accuracy:**

* Expected revenue (sum of pipeline value × probability) vs. actual closed deals
* Use **Append** to combine closed and open deals, then segment by close date vs. actual date

## Use cases by role

{% tabs %}
{% tab title="Sales leaders" %}
Track pipeline health, forecast accuracy, and deal velocity by rep. Pull Deals joined with Accounts and Owners into a dashboard to monitor stage progression and identify bottlenecks. Use Claude or ChatGPT to analyze which account industries or deal sizes close fastest and recommend focus areas for the team.
{% endtab %}

{% tab title="Marketers" %}
Measure lead generation volume and quality by source, channel, and campaign. Sync Leads data with lead scores and source attribution to identify highest-converting channels. Export to spreadsheets or BI tools for attribution modeling, then use AI to recommend budget allocation across channels.
{% endtab %}

{% tab title="Finance teams" %}
Sync Deals and Accounts to forecast revenue and track contract value. Join Deals with Account revenue data to monitor customer concentration and churn risk. Use AI to model revenue scenarios based on pipeline probability and close date trends.
{% endtab %}

{% tab title="Operations" %}
Monitor task completion rates, team activity levels, and customer engagement frequency. Export Tasks and Events to track SLA adherence and team workload. Use aggregate reports to identify over/under-resourced areas.
{% endtab %}
{% endtabs %}

## Platform-specific notes

* **Rate limits vary by edition**: Free and Standard editions have lower API quotas; Professional and Enterprise support higher throughput. Coupler.io respects your edition's limits and queues requests accordingly.
* **Custom fields and modules**: Any custom fields or modules you've added in Zoho CRM will appear in Coupler.io. Custom field names follow Zoho's API naming convention.
* **Related records**: When you sync a module with lookup fields (e.g., Deals linked to Accounts), you'll see the linked record ID; to get the full related record details, use a **Join** transformation in Coupler.io.
* **Sandbox and Developer environments**: Useful for testing data flows before rolling out to Production. Use the **Environment** selector during setup to switch between them.
* **Date and time fields**: Zoho CRM stores dates in UTC. Coupler.io preserves this; convert to your local timezone in your destination if needed.
* **Large data exports**: If syncing millions of records, start with a specific date range and gradually expand to avoid timeouts.

## Zoho CRM common issues

### Connection issues

<details>

<summary>"Invalid API token" or "Unauthorized" error</summary>

Your API token has expired or doesn't have the right permissions. Regenerate it in Zoho CRM:

1. Go to **Settings** → **APIs** → **API Tokens** (or **OAuth Tokens** depending on your Zoho CRM version)
2. Delete the old token and click **Create Token**
3. Select the scope **ZohoCRM.modules.READ** for read-only access to all modules
4. Copy the new token and paste it into Coupler.io
5. Test the connection with a manual run

If you're using OAuth instead of API tokens, make sure your Coupler.io integration is authorized and your Zoho account hasn't revoked access.

</details>

<details>

<summary>"Invalid environment or base URL" error</summary>

You've selected an environment (Production, Developer, or Sandbox) that doesn't match your Zoho CRM setup. Check which environment your account uses:

* **Production**: The main Zoho CRM account you use daily
* **Developer**: Your free Zoho developer sandbox (only available if you signed up for a developer account)
* **Sandbox**: A test environment (available on Enterprise and Ultimate plans)

Select the correct environment in Coupler.io and retry.

</details>

<details>

<summary>Connection times out or hangs</summary>

This can happen if your Zoho CRM account has millions of records or your network is slow. Try:

1. Set a **Start date** to limit data export to the last 30–90 days instead of syncing all historical data
2. Reduce the number of modules or fields you're syncing in the first run
3. Test with a single module (e.g., Leads) before adding multiple modules
4. Wait 5–10 minutes and retry; Zoho's API may be temporarily throttled

</details>

### Missing data

<details>

<summary>Some records or modules don't appear in the destination</summary>

Check if:

1. **Your API token scope is correct**: The token must have **ZohoCRM.modules.READ** permission. Tokens with limited scopes (e.g., only Leads access) won't fetch all modules.
2. **The module is visible in your Zoho CRM**: Some custom modules may be hidden or restricted by admin settings. Verify the module appears when you log into Zoho CRM.
3. **Your start date is too recent**: If you set a start date after the records were created, they won't sync. Clear the start date or set it earlier.
4. **Field-level permissions**: If your Zoho CRM admin restricted certain fields, they may not appear in the export. Contact your admin to grant field-level read access.

</details>

<details>

<summary>Deal or Contact records are missing related Account data</summary>

Zoho CRM stores related records as lookup field IDs, not full nested data. To get Account details alongside Deals or Contacts:

1. Create a **Join** transformation in Coupler.io
2. Join the Deals table to the Accounts table on the Account ID field
3. Select which Account fields (name, industry, revenue) you want to include

This merges both datasets so you see Account information for every Deal.

</details>

<details>

<summary>Custom field data is empty or shows as "null"</summary>

Custom fields may not sync if:

1. **The field is restricted by admin permissions**: Your Zoho admin may have hidden the field from API access. Ask your admin to enable API access for that field.
2. **The field isn't populated for all records**: If only some records have values in that custom field, others will appear blank — this is expected.
3. **The field type isn't supported**: Zoho CRM supports most field types in API exports; if it's a very new or proprietary field type, contact Coupler.io support.

</details>

### Permission errors

<details>

<summary>"You don't have permission to access this module" error</summary>

Your Zoho CRM user role doesn't have read access to that module. Ask your Zoho CRM admin to:

1. Go to **Setup** → **Users & Roles** → **Roles**
2. Select your role and check the **Module Permissions** section
3. Enable **Read** access for the modules you need to sync
4. Re-test the connection in Coupler.io

</details>

<details>

<summary>API token was revoked by admin</summary>

If your Zoho CRM admin revoked the token (e.g., during a security audit), you'll see an "Unauthorized" error. Generate a new API token:

1. Go to **Settings** → **APIs** → **API Tokens**
2. Click **Create Token** and select the appropriate scope
3. Update the token in Coupler.io and test again

</details>

### Data discrepancies

<details>

<summary>Record counts don't match between Zoho CRM and Coupler.io destination</summary>

This can happen for a few reasons:

1. **Time zone differences**: Zoho CRM stores all dates in UTC. If you set a start date, records created near midnight in your time zone may fall on different sides of the UTC boundary. Use a date range with a few days of buffer.
2. **Duplicate records**: If Coupler.io isn't set to replace old data (it appends by default), you may see duplicates on subsequent runs. Check your data flow settings and enable **Replace** mode if needed.
3. **Soft-deleted records**: Zoho CRM may include records marked as deleted or archived. If Coupler.io's destination uses **Append** mode, these may appear alongside active records.
4. **Filters or field-level security**: Your Zoho admin may have filtered records or restricted certain fields, reducing the data Coupler.io can access.

</details>

<details>

<summary>Deal amounts or other numeric fields show as text or zero</summary>

Zoho CRM's API sometimes returns numeric fields as text strings. In your destination:

* **Google Sheets**: Format the column as **Number** and use `=VALUE()` to convert if needed
* **Excel**: Use **Format Cells** → **Number** or apply a formula like `=VALUE(A1)`
* **BigQuery**: Cast the column as `CAST(field AS FLOAT64)`

Alternatively, set up a transformation in Coupler.io if the source data is consistently mistyped.

</details>

### Rate limits

<details>

<summary>"Rate limit exceeded" or "Quota exceeded" error</summary>

Zoho CRM's API rate limits depend on your edition:

* **Free**: 100 API calls/minute
* **Standard**: 1,000 API calls/minute
* **Professional & up**: Significantly higher; see Zoho's documentation

If you hit the limit:

1. **Wait 1 minute** before retrying — the quota resets per minute
2. **Reduce batch size**: Sync fewer modules or fields per data flow
3. **Stagger schedules**: If you have multiple Coupler.io data flows, schedule them 10–15 minutes apart so API calls don't pile up
4. **Consider upgrading**: If you consistently hit limits, upgrading your Zoho CRM edition increases your quota

</details>

<details>

<summary>Scheduled data flow fails intermittently</summary>

Intermittent failures often indicate hitting rate limits during peak hours. Try:

1. **Schedule the data flow for off-peak hours** (early morning or late evening in your time zone)
2. **Increase refresh interval**: Instead of hourly syncs, switch to every 6 hours or daily
3. **Reduce data scope**: Sync only the essential modules and fields
4. **Check Zoho's system status**: Zoho CRM may have maintenance windows that temporarily limit API availability

</details>

## Zoho CRM FAQ

<details>

<summary>Can I sync data from multiple Zoho CRM environments (Production, Sandbox) to the same destination?</summary>

Yes, you can create separate data flows for each environment. For example, create one data flow for Production Deals and another for Sandbox Deals. If you want them merged, use an **Append** transformation in Coupler.io to combine them into a single table.

</details>

<details>

<summary>Do I need a separate API token for each data flow?</summary>

No, you can reuse the same token across multiple data flows. All data flows using the same token will count against your Zoho CRM API quota, so be mindful of rate limits if you have many concurrent syncs.

</details>

<details>

<summary>What's the difference between syncing Contacts and Leads?</summary>

**Leads** are prospects you haven't converted yet; they typically have less rich data (name, email, company). **Contacts** are people linked to a specific Account and usually have deeper relationship history (phone, address, linked deals, activity log). Many teams sync both to track the full funnel from prospect to customer.

</details>

<details>

<summary>How do I sync custom modules or custom fields?</summary>

Custom modules and fields appear in Coupler.io's module list if your Zoho CRM admin has enabled them and granted you read access. When you select a module, all available fields (standard and custom) will appear. If a custom field is missing, ask your admin to verify API access is enabled for your user role.

</details>

<details>

<summary>Can I filter data by criteria (e.g., only "Closed Won" deals)?</summary>

Zoho CRM's API doesn't support filtering at the source level in Coupler.io. Instead, filter in your destination after the data syncs. In Google Sheets or Excel, use formulas or built-in filters. In BigQuery, use WHERE clauses. For a more reusable approach, use Coupler.io's filter transformations if available, or a BI tool like Looker Studio.

</details>

<details>

<summary>How often should I refresh my data flow?</summary>

It depends on how fast your data changes and your API quota:

* **Sales pipelines (Deals)**: Daily or every 6 hours if frequently updated
* **Contacts/Accounts**: Daily if your team actively adds and updates them
* **Reports (read-only summaries)**: Weekly if historical accuracy matters more than real-time sync

Start with daily and adjust based on your refresh latency tolerance and API quota remaining.

</details>

<details>

<summary>Why is my data appearing as duplicates in the destination?</summary>

If your data flow is set to **Append** mode (the default), it adds new rows without removing old ones. To replace old data with fresh data each sync, change the data flow's mode to **Replace**. Check your Coupler.io data flow settings to confirm which mode is active.

</details>

<details>

<summary>Can I send Zoho CRM data to an AI destination like Claude or ChatGPT?</summary>

Yes! You can sync Deals, Leads, or Accounts to Claude, ChatGPT, Gemini, Perplexity, or other AI destinations. Once the data flows, you can prompt the AI to analyze your pipeline (e.g., "Identify the top 5 at-risk deals and suggest retention strategies" or "Summarize lead sources and recommend budget allocation"). This is useful for quick insights without building a custom dashboard.

</details>

<details>

<summary>How do I handle timezones when syncing date fields?</summary>

Zoho CRM stores all dates and times in UTC. Coupler.io preserves UTC values in the export. To convert to your local timezone:

* **Google Sheets**: Use `=A1 + TIME_ZONE_OFFSET()` or a similar formula
* **Excel**: Apply a formula like `=(A1 + (your_offset / 24))`
* **BigQuery**: Use `DATETIME(date_field, 'America/New_York')` to convert on query

If dates matter for reporting, convert them after syncing.

</details>

{% hint style="info" %}
For more details on available modules and metrics, see the **Data Overview** article. For help troubleshooting connection or data issues, check **Common Issues**.
{% endhint %}


---

# 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.coupler.io/sources/category/crm/zoho-crm.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.
