Zoho WhatsApp Integration: CRM, API & Automation Without Zapier

Zoho WhatsApp integration closes the gap between your CRM and the inbox your customers actually read. There is no separate “Zoho WhatsApp API” from Zoho that sends official Cloud API messages on its own — you connect Zoho CRM (or Bigin) to Meta’s WhatsApp Cloud API through a BSP. Ominiflow is that layer: OAuth sync, workflow webhooks, and template send, without CSV exports and without Zapier for core lead flow.

This guide covers native OAuth integration, webhook workflows, field mapping, popular automation patterns, troubleshooting, and how Zoho + WhatsApp compares to Zapier chains.

Too long? Read this first

• Sync Zoho CRM or Zoho Bigin leads and contacts into Ominiflow automatically
• Setup uses OAuth (Client ID + Secret) plus optional Zoho workflow webhooks
• Contacts must have valid phone numbers in E.164 format for WhatsApp messaging
• Business-initiated messages need Meta-approved templates unless inside 24-hour window
• Native connector beats Zapier for core lead sync — see Zoho WhatsApp without Zapier
• Zoho Marketing Automation and Zoho workflow rules can fire the same WhatsApp templates via webhook
• Cloud API only since on-premise deprecated October 2025

What “Zoho WhatsApp API” actually means

Zoho does not sell a replacement for Meta’s official WhatsApp API. Searches for Zoho WhatsApp API mean one of these setups:

Zoho CRM WhatsApp integration on Ominiflow uses Zoho’s REST API (Client ID + Secret) plus Meta Cloud API. Zoho stays source of truth for leads; WhatsApp stays the conversation layer.

Why integrate Zoho with WhatsApp?

• Instant lead engagement — welcome message or qualification bot fires when a lead is created
• Fewer manual errors — no copy-paste between CRM and messaging tools
• Faster sales cycles — reps see WhatsApp replies inside Ominiflow while Zoho stays source of truth
• Campaign triggers — stage changes in Zoho kick off template sequences (with opt-in)
• Unified reporting — tie CRM pipeline stages to WhatsApp conversation outcomes

Integration architecture

1. Zoho event — lead created, deal stage changed, contact updated
2. Sync layer — native OAuth connector or Zoho workflow webhook
3. Ominiflow — validates template, formats phone, sends message, stores conversation
4. Meta Cloud API — delivers message to customer device
5. Customer reply — Ominiflow inbox → optional write-back to Zoho timeline

Full architecture: WhatsApp API integration guide

Before you start

• Active Ominiflow account with WhatsApp Business API connected
• Zoho CRM or Zoho Bigin with admin permissions
• Access to Zoho API Console (use .com / .eu if your org is not on zoho.in)
• Phone numbers stored in E.164-friendly format (+919876543210 or 919876543210)
• Approved WhatsApp templates for outbound triggers in Ominiflow

How to integrate Zoho with Ominiflow

Step 1: Install Zoho from the Ominiflow dashboard

1. Log in to your Ominiflow dashboard
2. Go to Integrations or Discover Apps
3. Search for Zoho and click Install

After install you will see:

• Redirect URL — paste this into Zoho (required)
• Webhook URL — for workflow-based lead push (optional)
• Fields for Client ID and Client Secret

Step 2: Create a client in Zoho API Console

1. Visit the Zoho API Console and sign in
2. Click Add Client → Server-Based Application
3. Client Name: Ominiflow WhatsApp Integration
4. Homepage URL: your business website (e.g. https://ominiflow.com)
5. Paste Ominiflow Redirect URL into Zoho's redirect field
6. Click Create

Step 3: Copy credentials and connect OAuth

1. Copy Client ID and Client Secret from Zoho
2. Paste into Ominiflow → Zoho integration settings → Save
3. Click Connect and approve permissions on Zoho consent screen

Step 4: Webhook setup (recommended for real-time leads)

1. Copy Webhook URL from Ominiflow
2. In Zoho: Settings → Automation → Workflow Rules
3. Create rule for Leads or Contacts on create/update
4. Add Webhook action with Ominiflow URL
5. Map fields: name, phone, email, lead source, owner, deal stage
6. Save and activate

Step 5: Map fields to template variables

Popular Zoho + WhatsApp workflows

• New lead → welcome template — qualify budget and timeline via chatbot
• Demo booked → reminder — utility template 24h before call
• Deal stage = Proposal sent → follow-up nudge — marketing template with opt-in only
• Support ticket in Zoho Desk — notify customer on WhatsApp with case ID
• Payment received — receipt template from Zoho Books via webhook (or Razorpay + WhatsApp)

Zoho automation → WhatsApp (workflow rules, no Zapier)

Zoho automation for WhatsApp is a workflow rule, not a Zap. In Zoho CRM: Setup → Automation → Workflow Rules. Trigger on lead create, field update, or deal stage. Action = webhook to Ominiflow with phone, name, and stage. Ominiflow sends the approved template. Same pattern works in Zoho Bigin.

• Keep marketing-category templates behind an opt-in field on the Zoho lead
• Use utility templates for demo reminders, payment due, and onboarding
• Idempotency: include Zoho record ID so retries do not double-send

Zoho Marketing Automation + WhatsApp

Zoho Marketing Automation is Zoho’s campaign product (email journeys, scoring, WhatsApp as a channel in Zoho’s own stack). If you already run journeys there and want official Cloud API delivery, quality rating, and a shared inbox, treat WhatsApp as an action at the end of the journey — not a second ESP.

1. In Zoho Marketing Automation, add a webhook (or CRM-sync) at the journey step where you would have sent email
2. Post name, phone, campaign ID, and consent timestamp to Ominiflow
3. Ominiflow sends a Marketing template only when the Zoho consent field is true
4. Replies land in the Ominiflow inbox and write back to Zoho CRM activity — so sales sees the thread, not just a campaign stat

This is how you get Zoho Marketing Automation talking to WhatsApp without Zapier: one webhook, one template, one inbox. Do not run Zoho’s WhatsApp channel and Ominiflow on the same number at the same time.

Zoho native integration vs Make / Zapier

Guide: Make + WhatsApp

Troubleshooting

Important notes

• Phone number required — WhatsApp cannot message contacts without valid mobile
• Opt-in for marketing — transactional utility differs from promotional broadcasts
• Historical sync — native connectors typically sync forward from connect date
• Data region — use correct Zoho API domain (.in, .com, .eu)

Get Zoho + WhatsApp running on Ominiflow

Book Integration Setup →

Related: automation platform · WhatsApp API India · free API workshop

FAQ