Zoho CRM Trigger
The Zoho CRM trigger starts your flow when a record changes in Zoho — a lead is created, a deal is edited, a contact is deleted. When you save a flow with this trigger, Flowera automatically subscribes to Zoho's watch API for the module and events you chose, so no manual webhook setup is needed on Zoho's side.
This page covers setting up the trigger inside a flow. Connecting your Zoho organization happens once in the Channels section.
Your Zoho CRM organization must already be connected to Flowera (via Zoho OAuth) before it appears in the connection dropdown here. Connect one from Integrations → Zoho CRM. See the Credentials section for account connection.
Adding it to a flow
On the Start node, open Webhooks, add a webhook, and set Webhook Type to Zoho CRM.
Inputs
| Parameter | Description | Required |
|---|---|---|
| Webhook Name | A unique name for this webhook (e.g. zoho-leads). Used in variables like {{$webhook.zoho-leads.module}}. | Yes |
| Zoho Connection | The connected Zoho CRM organization to watch. | Yes |
| Zoho Module | The CRM module to watch (see the list below). | Yes |
| Zoho Events | Which record events fire the flow — create, edit, and/or delete. At least one required. | Yes |
Module
Under Zoho Module you pick which CRM module to watch. The standard modules are:
Leads, Contacts, Deals, Accounts, Tasks, Events, Calls, Cases, Solutions, Products, Vendors, Campaigns, Price_Books, Quotes, Invoices
Any custom modules in your Zoho org are discovered automatically and also appear in the dropdown.
Each (connection × module) pair creates one watch subscription on Zoho. Flowera renews these subscriptions automatically before they expire.
Events
Under Zoho Events you choose which record lifecycle events trigger the flow. You can select more than one:
| Event | Fires when… |
|---|---|
| Record Created | A new record is added to the module. |
| Record Edited | An existing record is updated. On edit, the changed field names are available in {{$webhook.<name>.affectedFields}}. |
| Record Deleted | A record is deleted. Only the record IDs are available — the record body is already gone. |
The event that fired is available as {{$webhook.<name>.operation}} (create, edit, or delete).
For create and edit events, Flowera auto-fetches the full record into {{$webhook.<name>.record}} — but only when the notification carries 10 or fewer IDs. For bulk events (more than 10 records) and for delete events, the record body is not fetched; use the {{$webhook.<name>.ids}} array to drive your own read (via a Zoho Tool) instead.
Reading the event in your flow
Zoho triggers expose these variables automatically (no payload mapping needed):
| Variable | Description |
|---|---|
{{$webhook.<name>.module}} | The module's API name (e.g. Leads, Deals). |
{{$webhook.<name>.operation}} | The event: create, edit, or delete. |
{{$webhook.<name>.ids}} | Array of affected record IDs (always an array). |
{{$webhook.<name>.serverTime}} | Zoho's server time when the event fired. |
{{$webhook.<name>.affectedFields}} | Changed field names (edit events only). |
{{$webhook.<name>.record}} | The auto-fetched record body (create/edit, ≤10 IDs). |
See Variables for the full reference.
Example
React to new leads: webhook named zoho-leads, connection = your Zoho org, module Leads, event Record Created. When a lead is created in Zoho, the flow runs with the new lead in {{$webhook.zoho-leads.record}}, and an Agent (with the Zoho CRM tool for read/update) enriches or routes it.
Tips
- Watch the specific events you need — subscribing to all three (create/edit/delete) when you only care about new records will fire the flow more than necessary.
- For bulk and delete events, loop over
{{$webhook.<name>.ids}}with a Zoho Tool to read records yourself. - To act back on Zoho (update a field, add a note), pair this trigger with the Zoho CRM tool inside an Agent node.