Swarmz
IntegrationsCRM, sales, and recruiting

Zoho CRM

Inspect Zoho CRM modules and fields, then read, create, update, or upsert records

Connect Zoho CRM when a project needs current sales records or must change CRM data. A shared connection uses one authorized Zoho CRM user for a project. A published app can ask each signed-in app user to authorize their own Zoho CRM account.

Before you connect

A Swarmz administrator must configure and enable the Zoho CRM OAuth application before the connector appears. Each Zoho user still signs in and approves access; the administrator's client secret is never used as a user's credential.

Create a server-based OAuth client in the Zoho API Console. Add the callback URL shown on the Zoho CRM card in Admin > Settings > Integrations. If users can belong to more than one Zoho data center, enable Multi-DC support for the client.

Copy the client ID and client secret into the Swarmz admin card, complete Test, then enable the connector. The secret is write-only. To replace it, rotate the secret in the Zoho API Console and enter the new value in Swarmz.

Available operations

OperationWhat it doesLimit per minute
list_modulesLists modules visible to the connected user30
list_fieldsLists fields for one module30
list_recordsLists up to 200 records from one module30
get_recordReads one record by module and ID30
search_recordsSearches one module by email, phone, or word20
create_recordCreates one record10
update_recordUpdates one record by ID10
upsert_recordCreates or updates one record using duplicate-check fields10

The connector uses Zoho CRM API v8 and the API domain for the selected data center. List and search requests return at most 200 records per call. Search supports one email, phone, or word input; arbitrary criteria are not exposed. Write operations pause for AI approval during a build.

Connect Zoho CRM

In Settings > Integrations, select Zoho CRM, then select Connect new.

  1. Select the data center that holds the Zoho account: US, EU, India, Australia, Japan, Canada, or China.
  2. Select read access. Add write access only when the project will create, update, or upsert records.
  3. Sign in to the intended Zoho account and approve access.
  4. Link the connection to the project.

For an internal pipeline view, ask: “Use our shared Zoho CRM connection to list open Deals and show the related Accounts.” For a multi-tenant app, ask: “Let each signed-in app user connect Zoho CRM, then search Contacts and update Deals in their own account.” See Connector connection modes before choosing between a shared and app-user connection.

Verify Zoho CRM

  1. List modules and confirm that a known standard or custom module appears.
  2. List fields for Contacts and check a known field API name.
  3. List records from a test module and compare the result in Zoho CRM.
  4. Search for a test contact by email, phone, and a name word.
  5. With write access, create a disposable record and update one field.
  6. Upsert the record through a test unique field, then confirm Zoho updated the existing record instead of creating a duplicate.
  7. Delete the disposable record in Zoho CRM. The connector deliberately does not expose delete operations.

If authorization opens the wrong regional sign-in page, cancel it and select the account's data center before reconnecting. If reads work but writes fail, reconnect with write access and confirm the Zoho user's profile can edit that module. A newly changed record may not appear in search immediately because Zoho indexes search separately; read it by ID when you need an immediate check.

On this page