The Fields tab shows the fields of your Zoho org as Zoho reports them, including custom fields. Use it to confirm API names before you write them in instructions or pick them in a trigger. Kylo does not copy fields into a separate mapping. It reads the fields it needs from Zoho at the moment an event or a tool call needs them.

​
Before you start

  • A connected Zoho org with ZohoCRM.settings.fields.READ and ZohoCRM.settings.modules.READ. Both are required scopes. See Connect Zoho CRM.
1

Open the Fields tab

On Integrations, select Manage on the Zoho CRM card, then Fields. The tab opens on the Leads module.
2

Choose a module

Use Module to switch between Leads, Contacts, and Deals. Kylo loads the field list for that module from Zoho. A module with no readable fields shows “No fields returned for this module.”
3

Read the columns

You now know the API name of every field the agent can touch.

​
Use a field in an instruction

Use the API name when you tell the agent to read or write a field, for example “After the lead gives a company name, use @zoho.leads.update to set Company.” The @zoho.leads.fields tool lets the agent read the live list itself, including custom fields.

​
Fields Kylo reads on its own

When an installed automation fires, Zoho posts these merge fields: id, Mobile, Phone, First_Name, Last_Name, Email, and, for create and field-update rules, Lead_Status. If a value is missing from the post, Kylo fetches the lead from Zoho and uses the fetched record. The tag is never part of the post, because Zoho rejects it as a merge field, so Kylo reads the lead’s tags from the fetched record. See Zoho fields.

Next: create a trigger

Bind an installed automation to a lead phone field.