Salesforce WhatsApp integration: options, cost and setup

Salesforce connects to WhatsApp in two broad ways. Its own enhanced WhatsApp channel runs in Agentforce Service, formerly Service Cloud, and needs Enterprise edition or higher with the Digital Engagement or Agentforce Contact Center Digital add-on. Alternatively, an automation tool such as n8n or Power Automate writes each WhatsApp chat into Salesforce as a lead, contact or task.

Salesforce's channel is a service console for one-to-one chats on a number that lives inside Salesforce. The automation route suits sales teams whose reps keep their WhatsApp numbers on their phones, groups included, and only need Salesforce to hold the record.

Does Salesforce have its own WhatsApp integration?

Yes. As of October 2026, Salesforce's editions article lists the enhanced WhatsApp channel for Enterprise edition or higher, for Service or Sales, with either the Digital Engagement or the Agentforce Contact Center Digital add-on. Starting a conversation from your side needs more: the WhatsApp Outbound Messages add-on, or WhatsApp message credits, which Salesforce has required on Agentforce Contact Center Digital since 27 March 2026. On that add-on, Salesforce says the credits must be bought before a WhatsApp channel can be created at all.

Set-up runs through Meta. An admin creates the channel in Messaging Settings, signs in with Facebook, picks or creates a Meta business account and a WhatsApp Business Account, verifies the number by text or call, and activates the channel within 14 days. Each channel is one number, and you can create one per rep. Reps answer from the Service Console and can pass a chat to another rep, a queue or an Omni-Channel flow. Salesforce's own documentation lists four limits worth knowing first:

• The number leaves the WhatsApp app. Salesforce warns not to log into the WhatsApp mobile or desktop app with the number after creating the channel, or it can't be activated.
• Group chats aren't supported. If a customer adds someone to the conversation, that person's messages aren't delivered.
• Locations, contact cards and polls don't come through, and nor does deleting a message.
• Replies run on a clock. A customer's message opens a 24-hour customer care window; after it closes, reps can only send messages Meta has approved in advance, and notifications need consent collected outside WhatsApp.

That suits a support team answering one to one inside Salesforce. A sales team whose leads arrive on reps' own numbers or in groups would have to move every number off its phone.

Salesforce and WhatsApp: the routes compared

Both automation routes depend on Salesforce's API. Salesforce includes API access by default from Enterprise edition up and on Developer edition; Professional edition must buy it as the Web Services API add-on, and Group and Essentials editions can't have it. Microsoft adds that Salesforce trial accounts can't connect, because they have no API access.

How do I create a Salesforce lead from a WhatsApp chat in n8n?

n8n's Salesforce node creates, updates and upserts leads and contacts, adds notes, creates tasks and cases, and runs SOQL searches. It signs in with JWT or OAuth2, and n8n recommends an External Client App, since Salesforce is phasing out Connected Apps. On the WhatsApp side this uses WavesFlo, whose numbers are linked by QR code from Linked devices, so each phone keeps working.

1. 1Start with a Webhook node that receives WavesFlo's message.received event and verifies its signature, as the webhooks guide shows. The event fires for each incoming message that reaches WavesFlo and carries the sender, the text, the chat type and the connected number it arrived on.
2. 2Add a Remove Duplicates node keyed on the event ID. Delivery is at least once, and events don't always arrive in order.
3. 3Add a Filter node that keeps direct chats only. Groups need a different home, covered below.
4. 4Normalise the sender's number to the format your org stores, such as +919876543210, then run the Salesforce node's Search operation for a contact, or an unconverted lead, with that mobile number.
5. 5If nothing matches, create a lead. Fill required fields WhatsApp can't supply, such as company, with a placeholder like 'WhatsApp enquiry', and set Lead Source from the connected number: your IndiaMART listing's number and the number on a Pune site hoarding are different sources.
6. 6Log the message as a task or note on the lead or contact, so whoever opens the record sees what the customer asked.
7. 7Optionally, run a second workflow on message.sent, which also fires for messages typed on the phone, so Salesforce holds both sides.

SELECT Id, AccountId, OwnerId FROM Contact
WHERE MobilePhone = '+919876543210' LIMIT 1

SELECT Id, OwnerId FROM Lead
WHERE MobilePhone = '+919876543210' AND IsConverted = false LIMIT 1

Can Power Automate send WhatsApp chats to Salesforce?

Yes. Power Automate's Salesforce connector gets, creates, updates and upserts records, runs SOQL, and triggers when a record is created or modified. It is a Premium connector, so the free plan won't run it; the Power Automate WhatsApp connector guide explains which licences do.

1. 1Start a cloud flow with When an HTTP request is received, and add its URL as a WavesFlo webhook destination for message events.
2. 2Verify each delivery's signature first. Power Automate's expressions have no HMAC function, so run the check in a small Azure Function using the code in the webhooks guide.
3. 3Use Get records on Lead with a filter query on the mobile number. If a lead exists, use Create record to add a Task to it; if not, create the Lead, then the Task.
4. 4If the WhatsApp number sits in an External ID field, use Insert or Update (Upsert) a Record by External ID (V2) instead.

Microsoft's known issues for the connector include two Salesforce settings: the connecting user needs the API Enabled permission, and Lock sessions to the IP address from which they originated must be off.

What about WhatsApp groups?

Salesforce's channel doesn't handle groups, yet a lot of Indian selling happens in them: a distributor group per city, a channel-partner group per project, a buyers' group after a site visit. With the webhook route, message.received fires for group messages too, and you decide what Salesforce does with them:

• Log against the account. Keep a lookup of group to Salesforce account and log each group message as a task on that account, with the sender's name in the subject. Never create a lead per group member: one busy group would flood the lead list.
• Watch for buying signals. Filter group messages for words such as quote, rate or price list, and create a task for the account owner, so a request in a 200-member group isn't lost in the scroll.

What WavesFlo does here, and what it doesn't

WavesFlo is the WhatsApp side of this set-up, not a CRM, and has no native Salesforce app: n8n or Power Automate does the Salesforce step. What it adds is the inbox reps work from. Direct chats and groups from every linked number land in one shared inbox, each marked with the number it arrived on, and the reply goes out on that number. A person hands a conversation to a teammate or leaves it in the shared queue, and on Growth and Enterprise round-robin can give new chats to each person in a team in turn.

• It doesn't read Salesforce. Owners, stages and lead status stay there; in the inbox, your team uses its own labels and internal notes.
• Threads start when a number is linked, so older history isn't imported, and inbox search covers name, number and latest message only.
• A chat where someone has turned on WhatsApp's Restricted chat stays on the phone: nobody in that chat can use linked devices for it, so it never reaches the inbox, the webhooks or Salesforce.
• Every inbox reply passes the opt-out register, which fails closed, the emergency pause and the number's daily ceiling. Through n8n or Power Automate, a consent.withdrawn event can also tick a custom opt-out field in Salesforce.
• The inbox is on Growth and above: as of October 2026, ₹2,999 per session per month with one team member and one number included, ₹499 per extra team member and ₹999 per extra number per month. See pricing.

Which route should you choose?

• Salesforce's channel, if reps already work in the Service Console, conversations are one to one, and you're content to move each number off the WhatsApp app.
• The webhook route, if reps keep numbers on their phones, leads arrive in groups as well as chats, or you run many numbers and only need Salesforce to hold the record.

Getting the record into Salesforce is half the job; answering fast and following up is the rest. See WhatsApp lead management and the WhatsApp for sales teams guide.