Skip to main content

Zoho CRM

Zoho is the odd one out among Flowera's channels: nobody is chatting. Instead, something changed in your CRM — a lead was created, a deal moved, a contact was deleted — and you want a flow to do something about it.

Set the organization up first: Zoho CRM credentials. The node reference lives at Zoho trigger and Zoho CRM tool.

What Zoho flows can do​

  • React to record changes — greet a new lead on WhatsApp, alert a team when a deal stalls, enrich a contact the moment it's created.
  • Read records mid-flow — look up a customer's history before answering their question.
  • Write records — create a lead from a chat conversation, update a deal stage, log an activity.

The last two don't need the trigger at all. A web-chat flow can read from and write to Zoho just as happily as a Zoho-triggered one.

Trigger events​

EventFires when
CreateA new record is added to the module
EditAn existing record is updated
DeleteA record is removed

You choose the module the trigger watches — Leads, Contacts, Accounts, Deals, and the rest of the standard set. One trigger watches one module; add more triggers for more modules.

The record that changed arrives in the flow as structured data, so you can branch on any field: route enterprise deals to one path and self-serve signups to another with a Condition node.

Reading and writing records​

Two ways to touch Zoho from inside a flow:

  • Zoho CRM tool — the built-in tool, with named operations for the common record actions. Give it to an Agent and the agent decides when to call it, or put it in a Tool node to run one specific operation every time.
  • HTTP node — for anything the tool doesn't cover, call the Zoho REST API directly using the same connection.

Recipe: act on a new record​

Greet every new lead within seconds of it landing in the CRM:

  1. Start — Zoho trigger, module Leads, event Create.
  2. Condition — does the record have a phone number? No phone, no message.
  3. Agent — write a short, personal opener using the lead's name and source.
  4. Tool (WhatsApp) — Send Template Message to the lead's number.
  5. Tool (Zoho CRM) — log the outreach back onto the record so your sales team can see it.

Full walkthrough: Zoho record-event flow.

Limits and gotchas​

  • Edit events fire on every change, including changes your own flow makes. If a flow writes back to the same module it listens on, add a guard — check a field, or write to a different module — or you'll build a loop.
  • Deleted records carry less data. A delete event tells you what was removed, not everything the record used to contain. Capture what you need before deletion, or store it in flow state earlier.
  • Zoho's connection is per organization. If you work across several Zoho orgs, connect each one and pick the right connection in the trigger.
  • Field names are Zoho's, not yours. A field labelled "Company Size" in the Zoho UI may have a different API name. Check the record payload in an execution trace before writing conditions against it.