​
Symptom

The Zoho Connection tab shows a Missing scopes warning, or automation installs and agent tools fail with Zoho permission errors.

​
Root cause

At OAuth consent, Zoho shows the scope list Kylo requested, and it can be trimmed before approving. Kylo’s default grant is 20 scopes covering leads, contacts, deals, notes, tags, workflow automation, field metadata, and search. When fewer come back, the features that needed the missing scope stop working even though the connection itself is fine. Kylo compares the granted scope string with the requested set and lists what is missing, with covering rules: a granted ZohoCRM.modules.ALL covers every module scope, a granted ZohoCRM.modules.READ covers ZohoCRM.modules.leads.READ, and ZohoCRM.modules.leads.ALL covers that module’s operations.

​
What each area needs

The areas group the scopes by feature. The app shows only the Missing scopes list, so use this table to map a scope to the feature that fails.

​
The fix

Select Disconnect on the Zoho Connection tab, connect again, and keep the scopes the warning names. The warning clears when the widened grant lands. Disconnect removes the Kylo workflow rules from Zoho, so install your automations again afterwards. If the install still fails with an edition or license error, your Zoho org’s plan does not include the automation or tags APIs; that is a Zoho edition upgrade, not a scope fix.

​
Sources