Connect Salesforce to WhatsApp
No two Salesforce orgs are shaped alike, which is why a one-size connector usually fits nobody. This one is built on the public REST API and webhooks, so it matches your objects rather than ours.
How this connects
Built against our public REST API and webhooks. This one needs a developer.
Salesforce and Watx, together.
- Create or update Watx contacts from Leads and Contacts
- Trigger WhatsApp templates on stage changes or workflow rules
- Post WhatsApp conversation and message events back as activities
- Scope API keys so the integration only reaches what it needs
Four automations that earn their keep.
-
When
New qualified lead
Then
Send the first-touch template and open a conversation in the shared inbox.
-
When
Opportunity moves stage
Then
Fire the template that stage always needs, with the owner’s name in it.
-
When
WhatsApp reply received
Then
Post it as an activity against the record so the rep sees it in Salesforce.
-
When
Contact opts out
Then
Write it back so no campaign re-adds them.
How to connect it.
This one needs a developer, and we would rather say so than find out together.
- 1 Generate a scoped API key in Watx Settings.
- 2 Call the Watx REST API from Apex, Flow or your middleware.
- 3 Subscribe a webhook for conversation and message events.
- 4 Map your objects to Watx contacts and test in a sandbox first.
Salesforce, answered.
Does this need a developer?
Yes, and we would rather say so. A real Salesforce org is rarely a simple case.
Is the API on every plan?
Yes. Scoped keys and webhooks are part of the product, not gated behind the top tier.
Often set up alongside
Not sure it will fit?
Tell us what Salesforce has to talk to and we will say plainly whether it works today, needs a developer, or does not exist yet.