Source connector

Zoho CRM connector

Zoho CRM integration for databases, warehouses and BI tools

Modular CRM with strong automation and telephony. Datrise captures Zoho CRM entities such as leads, contacts, accounts, deals, and workflow-driven field changes, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Zoho CRM API v7 authenticates with OAuth 2.0, incremental runs key on Modified_Time (If-Modified-Since header), and Zoho CRM caps calls at credit-based per organisation per day: 5,000 (Free) up to 50,000 + per-license increments capped at 5,000,000/day (Enterprise) or unlimited (Ultimate); no per-minute cap, but concurrency is capped at 5-25 simultaneous calls depending on edition.

Of the 5 objects, 4 sync as upserts keyed on the primary key and 1 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `zoho_crm_leads`) with a schema derived from the Zoho CRM API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the Zoho CRM pipeline page, and join the waitlist to get the Zoho CRM connector (CRM) with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Zoho CRM data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
leads	zoho_crm_leads	Upsert by primary key, incremental on updated-at
contacts	zoho_crm_contacts	Upsert by primary key, incremental on updated-at
accounts	zoho_crm_accounts	Upsert by primary key, incremental on updated-at
deals	zoho_crm_deals	Upsert by primary key, incremental on updated-at
workflow-driven field changes	zoho_crm_workflow_driven_field_changes	Append-only, incremental by timestamp

Zoho CRM API: setup facts for the connector

Verified against the vendor documentation on 2026-09-02. Unknown values are left blank rather than guessed.

API	Zoho CRM API v7
Authentication	OAuth 2.0 — OAuth 2.0 only, with access tokens valid for 1 hour and a refresh token that stays valid indefinitely until revoked; self-client, server-based and mobile-based grant flows are all supported.
Pagination	page — `GET /records` uses `page`/`per_page` (per_page max 200) for the first 2,000 records, then requires the opaque `page_token` (from `next_page_token`, valid 24 hours) to page further, up to 100,000 records total.
Rate limit	credit-based per organisation per day: 5,000 (Free) up to 50,000 + per-license increments capped at 5,000,000/day (Enterprise) or unlimited (Ultimate); no per-minute cap, but concurrency is capped at 5-25 simultaneous calls depending on edition
Incremental cursor	Modified_Time (If-Modified-Since header) — `GET /records` honors an `If-Modified-Since` request header (ISO-8601 timestamp) to return only records changed after that time.
Webhooks	Yes — Notification APIs (`POST /actions/watch`)
Bulk export	Yes — Bulk Read API (`POST /crm/bulk/{version}/read`, async job + `page_token`)
Deletes detectable	Yes — The Get Deleted Records API (`type=recycle\|permanent\|all`) lists deletions with actor and timestamp: recycle-bin entries for 60 days, permanently-deleted entries for 120 days after the fact.

Official API reference

What bites when replicating Zoho CRM

Standard `page`/`per_page` pagination stops working past 2,000 records; beyond that you must switch to the `page_token` returned as `next_page_token`, which is user-specific and expires after 24 hours if you stop mid-sync.
Get Deleted Records only guarantees visibility for a limited window — 60 days for recycle-bin deletions, 120 days for permanent ones — so a connector that syncs less often than every 60-120 days will silently miss deletions that fall outside the window.
The daily API budget is a shared credit pool, not a flat per-endpoint count, and 'some APIs' (per Zoho's own docs) consume more than 1 credit per call, so identical-looking Bulk Read or Convert-Lead calls can drain the quota far faster than simple `GET /records` calls.
Webhook (`actions/watch`) subscriptions expire after at most `channel_expiry` of one week, and default to just 1 hour if the field is omitted or set beyond a week, so an unmonitored webhook silently stops delivering `create`/`edit`/`delete` events until manually re-enabled.

Compare this against every other documented API

Popular destinations for Zoho CRM

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

Zoho CRM connector FAQ

What Zoho CRM data does the connector extract?: 5 objects: leads, contacts, accounts, deals and workflow-driven field changes. Each lands in its own table with types preserved; history-style objects (1: workflow-driven field changes) load as append-only streams.
Is the Zoho CRM integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load Zoho CRM data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Zoho CRM → destination pair has its own page with the object-to-table mapping.

Related CRM sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Zoho CRM pipeline with guided onboarding

Join the waitlist to get priority access for Zoho CRM integrations with guided setup, schema-aware mapping, and production-grade incremental sync.