Zoho CRM
Read and write Zoho CRM leads, contacts, accounts, deals and custom modules.
Connect it with: Sign in (OAuth). Zoho CRM's own documentation: https://www.zoho.com/crm/developer/docs/api/v8/auth-request.html.
What agents can do
Connect Zoho CRM so the agents working your tasks can reach it. With it connected, they can:
- Create and update leads, contacts, accounts and deals, and convert leads.
- Read and write custom modules and their fields.
- Search records by criteria, email or phone, or query them with COQL.
- Add notes and tasks to records so the follow-up stays in Zoho CRM.
Before you start
- A Zoho CRM user whose profile has API access (Zoho CRM Standard edition or higher).
- A Zoho account in the US data center (you sign in at accounts.zoho.com).
- A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.
Connect with Zoho CRM
This is the quickest way in: you sign in to Zoho CRM and approve what Jaah asks for. You never copy a key.
- In Jaah, open Secrets and select New.
- Search for Zoho CRM and select its card.
- Give the secret a name you will recognize, such as the account or workspace it reaches, and choose who can use it (see Who can use it).
- Select Connect Zoho CRM. Zoho CRM's sign-in window opens.
- Sign in to Zoho CRM if asked, check the access listed, and approve it.
- You land back in Jaah on the new secret, which reads Connected once its test passes.
If the button reads Jaah app not configured, this Jaah has no app registered at Zoho CRM yet. Use your own OAuth app until it does (see Use your own OAuth app).
Scopes Jaah requests
Jaah asks Zoho CRM for these scopes, and no others. A scope marked optional is a checkbox on the Connect screen: untick it and agents simply cannot do that part.
| Scope | Why Jaah asks for it | Required |
|---|---|---|
ZohoCRM.modules.ALL | Read, create, update and delete records in every module, custom modules included | Yes |
ZohoCRM.users.READ | Read users: Test names who connected and agents can assign record owners | Yes |
ZohoCRM.settings.READ | Read layouts, fields and picklists so records match your setup | No — you may untick it |
ZohoCRM.coql.READ | Run COQL queries for filtered reads across modules | No — you may untick it |
Connect with an API key
Zoho CRM has no API key option in Jaah: connect with the sign-in above.
Use your own OAuth app
Register your own OAuth app at Zoho CRM when your company requires apps it controls, or before this Jaah has an app registered there.
- Create an OAuth app in Zoho CRM's developer console, https://api-console.zoho.com/ (Zoho CRM's documentation).
- Set its redirect URI to
https://app.jaah.ai/api/credentials/connect/callback(on your own Jaah, its console address followed by/api/credentials/connect/callback). - Give it the scopes in Scopes Jaah requests.
- Copy its client ID and client secret.
- In Jaah, start a new Zoho CRM secret, select Use your own OAuth app, paste both values and select Connect Zoho CRM.
The client secret is stored with the connection, encrypted, like any other secret value.
Test the connection
Select Test on the secret. Jaah calls Zoho CRM's API once (GET https://www.zohoapis.com/crm/v8/users?type=CurrentUser) with the stored values, and shows who it answered as, or which value Zoho CRM refused and the status it answered. Jaah also tests automatically when you save or reconnect.
The last result and its time stay on the secret's page, so you can see whether it still works without testing again.
Who can use it
Every secret has an owner, and the owner decides who can use it:
- Personal — only your own tasks can use it. This is the default.
- Organization — every task in the organization can use it. Only Org Owners and Admins can choose this.
- Attached to a project — every task on that project can use it, whoever started the task. See Attach a secret to a project.
More on owners and access: How secrets work.
Use it in an agent session
An agent asks for the secret with its credential_get tool, by the secret's path, when it needs it, and gets the values for that one call. The path is the owner's prefix and the secret's name:
org/<name>for an organization secret,projects/<project>/<name>for one attached to a project,me/<name>for your personal one.
A signed-in connection hands the agent a live access_token, with access_token_expires_at. Jaah refreshes it before it expires, so an agent never handles a refresh token.
Tell the agent in your task description which secret to use, for example “use the Zoho CRM secret org/zoho-crm”.
Manage, rotate or disconnect
Everything is on the secret's page under Secrets:
- Reconnect: when Zoho CRM ends the grant (a password change, a revoked app, an expired refresh), the secret shows Needs reconnect. Select Reconnect and sign in again; agents get the new token on their next call.
- Disconnect: select Delete. The stored values are destroyed and agents lose access on their next call. To end access at Zoho CRM's side too, revoke Jaah in Zoho CRM's settings.
Limitations
- Only Zoho accounts in the US data center (zoho.com) can connect today; accounts in the EU, India, Australia, Japan, Canada, China or Saudi Arabia data centers cannot.
- Agents act as the user who connected, with that user's profile permissions and data sharing rules.
- Zoho CRM counts every call against the org's API credits for 24 hours, set by edition and number of licenses.
- Agents send the token as
Authorization: Zoho-oauthtoken <access_token>to https://www.zohoapis.com, Zoho's own scheme. - Agents can do only what the connected Zoho CRM account and its granted scopes allow.
Troubleshooting
The Zoho window shows invalid_client or 'Invalid Redirect Uri'
Your account is outside the US data center, or the Jaah app's redirect URI does not match. Check that you sign in at accounts.zoho.com; accounts in other data centers cannot connect yet.
Test says Zoho CRM rejected the access token (401) or the secret shows Needs reconnect
The grant was revoked under Zoho Accounts > Sessions > Connected Apps, or Zoho dropped the refresh token after more than 20 were issued. Select Reconnect and approve again.
An agent gets OAUTH_SCOPE_MISMATCH
You unticked an optional scope the call needs (settings or COQL). Select Reconnect and keep that scope ticked.
An agent gets LIMIT_EXCEEDED or 'API calls limit exceeded'
The org's daily API credits are spent. A Zoho CRM admin checks Setup > Developer Hub > APIs and SDKs > Dashboard, or buys more credits.
Still stuck? Select Test and read the result: it names the value Zoho CRM refused and the status it answered.
FAQ
Does connecting Zoho CRM give access to other Zoho apps?
No. Jaah asks only for Zoho CRM scopes; Zoho Books, Desk and the others need their own connection.
Why does Zoho ask me to approve again each time I connect?
Jaah asks Zoho for a fresh consent so Zoho issues a refresh token; without one the connection would stop after an hour.
Can Jaah or an admin see the key or token?
No. Jaah stores it encrypted and never shows it again. Only the tasks allowed to use the secret receive it, at the moment they ask for it.
Can I connect more than one Zoho CRM account?
Yes. Add one secret per account, each with its own name, and tell the agent which one to use.