Skip to content
Verbatik
GuidesAPI reference

Integrations

Zoho CRM

Connect Zoho CRM, obtain the required access and configure permitted actions.

The API adapter is implemented. Validate your own account and authorized actions before routing production calls.

Before you start

Connect the account belonging to this business and workspace. Vendor subscriptions, API limits and role permissions still apply.

API: Zoho CRM REST API v8

Authentication: Zoho OAuth; client ID, client secret and refresh token are needed for ongoing use

Get access and connect

  1. Use a Zoho CRM organization and open the Zoho API Console at https://api-console.zoho.com/ for the organization's data center. Register a Server-based Application for a web authorization flow, or a Self Client for a customer-controlled single-account setup.
  2. Select the CRM module scopes required by the actions. Request offline access when completing the initial grant and exchange the one-time grant code for an access token and refresh token using the matching Zoho Accounts data-center endpoint.
  3. Set Verbatik's instanceUrl to the API domain returned in that token receipt, such as https://www.zohoapis.eu. Enter clientId, clientSecret and refreshToken in the integration's encrypted credential fields; accessToken is optional when renewal is fully configured.
  4. Verbatik renews short-lived tokens using the fixed Accounts host mapped to that data center and checks the returned api_domain. Do not mix a production organization's refresh token with a sandbox or another Zoho organization.
  5. Run Test connection (CurrentUser). Enable selected actions and use the organization's field API names for generic record writes, including all required custom fields.
  6. Verbatik suppresses Zoho workflow triggers by default. Set triggerWorkflow only for a deliberately configured record action that should execute the organization's workflows.

Account requirements

  • A CRM user with the corresponding module, record and field permissions is required. The client can request per-module READ/CREATE/UPDATE scopes instead of ALL when the enabled actions allow narrower access.
  • Access tokens expire after one hour. A standalone pasted access token is temporary; provide the complete OAuth renewal configuration for ongoing use.
  • The selected API data center must match the authorization account. Supported data centers are US, EU, India, Australia, China, Japan and Canada.
  • Zoho may return HTTP success with record-level errors. Verbatik rejects those receipts rather than confirming a failed action. API credits, edition restrictions and organization validation rules still apply.

Permissions

  • ZohoCRM.users.READ
  • ZohoCRM.modules.contacts.ALL
  • ZohoCRM.modules.accounts.ALL
  • ZohoCRM.modules.leads.ALL
  • ZohoCRM.modules.deals.ALL
  • ZohoCRM.modules.tasks.ALL
  • ZohoCRM.modules.calls.ALL
  • ZohoCRM.modules.notes.ALL

Grant the subset needed for the actions you enable. API scopes do not override the connected user’s record permissions or vendor validation rules.

Connection fields

  • accessToken — Zoho access token (optional with automatic renewal) (optional). Secret fields are saved as workspace credentials.
  • clientId — OAuth client ID (automatic renewal) (optional). Secret fields are saved as workspace credentials.
  • clientSecret — OAuth client secret (automatic renewal) (optional). Secret fields are saved as workspace credentials.
  • refreshToken — OAuth refresh token (automatic renewal) (optional). Secret fields are saved as workspace credentials.
  • instanceUrl — Zoho API data-center origin (optional).

Available actions

  • test_connection — Read · available for after-call automation. Read account or schema metadata to verify credentials without creating records.
  • find_contact — Read · available for after-call automation. Search Zoho contacts by email.
  • get_record — Read · available for after-call automation. Read a known Zoho CRM record.
  • create_contact — Write · available for after-call automation. Create a Zoho contact. Last name is mandatory.
  • create_record — Write · available for after-call automation. Create a supported Zoho record with module API fields. Supply required fields, for example Last_Name for leads, Deal_Name/Stage for deals, and Subject for tasks.
  • update_record — Write · available for after-call automation. Update a known Zoho record, optionally triggering configured workflows.
  • add_note — Write · available for after-call automation. Attach a note to a supported Zoho CRM record.
  • create_task — Write · available for after-call automation. Create a Zoho follow-up task using a known contact ID when supplied.
  • log_call — Write · available for after-call automation. Record a completed incoming or outgoing call. Duration uses HH:mm. Does not dial.

Verify before going live

Run Test connection and one read action against a known permitted record. Then test each intended write in an authorized sandbox. Check the provider’s own record and the Verbatik receipt. Publish the agent after assigning its tools. If a write has an unknown outcome, reconcile it with the vendor before trying again.

Vendor documentation

Verbatik documentation · Updated November 5, 2026
Previous

GoHighLevel

Next

Zendesk