Zoho CRM WhatsApp integration: log chats from your numbers

WavesFlo integrates natively with Zoho CRM: sign in to Zoho from Integration → CRM, and once a workspace admin turns syncing on, one-to-one WhatsApp chats and opt-outs from the numbers your team already uses are logged as notes on the matching Zoho contact. Zoho's own WhatsApp channel needs an unused number on Meta's Cloud API instead.

Which route fits depends on where your leads already arrive. Below: what WavesFlo's integration logs and leaves out, what Zoho's own channel needs, when an n8n workflow fits better (new senders as leads, your own fields, or Bigin), how to avoid duplicates, and what belongs in each tool.

Does WavesFlo integrate natively with Zoho CRM?

Yes, as of October 2026. Connect Zoho CRM from Integration → CRM in the WavesFlo dashboard by signing in to Zoho; Zoho's regional data centres, India's included, are supported. Nothing reaches Zoho until a workspace admin turns syncing on: every sync switch starts off on a new connection.

• Each switch is separate: incoming direct messages, outgoing direct messages, and opt-outs and opt-ins. Each is logged as a note on the matching Zoho contact.
• Matching is by phone number: a link WavesFlo remembers first, then Zoho's own phone search, then, only if the connection is allowed to, a new Zoho contact.
• Only one-to-one chats are logged. Group, status and channel messages never reach Zoho; media isn't copied (the note says a photo or document was sent), and very long messages are cut at about 4,000 characters.
• Zoho contacts with a usable international phone number can be imported into WavesFlo's audience, on demand or automatically every six hours; re-imports don't duplicate or overwrite what WavesFlo already knows.
• An import never records consent: being in Zoho isn't agreeing to WhatsApp messages, so imported people arrive with unknown consent and WavesFlo's sending rules treat them that way.
• Disconnecting revokes WavesFlo's access in Zoho.

The integration works with Zoho contacts, not leads, and WavesFlo is still not a CRM: no pipeline, deal stages or lead scoring. If you want each new sender created as a Zoho lead, or you use Bigin, use the n8n workflow below.

Does Zoho CRM have a WhatsApp integration?

Yes. Zoho calls it business messaging. An administrator sets it up under Setup → Channels → Business Messaging, signs in with Facebook Business Manager and verifies the number. Zoho's help page, last updated in September 2026, sets out what it needs and how it behaves:

• Prerequisites: a Facebook Business Manager account, a verified business, a WhatsApp Business account and a number registered on Meta's Cloud API.
• The number must be unused. Numbers in use on other products can't be connected, and Zoho says migrating an existing number isn't supported yet.
• New senders can be added as leads or contacts automatically and assigned to users, groups or roles.
• Replies must go within 24 hours of the customer's message. To start a conversation, the business sends a message Meta has approved in advance, from a record or from a workflow rule.
• Messages the business sends are charged against credits bought inside Zoho CRM, with an optional automatic top-up.

Conversations land in a Messages module, attached to the lead or contact, and reps reply from there or straight from the new-message notification.

Which route suits a team already selling on WhatsApp Business numbers?

Zoho's channel is the simpler choice if you are starting with a fresh number and want reps to work inside Zoho. If enquiries already arrive on numbers your team has used for years, a new number means telling every customer and reprinting everything that carries the old one; linking the existing numbers to WavesFlo and switching on its Zoho CRM integration avoids that. For flows the integration doesn't cover, such as creating leads, Microsoft-based teams should note that Power Automate's catalogue has Zoho connectors for Calendar, Forms, Mail, Sign, TeamInbox and ZeptoMail, plus an independent publisher's Zoho Invoice connector, but none for Zoho CRM as of October 2026, so n8n is the shorter route.

How do you send WhatsApp leads to Zoho CRM with n8n?

WavesFlo's integration logs chats on Zoho contacts. To create each new sender as a lead, with Lead Source and your own fields, build this workflow on WavesFlo's signed webhook events instead:

1. 1In n8n, create a Zoho credential (OAuth2) and choose the data centre your account lives in, such as IN for Zoho's India data centre.
2. 2Start the workflow with a Webhook node whose URL WavesFlo sends message events to, and verify each delivery's signature. Add an If node that passes message.received from direct chats only, then a Remove Duplicates node keyed on the event ID, because a delivery can arrive twice.
3. 3In an Edit Fields (Set) node, put the sender's number in one format, such as +919876543210, and keep the profile name, the message and the id of the number it arrived on.
4. 4Look the person up with an HTTP Request node, choosing Predefined Credential Type and your Zoho credential, and call Zoho's search API on Leads with the phone parameter, which checks every phone field in the module. Repeat on Contacts if your team converts leads.
5. 5If nothing matches, add the Zoho CRM node with Lead and Create. The node requires Company and Last Name, which a WhatsApp lead rarely gives, so use the profile name and a placeholder such as Not given. Put the number in Mobile, WhatsApp in Lead Source (add it to the picklist first) and the first message in Description.
6. 6Add each message to the lead as a note with a second HTTP Request node calling Zoho's Notes API. The Zoho CRM node has no notes operation as of October 2026.
7. 7Test from your own phone, then publish the workflow.

The webhooks guide has the signature recipe, and the event reference is on the developers page.

How do you avoid duplicate leads in Zoho?

• WavesFlo's integration matches by phone number, first a link it remembers and then Zoho's phone search, and creates a contact only if the connection is allowed to.
• In an n8n workflow, deduplicate deliveries on the event ID before anything else runs.
• Store numbers in one format, and tidy existing records once. A number typed by hand as 098765 43210 may not match an event carrying +919876543210.
• Search before you create, as in step 4, and add a note rather than a new lead when a record exists.
• Or let Zoho match for you. Its upsert checks Email first, then any field marked unique, and the Zoho CRM node's Create or Update leaves that order to Zoho, so marking Mobile as unique (Do not allow duplicate values) makes the upsert match on the number. Unique fields need a paid edition, and Leads can have two besides Email. The catch: the node sends Company and Last Name on every call, so a match overwrites them with the workflow's placeholders. Searching first avoids that.
• Turn on the duplicate check for converted leads, so a customer who became a contact isn't created again as a lead.

Can you do the same in Bigin?

Partly. Bigin, Zoho's CRM for small businesses, has its own WhatsApp integration in the Express, Premier and Bigin 360 editions, according to its help page. Like Zoho CRM's, it needs a Facebook Business Manager account and a number on Meta's Cloud API, and each new sender becomes a contact, shared out among users in turn. n8n's documentation lists a Zoho CRM node but no Bigin node as of October 2026, so the n8n route to Bigin means HTTP Request calls to Bigin's own API, with more setting up.

What stays in WhatsApp and what moves to Zoho?

Zoho keeps the record: the lead or contact, its owner, stage, value and follow-up tasks, and the reports built on them. WavesFlo keeps the conversation: every number's chats in one shared inbox, where people assign chats, add internal notes and set labels. Once a workspace admin turns syncing on, WavesFlo's Zoho CRM integration adds each one-to-one chat, and each opt-out or opt-in, as a note on the matching Zoho contact; group, status and channel messages never reach Zoho. WavesFlo isn't a CRM: it has no pipeline, deal stages or lead scoring. Labels set in the inbox stay in WavesFlo, so keep stages in Zoho. More on that in WhatsApp Business labels.

For the routine around it, from first reply to handover, see WhatsApp for B2B sales teams. The same events can also log leads in a Google Sheet, and WavesFlo connects to HubSpot natively in the same way as Zoho CRM.