Zoho CRM connector FAQ

Important

This feature is in Beta. To use it, a workspace admin must turn on Lakeflow Connect for Zoho CRM from the Previews page. See Manage Azure Databricks previews.

This page answers frequently asked questions about the managed Zoho CRM ingestion connector in Lakeflow Connect. For FAQs that apply to all managed connectors, see Managed connector FAQs.

Which Zoho CRM editions does the connector require?

The connector works with any Zoho CRM edition. API access is available in all editions, and daily API credits and concurrency limits scale with your edition. The territories and user_territories tables require Enterprise edition or above, and the currencies table requires Professional edition or above. See Zoho CRM API limits.

Which tables does the connector support?

The connector supports standard modules such as leads, contacts, accounts, and deals, line-item tables, settings tables such as users, roles, and stages, and one table for each custom module. For the full list, see Supported source tables.

Does the connector support custom modules and custom fields?

Yes. The connector discovers custom modules that are API-supported and viewable, and creates one table for each. Module tables include custom fields because the connector builds each schema from the module's field metadata.

How far back can the connector ingest data?

For incremental tables, the first sync ingests records modified on or after the required start_datetime option. Each later sync ingests records modified after the last run. Full-refresh tables reingest all available records on every run.

Does the connector capture deleted records?

No. Records deleted in Zoho CRM remain in destination tables until you run a full refresh. See Deleted records.

Which authentication methods does the connector support?

The connector supports authentication using OAuth client credentials (M2M) with a Zoho Self Client only. OAuth U2M and basic authentication aren't supported.