A trigger names a Zoho event and tells Kylo where to read the lead’s WhatsApp number. You create triggers on Outbound, Triggers. See Create a trigger for the steps.

​
The Triggers page

The list has the columns Name (sortable) and Automation, and an actions menu per row with View and a delete action. An empty list shows No triggers yet and “Add a trigger to automate outbound messages.” A warning appears at the top when Kylo could not provision the Zoho automation, and tells you to reconnect Zoho. View opens View trigger with the automation, the Lead phone field, and the Lead tag when one is set. Deleting a trigger that a campaign uses is refused with This trigger is in use and the name of the campaign to remove it from first.

​
The six triggers

The Automation list offers only automations you have installed. See Zoho automations. “Phone value needed” is enforced in Zoho: the workflow rule fires only when Mobile or Phone is not empty. A lead with no number never reaches Kylo, except through Zoho: Lead created, where Kylo then skips it with phone_missing.

​
The lead phone field

Lead phone field is Mobile or Phone, and it defaults to Mobile. The hint reads “The Zoho field the WhatsApp number is read from.” Kylo reads that field, normalizes the number, and sends to it. See Zoho fields.

​
The tag gate

Zoho: Update lead with tag shows a Lead tag field that lists your Zoho tags for Leads. The hint reads “The trigger sends only to leads that carry this tag in Zoho.” Zoho cannot filter on tags in a webhook rule, so Kylo fetches the lead when the event arrives and compares the tag. A lead without the tag is skipped with tag_mismatch. Use it to aim a campaign at a segment, for example “send the reactivation template to leads tagged Dormant”. Create the tag first: Create Zoho tags.

Campaigns

Bind a trigger to a template.