Create a Self Client in the Zoho API console, generate a grant code with two scopes, and paste the client ID, client secret and code into Mantis with your data centre; then select leads and click Send to CRM. Each lead becomes a Zoho CRM Lead with Lead Source "Mantis", and sending again updates the same record instead of duplicating it.
The short answer
Each lead lands in Zoho as a Lead with Lead Source set to "Mantis". Mantis's Integrations → CRM page lists five destinations — HubSpot, Zoho CRM, Pipedrive, Freshsales and Webhook — so if Zoho isn't your only option, the CRM routes comparison covers all five, and there is a separate guide for sending Google Maps leads to HubSpot.
Pick your Zoho data centre first
Mantis's Zoho form has four fields: Data centre, Client ID (which looks like `1000.XXXXXXXX`), Client secret and Grant code. The data centre dropdown offers India (zoho.in), US (zoho.com), Europe (zoho.eu) and Australia (zoho.com.au).
Your data centre is the domain you log in to Zoho on, and the API console address must match it: api-console.zoho.in, api-console.zoho.com, api-console.zoho.eu or api-console.zoho.com.au. If the data centre you pick in Mantis doesn't match the console you used, Zoho rejects the client ID and secret.
Zoho also runs China (.com.cn), Japan (.jp) and Canada (zohocloud.ca) data centres. These are not in Mantis's list, so accounts hosted there can't connect this way today — the closest route is Mantis's webhook to Zapier, Make or n8n, passing leads on to Zoho from there if your automation tool supports your data centre (see the CRM comparison guide).
Step 1: Create a Zoho Self Client and a grant code
This follows Zoho's documented authorization flow (see Zoho's docs):
The two scopes do specific things: `leads.ALL` lets Mantis create and update Leads, and `org.READ` lets Mantis read your organization name to confirm the connection. As of 15 November 2026, Zoho's v8 docs show no change to the Self Client / grant-code flow.
Step 2: Connect Zoho CRM in Mantis
Paste the data centre, Client ID, Client secret and grant code into Mantis's Zoho form and connect within the code's time window — a grant code works once, and Mantis swaps it for a refresh token straight away.
Mantis checks the credentials with Zoho before saving: it exchanges the code, then reads your organization. The credentials are stored encrypted and never shown again. Zoho access tokens last an hour and refresh tokens last until revoked, so you normally set this up once and reconnect only if Zoho rejects the access.
Step 3: Select leads and send them
In Mantis, go to Leads, select the rows you want, and click Send to CRM. You can send up to 500 leads at a time. If you're still deciding how to collect Google Maps leads in the first place, see the Google Maps scrapers comparison.
What each lead looks like in Zoho CRM
Mantis maps its fields to Zoho Lead fields like this:
| Mantis field | Zoho Lead field |
|---|---|
| Business name | Company |
| Person's last name (or the business name if there's no person) | Last Name |
| First name | First Name |
| Role | Designation |
| Phone | Phone |
| Website | Website |
| Area | City |
| — (set automatically) | Lead Source = "Mantis" |
| Category, area, rating & reviews, signals, score, contact role, LinkedIn, list name | Description |
Empty fields are skipped, and Last Name and Company are the Leads module's required fields.
How duplicates are handled
On the first send, Mantis upserts on Email when the lead has one, so a Lead already in Zoho with that email is updated rather than duplicated. Sending the same lead again updates the same record by id. If the record was deleted in Zoho since the last send, it is created again. One honest caveat: a lead with no email on its first send is created as new, because there is no email to match on.
If something fails
| What Mantis says | Fix |
|---|---|
| Client ID/secret rejected | Copy both again from the Client Secret tab and check the data centre |
| Grant code rejected | It expired or was used; generate a new one and connect straight away |
| No refresh token | Generate a new code |
| Scope refused | Regenerate the code with both scopes |
| Access rejected | Disconnect and reconnect with a new code |
| API limit | Wait a minute and send again |
These are the messages Mantis shows, shortened. A rejected token stops the batch early. Zoho limits how many access tokens a refresh token can mint in ten minutes, so Mantis mints one per batch and reuses it, instead of asking Zoho for a new one per lead.
Send your next list straight to Zoho CRM
Find local businesses, select them, Send to CRM. 500 free credits once at signup, no card.
Start freeI'm Tarun, founder of Mantis.
Frequently asked questions
Do I need a paid Zoho CRM plan?
Mantis only needs a Self Client grant code with the two scopes on your organization. What your Zoho edition allows API-wise is a Zoho question — check Zoho's edition details for your plan.
Why did my grant code stop working?
A grant code works once and expires after its set duration — 10 minutes if you followed Step 1. Generate a new one and connect straight away.
My Zoho account is on zoho.jp, zohocloud.ca or .com.cn — can I connect?
Not through this form today; those data centres aren't in Mantis's list. The webhook route in the [CRM comparison guide](/resources/send-google-maps-leads-to-crm) is the alternative.
What happens if I disconnect?
Leads already sent stay in Zoho CRM.
Related reading
send Google Maps leads to HubSpot · Google Maps leads to CRM: 5 ways · Google Maps scrapers compared
