Skip to main content

Zoho CRM

Connecting Zoho authorises Flowera to read and write records in one Zoho organization, and to receive notifications when records change.

Before you start​

You need:

  • A Zoho CRM account with API access on your plan.
  • Administrator rights in the Zoho organization you're connecting. Flowera detects your data centre (.com, .eu, .in, and so on) from the account you sign in with — there's nothing to pick. Once connected, the region is shown as a badge on the credential.

Once connected, the account appears in the Zoho trigger dropdown.

Connecting a Zoho organization​

  1. Open Credentials and switch to the Connected Accounts tab.
  2. Press Add Platform and choose Zoho CRM.
  3. Sign in to Zoho and approve the access request.
  4. The organization appears under CRM, ready to use in triggers and the Zoho CRM tool.

Connect each organization separately if you work across several.

Permissions Flowera requests​

Flowera requests full access to each module it works with — Leads, Contacts, Deals, Accounts, Notes, Tasks, Events, Calls, Cases, Products, Vendors and Quotes. In Zoho's terms that is read, create, update and delete on those modules.

PermissionWhy
Read recordsLook up leads, contacts, deals, and the other modules mid-flow
Create and update recordsWrite back what a conversation produced
Delete recordsAvailable to the Zoho CRM tool as an explicit, opt-in action
Read module metadataPopulate the module and field dropdowns in the trigger and tool
NotificationsReceive create / edit / delete events
Deletion is real, and two kinds of it are not equal

The Zoho CRM tool ships Delete Record and Delete Attachment operations, and the OAuth grant covers them. They aren't enabled by default — you choose the operations a tool node may perform — but a flow you configure that way can delete from your production CRM.

  • Delete Record moves the record to Zoho's Recycle Bin, recoverable for 60 days. One record at a time, by design.
  • Delete Attachment is immediate and irreversible — Zoho does not put attachments in the Recycle Bin.

Only enable a delete operation on a flow you've tested, and prefer an update where one would do.

Managing connections​

Connected organizations appear under CRM on the Connected Accounts tab, with their status and the option to disconnect.

Disconnecting revokes the authorisation. Every flow that used the connection stops working against Zoho — triggers stop firing and tool calls fail — until you connect again.

Zoho's authorisation refreshes itself in normal use. If it's revoked from the Zoho side, or the admin account that granted it is deactivated, you'll need to reconnect.

Troubleshooting​

SymptomLikely cause
Sign-in succeeds but no organization appearsYou signed in with a Zoho account on a different data centre than the organization you meant — sign out of Zoho and sign in with the right account
Trigger never firesThe module or event isn't the one you're changing; check both on the Start node
Fields are missing from the payloadZoho sends the record's API field names, which differ from UI labels — read a real payload in an execution
"Insufficient privileges"The Zoho user who authorised doesn't have rights on that module
Records update, then update againA flow is writing to the module it listens on — add a guard