How do I integrate Salesforce with WhatsApp?
Connect Salesforce Leads, Contacts, and Opportunities to WhatsApp via Ominiflow. Webhook architecture, field mapping, stage triggers, and bi-directional conversation logging. Connect WhatsApp API on Ominiflow, then use Salesforce Flow HTTP callouts, Make middleware, or Apex REST API to trigger templates on Lead/Opportunity events and log inbound replies as Activities.
Last updated: 6 July 2026
Your Salesforce org holds leads, opportunities, and case history. Your customers respond on WhatsApp. Without integration, reps toggle tabs, copy phone numbers, and lose conversation context on handoffs. Connecting Salesforce to WhatsApp Business API through Ominiflow puts messaging inside your revenue workflow — stage changes trigger templates, inbound replies log to the right record, and managers see full audit trails.
This guide covers architecture options (webhooks, Make, Salesforce Flow + API), field mapping for Leads and Opportunities, template compliance, and enterprise rollout patterns on Meta Cloud API.
Too long? Start here
- Outbound: Salesforce event (new Lead, Opportunity stage change) → Ominiflow → approved WhatsApp template
- Inbound: Customer WhatsApp reply → Ominiflow → Salesforce Task/Activity or custom object log
- Phone field: MobilePhone or Phone in E.164 format (+919876543210 stored, 919876543210 in API)
- Business-initiated messages require approved templates outside the 24-hour customer care window
- Three patterns: Ominiflow webhooks + Salesforce Flow, Make middleware, custom Apex + REST API
- On-premise WhatsApp API is deprecated (Oct 2025) — all paths use Cloud API
Why integrate Salesforce with WhatsApp?
- Speed-to-lead — web form Lead created → WhatsApp welcome in under 60 seconds
- Pipeline automation — "Proposal Sent" stage triggers follow-up template sequence
- Case deflection — routine support queries answered on WhatsApp, logged as Cases
- Manager visibility — conversation history on Lead/Contact/Account record
- Global teams — WhatsApp preferred over email in India, UAE, LATAM, and Southeast Asia
- Click-to-WhatsApp attribution — ad leads tagged with campaign source in Salesforce
Integration architecture
- Salesforce trigger — Flow, Process Builder, or Apex on Lead/Opportunity/Case events
- Middleware — HTTP callout to Ominiflow webhook or Make scenario
- Ominiflow — template validation, phone formatting, agent routing, conversation store
- Meta Cloud API — message delivery to customer device
- Inbound webhook — reply → Ominiflow → Salesforce API creates Task or updates custom fields
Full patterns: WhatsApp API integration guide
Setup: Salesforce + Ominiflow
Step 1: WhatsApp API on Ominiflow
- Connect WhatsApp Business number via Ominiflow (Cloud API)
- Complete Meta Business Manager verification
- Create templates: lead welcome, proposal follow-up, case update, meeting reminder
- Copy API credentials and inbound webhook URL from Ominiflow dashboard
Step 2: Salesforce field mapping
| Salesforce field | Ominiflow / template | Notes |
|---|---|---|
| Lead.MobilePhone | to | Strip + for API; validate on Lead insert |
| Lead.FirstName | Template {{1}} | Fallback to Company if blank |
| Opportunity.Name | Template {{2}} | Deal context in message |
| Lead.Id / Opportunity.Id | Custom field | Match inbound replies to record |
| Owner.Name | Template {{3}} | Rep introduction messages |
Step 3: Salesforce Flow (no-code outbound)
- Create Record-Triggered Flow on Lead: after insert
- Decision: MobilePhone is not null AND LeadSource ≠ excluded sources
- Action: HTTP Callout to Ominiflow webhook URL
- Body JSON: phone, template_name, language, components with Lead fields
- Store External Credential for Ominiflow API key in Named Credential
- Activate flow; test with sandbox Lead
Step 4: Inbound reply logging
- Configure Ominiflow inbound webhook handler
- On message received: lookup Salesforce Lead/Contact by phone
- Create Task: Subject = "WhatsApp: [first 50 chars]", Description = full message
- Update custom field
Last_WhatsApp_Activity__cwith timestamp - Route to agent in Ominiflow inbox with Salesforce record link
Step 5: Opportunity stage triggers
Record-Triggered Flow on Opportunity: when StageName changes to "Proposal Sent":
- Wait 0 minutes → send proposal_ack utility template
- Subflow or Ominiflow sequence: day 2 follow-up, day 5 final nudge
- Cancel sequence if Opportunity moves to Closed Won/Lost or customer replies
Integration patterns compared
| Pattern | Pros | Cons | Best for |
|---|---|---|---|
| Salesforce Flow + Ominiflow webhook | Native SF automation, auditable | HTTP callout limits; governor awareness | Mid-market with SF admin |
| Make / Zapier middleware | Fast setup, visual debugging | Per-task cost at scale; latency | POC and sub-5K msgs/month |
| Apex + Ominiflow REST API | Full control, bulk handling | Developer required; maintenance | Enterprise, high volume |
| Salesforce Messaging (native) | Inside SF UI | Separate licensing; WhatsApp via partners | Teams already on SF Digital Engagement |
Enterprise use cases
- B2B SaaS — trial signup Lead → onboarding WhatsApp sequence → AE alerted on reply
- Financial services — KYC reminder on Opportunity; authentication template for OTP
- Real estate — site visit booking from Lead; confirmation utility template
- Healthcare — appointment Case → reminder template (non-diagnostic)
- Support — Case status change → customer notification on WhatsApp
Compliance and governance
- Opt-in for marketing — store consent timestamp on Lead/Contact custom field
- Data residency — align with org's GDPR/DPDP policies for message content logging
- Field-level security — restrict WhatsApp send permissions via Salesforce profiles
- Audit trail — Tasks or custom Message objects for every outbound/inbound
- Template category accuracy — utility for transactional; marketing only with opt-in
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| Flow runs but no message | Named Credential auth failure | Verify API key; check Ominiflow webhook logs |
| Wrong Lead matched on reply | Duplicate phone numbers | Dedup rule; match on most recent open Lead |
| Template #132000 error | Variable count mismatch | Align {{1}}/{{2}} with approved template |
| Governor limit exceeded | Bulk Lead import triggers Flow per row | Batch via Apex or pause Flow for bulk loads |
| Messages not logged to SF | Inbound webhook not configured | Set Ominiflow → Salesforce write-back in integration settings |
Salesforce + WhatsApp on Ominiflow
Ominiflow provides webhooks, REST API, shared inbox, and template management for Salesforce integrations. Enterprise onboarding includes field mapping workshops and sandbox testing.
Book Enterprise Integration Call →
Related: API integration guide · Zoho integration · pricing
FAQ
Does Ominiflow have a native Salesforce connector? expand_more
Salesforce integration runs via webhooks, REST API, and Make/Zapier middleware. Salesforce Flow HTTP callouts to Ominiflow are the most common enterprise pattern. Custom Apex integrations available for high-volume accounts.
Do I need Zapier to connect Salesforce with WhatsApp? expand_more
No. Salesforce Flow with HTTP callout to Ominiflow works without middleware. Make/Zapier suits teams without Salesforce admin resources.
How long does Salesforce WhatsApp integration take? expand_more
POC via Make: 3–5 days. Production Flow + inbound logging: 2–4 weeks including sandbox testing and template approval.
Can WhatsApp conversations log to Salesforce Activities? expand_more
Yes. Inbound and outbound messages create Tasks or custom Activity records matched by phone number to Lead, Contact, or Account.
Does this work with Salesforce Sales Cloud and Service Cloud? expand_more
Yes. Lead/Opportunity triggers suit Sales Cloud. Case status notifications suit Service Cloud. Same Ominiflow WhatsApp number can serve both.
What about Salesforce Digital Engagement? expand_more
Salesforce's native messaging is a separate product path. Ominiflow suits teams wanting dedicated WhatsApp BSP features — chatbot builder, broadcasts, Meta fee transparency — integrated via API.
Is WhatsApp Cloud API required? expand_more
Yes. On-premise API was deprecated October 2025. Ominiflow uses Meta Cloud API exclusively. Updated July 2026. Salesforce + WhatsApp integration guide for revenue and support teams.
