Zoho connection

Zoho CRM is the system of record for lead data. The agent reads and writes records through its Zoho tools, and outbound sends start from Zoho workflow events. Each agent has its own Zoho connection.

​

How the connection works

1. You choose a data centre and scopes in the Connect Zoho CRM dialog and select Connect.
2. Kylo sends you to Zoho’s consent screen on that data centre. Kylo asks for offline access and always forces the consent screen, so Zoho issues a refresh token.
3. You approve. Zoho redirects back to Kylo, which stores the tokens encrypted and shows Zoho CRM connected on the Integrations page.
4. Kylo uses the refresh token to get short-lived access tokens when it calls Zoho, so no one signs in again.

The OAuth state is signed, so a tampered redirect cannot attach a connection to another workspace.

​

Data centres

Zoho runs separate regions, and each has its own sign-in and API host. The dialog offers seven: The default is United States. A wrong region fails at Zoho’s sign-in. See Zoho multi data centre support.

​

The Connection tab

On the Zoho CRM card select Manage. The tab shows three rows: When Zoho granted fewer scopes than Kylo requested, a Missing scopes warning lists them. A disconnected agent shows Disconnected and “Connect Zoho CRM from Integrations.”

​

What the connection unlocks

• The Zoho tool group on the agent’s Tools page. See Agent tools.
• The Fields, Automation, and Tags tabs. See Zoho fields, Zoho automations, and Zoho tags.

​

Disconnect

Disconnect first removes the Kylo workflow rules and webhook actions from your Zoho org, then deletes the stored tokens. If the teardown cannot reach Zoho, Kylo still removes the connection. Triggers that used the removed automations stop firing.