Send chatbot leads to Zoho CRM
Into the module you choose, in your own data centre
A lead from the chat becomes a record in the Zoho module you pick, in the data centre your account actually lives in -- asked for rather than guessed, because guessing it fails in a way that reads like a bad token.
What it does
Your data centre, not a default
Zoho runs separate estates. An account created in Europe does not exist on .com, and a token minted in one is refused by the other. The connection asks which is yours.
Modules and fields from your account
The picker lists the modules your account can create in, standard and custom, and the mapper offers the fields each one has.
Picklists that hold
A picklist value Zoho does not have is left out rather than sent, because a refused value fails the whole record.
How to connect it
Read the full guide- 1
Create a Self Client
In Zoho's API console, with the three scopes the connection screen lists.
- 2
Generate a refresh token
Once, from that Self Client. It does not expire on its own.
- 3
Connect Zoho CRM
Paste the client id, the secret and the refresh token, and pick your data centre.
- 4
Map the fields
Auto-map, then check it. Leads and Contacts need a last name, and it is filled in when the mapping leaves it out.
Questions people ask
Why does it ask for a data centre?
Because Zoho has several and they do not share accounts. Sending a European account to the US endpoint produces an authentication error that looks like a credential problem and is not.
Does it work with custom modules?
Yes. Anything your account can create in appears in the picker, with its own fields.
What if a field is rejected?
Zoho answers with a per-record status inside a successful response. We read it and fail the dispatch with the reason, rather than recording a success that did not happen.
What teams use it for
Upload your documents, get answers that cite them
One knowledge base, an AI chat or an Ask AI search on any site, and every answer with the passage it came from. Free for 14 days.