Integrations

One number, wired into the rest of your software.

Four routes reach it: a no-code app on Zapier, Make and n8n, webhooks, the REST API, and an MCP server for AI assistants. All four come with the plan.

Start free trial

7 days free · No credit card · Cancel anytime

Routes

Four routes in, and nothing stops you running all four

None of them is a separate product. A single API key opens every one, they read and write the inbox your agents already work in, and a workflow somebody assembled over lunch sits happily beside code a developer ships next quarter.

Connector platforms

Zapier, Make, n8n and Integrately can all drive this number. You choose the event on one side, the message on the other, and switch it on. There is no editor to open and nothing to deploy.

Webhooks

Give us an HTTPS endpoint and every arrival reaches it as JSON while it is still happening: a message in, an acknowledgement back, a reaction, a reassignment, a contact edit.

REST API

Send, schedule, label, assign, search and export from your own backend, in whatever language it is written in. JSON both directions, and a tester in the docs that fires against your own account.

MCP server

One URL turns an AI assistant into an operator on the number: it can read a thread, draft the answer and queue the campaign, and it asks you before it writes anything.

IncludedAPI, webhooks and MCP in the plan

Two-waySend from your stack, receive every event

Same numberNothing to migrate or re-verify

The apps people ask about, and the job each one ends up doing

Names rather than categories, so you can find your own stack without reading the whole page. The tag on each row says which of the four routes reaches it, and not one of those routes needs anything bespoke built on our side. And if your app is not among them, that answer is here too, rather than left to you to work out.

No-codeThrough Zapier, Make, n8n or Integrately
WebhookThe app or WaliChat posts JSON at an endpoint
APIYour own code calls the REST API
MCPAn AI assistant working through the MCP server

Stores & checkout

ShopifyNo-code
A dispatch or a refund on the shop becomes a message on the buyer's thread, courier link included.
WooCommerceNo-codeWebhook
The same for a WordPress shop. If you would rather skip the middle layer, Woo can post its own webhook straight at your handler.
StripeNo-codeWebhook
Payment cleared, renewal due, card declined: each state earns its own message instead of a second email.

CRM & pipeline

HubSpotNo-code
A form fill can open the conversation, and whatever the customer answers goes back onto the record.
SalesforceNo-codeAPI
Stage changes and case updates reach the customer without a rep retyping them into another window.
PipedriveNo-code
When a deal moves, the owner gets nudged and the buyer gets the follow-up, in the same run.
Zoho CRMNo-code
Contacts and deals stay level with the thread, whichever side the change started on.

Enterprise & regional CRM

Microsoft Dynamics 365No-codeAPI
Bridge it through a connector, or call the API from whichever service already talks to Dynamics.
Bitrix24No-code
Hang WhatsApp off the workflows your team already runs in there.
NimbleNo-code
Put a contact's WhatsApp history where the rest of their record already lives.

Sheets, bases & apps you built

Google SheetsNo-code
One row, one recipient, with the delivery result landing back in the column beside it.
AirtableNo-code
A view is an audience and a record edit is a trigger. No export step in between.
BubbleAPI
An app you assembled yourself calls the API directly; there is no connector sitting in the middle.

Forms, bookings & sites

TypeformNo-code
The submission opens a thread while the answers are still on the screen.
CalendlyNo-code
Booking confirmed, reminder the evening before, and a nudge for whoever does not turn up.
WordPressNo-codeAPI
Contact forms and post events reach the number through a connector, or through a few lines against the API.

AI assistants

Claude Desktop & Claude CodeMCP
Reads a thread, drafts the reply, and waits for you to approve the send.
ChatGPTMCP
The same tools, wherever your account allows a custom connector.
Cursor & VS CodeMCP
Pull a customer's history without leaving the file you are working in.

Anything with a connector on one of those four platforms is a single workflow away, and anything with an HTTP API of its own is a webhook and a POST away. Browse the integration guides

No code

Four builders, one shape

It always comes down to one of two sentences. Something happens over there and a WhatsApp message goes out, or a message arrives here and something happens over there. Use whichever of the four your team is already paying for.

Zapier

A straight-line editor: one thing happens, one thing follows. The shortest route when the other app is obscure.

Make

A canvas where each step is a module you can branch, filter and loop. Pick it when the logic forks.

n8n

Runs on infrastructure you control if you want it to, so the payloads never leave your own network.

Integrately

Prebuilt recipes you switch on rather than assemble. Fastest when the flow is an ordinary one.

Whatever the other app is, if one of those four lists it then it can reach your number without a line of code being written at either end.

Webhooks & API

Everything that happens, pushed to your server

Register an HTTPS endpoint once and WaliChat posts a JSON body to it the moment something changes: a customer writes, a message is read, a chat is reassigned, a contact is edited. Your server decides what follows, whether that is answering through the API, opening a ticket or updating a row.

message:in:new
message:out:new
message:out:ack
message:out:failed
message:update
message:reaction
chat:update
contact:update
status:update
group:update
channel:in
number:session

Subscribe to all of them or to just one, and scope the subscription to a single number.

Read the API docs Open the API tester

REST · JSON · HTTPS

# Register a webhook endpoint
curl -X POSThttps://api.wali.chat/v1/webhooks #{'\n'}  -H"Authorization: $WALI_TOKEN" #{'\n'}  -H"Content-Type: application/json" #{'\n'}  -d'{"name":"Orders","url":"https://acme.dev/wali","events":["message:in:new"]}'

// Handle an inbound WhatsApp message
app.post("/wali", (req, res) => {
  const { event, data } = req.body
  if (event ==="message:in:new") {
    queue.add({ from: data.fromNumber, text: data.body })
  }
  res.sendStatus(200)
)

# Answer from your own backend
requests.post(
"https://api.wali.chat/v1/messages",
    headers={"Authorization": token},
    json={"phone": data["fromNumber"],"message": reply},
)

Webhook payload · message:in:new

{"event":"message:in:new","data": {"fromNumber": "+14155550142","body": "Do you ship to Portugal?" } }

MCP

The route where nobody builds anything

The other three routes ask you to describe the work in advance. This one does not: paste a single URL into any assistant that implements Model Context Protocol and it picks the WhatsApp tools up by itself, under the same key and the same permissions your agents work under. Reading runs freely; anything that writes is put in front of you first.

"Summarise everything that came in on the sales line overnight."
"Draft a reply to the invoice question and label the contact Billing."
"Which chats are still waiting on us from yesterday?"

How the MCP server works Read the docs

Recipes

Three you could build this afternoon

Each one is a rule: a condition, a consequence, and something a person no longer has to remember to do.

E-commerce

The parcel update nobody has to chase

When: Your shop marks an order as dispatched.
Then: The workflow posts the order code and the courier link to the number that placed it.

If the buyer answers, the reply lands in the shared inbox for any agent to pick up, rather than in a no-reply mailbox.

Sales

Every enquiry has an owner before it cools

When: Somebody writes to your number for the first time.
Then: message:in:new fires, your workflow creates or updates the record on your side, and the chat is handed to a department.

Whoever opens it already sees the name, where the person came from, and everything said so far.

Support

The overnight queue sorts itself

When: A question arrives hours after the office emptied.
Then: A Flow answers what it can and marks what it cannot, while the webhook drops the transcript into your own system.

The morning shift starts on a queue already split into handled, waiting, and needs a person.

Build it with Flows See the API in detail

Choosing

Which route should you take first?

Nothing here is exclusive, and plenty of teams keep a connector for the ordinary sends and a webhook for everything that needs judgement. This is only about where to begin.

The four integration routes compared
	Connector platforms	Webhooks	REST API	MCP server
Who wires it up	Anyone on the team	A developer, once	A developer	Anyone who can paste a URL
What you need first	An account on the builder	An HTTPS endpoint	An API key	An MCP-capable client
Which way the data moves	Both ways	Into your systems	Out of your systems	Both, a request at a time
Where the logic lives	On the builder's servers	On your server	On your server	In the assistant's session
When it runs	On a trigger, unattended	The instant something changes	Whenever your code says so	While a person is watching
Suits you when	Both apps already have a connector	You need to react to customers	You are sending at volume	The work is one-off and needs judgement
What it adds to your bill	The builder's own subscription	Nothing	Nothing	Nothing

Your WaliChat plan covers the API, the webhooks and the MCP server. A connector platform bills you for its own plan separately. Compare the plans

From zero to the first event

Console
Cut an API key
One key, from your account settings. The API, the tester, the connector platforms and the MCP server all authenticate with the same one.
Webhooks
Point us at a URL
Add an HTTPS endpoint and tick the events you want. A sample body goes out immediately, so you can prove it landed before you write anything.
Your stack
Wire the far end
Drop the trigger into your builder, or take the JSON yourself and answer over the API. Both can point at the same number.
Live
Watch the log
Every delivery keeps its status code, its response time and its error text, so a broken endpoint announces itself instead of going quiet.

Integration questions, answered

My tool is not on that list. Now what?

The list is the shortlist, not the ceiling. If your app appears on Zapier, Make, n8n or Integrately, it is one workflow away today. If it does not, it almost certainly has an HTTP API of its own, and reaching one of those is exactly what the webhooks and the REST API are for.

Does any of this need a developer?

Not the connector route: one trigger and one action on a platform your team can already use. Code only enters the picture when you want logic that lives on your own server, or a payload nobody has built a connector for.

Is integration access charged separately?

No. The REST API, the webhooks and the MCP server come with the plan, and there is no integrations tier to move up to. One caveat worth knowing: reaction events are only carried on the larger plans, while every other event is on all of them. The connector platforms bill you for their own subscriptions.

What can a webhook actually tell me?

Messages in and out, delivery acknowledgements, failures, edits, reactions, chat and contact changes, group updates and session status. Take all of them or a single one, and change your mind later without touching the code.

Can a webhook be pinned to one number?

Yes. A subscription can be scoped to a specific number, so the workflow behind your sales line never sees a byte of support traffic.

What happens while my endpoint is down?

The failure is recorded rather than swallowed. Each delivery keeps its HTTP status, its response time and the error text in the webhook log, so you can see precisely what broke and when.

Can I try a call before writing any code?

Yes. The docs carry copy-and-run examples and a live tester that fires real calls against your own account, so the first request you make is not one you had to write first.

Can an AI assistant send things on its own?

Reading is free-running; writing is not. Sending, assigning or launching a campaign is a tool call, and clients that support approval put it in front of you before it goes anywhere. The MCP page covers the permission model in detail.

Do I have to change my number for any of this?

No. Every route here runs on the WhatsApp Business number you already use, with the chats and the team structure already in the account.

Stop losing WhatsApp messages today

Join 5,000+ teams already using WaliChat to grow faster.

Start Free Trial NowSeven days on us · Nothing to pay up front · Connected in minutes