- Connect with a consent link approved once by a Zoho admin — Apivom's own client, every Zoho data centre (US, EU, IN, AU, JP, CA, SA, AE, SG, UK, CN)
- Read-only scopes: core modules (Leads, Accounts, Contacts, Deals, Products, Quotes, Sales Orders, Invoices) or all modules
- Mirror via COQL: full load first, then incremental on Modified_Time; deleted records reconciled daily
- Import Accounts → companies, Contacts → contacts, Deals → opportunities (stage mapping, lost reasons), Quotes/Sales Orders/Invoices → documents with lines, Tasks → activities
- Paced at least 400 ms apart and self-capped at 25 % of your organisation's daily API credits
- Access check shows which modules the granted consent can actually read
Zoho CRM API Connector
Read-only import from Zoho CRM into Apivom Iris: a Zoho admin approves a consent link once, then Accounts, Contacts and Deals are mirrored into your tenant and kept current with incremental loads — across every Zoho data centre, without ever writing to Zoho.
What you can do
Use cases
- Migrate or run in parallel without risk — Bring your Zoho pipeline into Iris while the sales team keeps working in Zoho — the feed is read-only, so nothing you do in Iris can alter the Zoho organisation.
- Group-wide reporting over several Zoho organisations — Connect each subsidiary's Zoho org (in its own data centre) to one Iris tenant and report on accounts, contacts and deals in one place with consistent stages.
- Keep opportunities current every day — Incremental loads on Modified_Time plus the daily deleted-records pass keep Iris opportunities and their stages aligned with Zoho Deals without manual exports.
Zoho CRM's REST API exposes every module of a Zoho organisation — Leads, Accounts, Contacts, Deals, Products, Quotes, Sales Orders, Invoices, custom modules — plus COQL, its SQL-like query language. Apivom Iris uses it as a one-way, read-only feed — nothing is ever written to Zoho. Connecting is a consent link a Zoho administrator approves once; Apivom's API client is registered in every Zoho data centre, so each organisation uses its own host. A first full load mirrors the selected modules into your tenant; incremental runs then query on Modified_Time and a daily pass reconciles deletions. From the mirror, Iris imports Accounts as companies, Contacts as contacts and Deals as opportunities, mapping Zoho stages to your pipeline and reading the lost reason from a custom field; Quotes, Sales Orders and Invoices arrive as documents with their lines, Tasks as activities, and Zoho users become the record owners. Requests are paced at least 400 ms apart and the connector stops at 25 % of your organisation's daily API credits, leaving the rest to your own Zoho users. The access check shows which modules the consent can read before the first import.
OAuth consent flow using Apivom's multi-data-centre Zoho client: a Zoho admin approves read-only scopes once; Iris refreshes the token at accounts.zoho.{dc} itself and sends Zoho-oauthtoken per request. Apivom Atlas stores no credential; the refresh token is encrypted in your Iris tenant.
Frequently asked questions
Does Iris write anything back to Zoho CRM?
No. The granted scopes are read-only and the connector contains no write path: Accounts, Contacts and Deals are mirrored into your tenant and imported there, but Zoho records are never created, updated or deleted by Apivom.
How often does the mirror refresh and does it consume my Zoho API credits?
After the initial full load, incremental runs on a schedule fetch only records changed since the last Modified_Time, and a daily pass reconciles deletions. Calls are at least 400 ms apart and the connector self-caps at 25 % of the organisation's daily API credits, leaving the rest for your own integrations.
Which Zoho data centres are supported?
All current Zoho data centres: zohoapis.com (US), .eu, .in, .com.au, .jp, .ca, .sa, .ae, .sg, .uk and .com.cn. The consent link detects the organisation's data centre and both the token refresh and the API calls go to the matching host.
Does Apivom charge per API call for this connector?
No. Connectors are part of your Apivom tenant and are not metered in the Atlas portal. The vendor's own pricing, quotas and rate limits still apply to the account you connect — Apivom paces its calls to stay inside them and shows every call in your tenant's integration log.
Where are my credentials stored and who can see the traffic?
Apivom Atlas is a stateless gateway: it never stores vendor credentials or tokens. The Apivom product that connects keeps the credential encrypted in your tenant database, and every request and response is logged in your tenant only — your data is never shared across tenants.
More Atlas integrations
AI integration guide (llms.txt)
Machine-readable markdown — feed it to your AI assistant as integration instructions.