Use the SimpleWA WhatsApp API with n8n

Automating WhatsApp used to mean choosing between two bad options: wrestle with Meta's official Business API — business verification, template approval, per-message billing — or duct-tape a browser extension that breaks every other week. There's now a middle path: a session-based WhatsApp API wired into n8n, the open-source workflow automation tool. Here's what that setup actually looks like, what you can build with it, and where each approach makes sense.

The basicsWhat is n8n, and why pair it with WhatsApp?

n8n is a visual workflow builder. You drag nodes onto a canvas, connect them, and the workflow runs — on a schedule, on a webhook, or on an event from another app. It talks to hundreds of services, and it can be self-hosted for free.

WhatsApp is where a huge share of customer conversations already happen. Open rates dwarf email. The hard part has always been programmatic access: getting messages into your automation stack and replies back out.

Connect the two and any n8n workflow becomes a WhatsApp sender, receiver, or AI agent — with no backend to write and no server to babysit.

Choose your pathThe two ways to connect WhatsApp to n8n

Before the how-to, be clear about the trade-off — most articles gloss over it.

PrerequisitesWhat you'll need

• An n8n instance — n8n Cloud, or self-hosted (one Docker command works for testing).
• A WhatsApp API account with a linked number. This walkthrough uses SimpleWA, a session-based WhatsApp API with isolated sessions and webhooks.
• Your API key from that provider.
• Optional: a chat-model API key (OpenAI, Anthropic Claude, Google copyright) if you want an AI agent.

Step 1Install the WhatsApp node in n8n

SimpleWA publishes an n8n community node. In n8n, open Settings → Community Nodes → Install and enter the package name:

n8n-nodes-simplewa

Prefer the command line? Install it manually, then restart n8n:

cd ~/.n8n/custom

npm install n8n-nodes-simplewa

The node handles three things: sending WhatsApp messages, managing sessions, and registering webhooks.

Step 2Add your credentials

Copy your API key from the provider's dashboard. In n8n, add any WhatsApp node to a workflow, create a new credential from it, paste the key, and save. You should see the connection succeed.

Keep this key private — it's what authorizes messages to be sent from your number.

Step 3Connect the webhook — this is how you receive messages

Sending is only half of it. To react to incoming messages, you need a webhook.

1. Add the Trigger node to your workflow and copy its webhook URL.
2. In your WhatsApp API dashboard, open Webhooks and paste that URL in.
3. Set an HMAC secret, and verify the signature on incoming requests so your workflow only trusts authentic events.

Now every incoming message — plus delivery receipts, read receipts, and session disconnects — pushes into n8n in real time. A typical payload:

"event": "message.received",
"from": "1555XXXXXXX",
"type": "text",
"text":  "body": "Hi, is anyone there?" ,
"timestamp": 1751808000

Step 4Send your first message

Add the Send Message node, map the recipient into the to field and your text into the message body, then hit Execute. Check your phone — it should land within a second or two.

That's the entire foundation: trigger in, send out. Everything below is built on those two nodes.

Use casesWhat you can actually build with it

[Trigger] → [AI Agent + Chat Model + Memory] → [Send Message]

Don't skip thisBest practices before you scale

Session-based copyright are more sensitive than official API numbers. A few rules keep yours healthy:

• Get opt-in. Only message people who agreed to hear from you. No tool makes unsolicited messaging safe — that's the honest truth, and spamming is the fastest way to lose a number.
• Pace your sends. Drop a Wait node (5–15 seconds) between messages instead of blasting.
• Warm up new numbers. Ramp volume gradually over days, not hours.
• Personalize. Identical messages to hundreds of people is the textbook spam signal.
• Respond to webhooks fast. Return a 200 immediately, then do the heavy AI work asynchronously so nothing times out or double-fires.
• Verify HMAC signatures on every incoming webhook.
• Make opt-out easy.

FAQFrequently asked questions

Can I use WhatsApp with n8n without coding?

Yes. n8n's builder is drag-and-drop, and the WhatsApp node exposes send and trigger operations as configurable fields. You can build an auto-reply bot — or even an AI agent — without writing code.

Do I need Meta business verification?

Not with a session-based API. You link an existing WhatsApp number by scanning a QR or pairing code, so there's no business verification and no message-template approval. Meta's official Cloud API requires both.

How much does this cost?

n8n is free to self-host (n8n Cloud has paid tiers). Session-based WhatsApp APIs typically charge a flat monthly fee rather than per message — SimpleWA's entry plan starts around $8/month — while Meta's Cloud API bills per delivered message.

Can the AI agent remember previous messages?

Yes. Attach a memory node keyed by the customer's phone number. A window of around 10 messages balances useful context against token cost; clear it after 24 hours of inactivity.

Will my number get banned?

It can — if you spam. Bans come from spam reports and unsolicited blasts, not from automation itself. Opt-in contacts, paced sending, personalized content, and easy opt-out keep a number healthy.

Wrapping upThe bottom line

If you need WhatsApp inside your automation stack and you don't want to spend two weeks in Meta's verification queue, a session-based API plus n8n gets you from zero to a working two-way integration in an afternoon. Install the node, add a key, connect a webhook, send. From there the same connection powers auto-replies, AI agents, order updates, and booking flows.

Just remember the trade-off you're accepting: speed and simplicity in exchange for unofficial status. Message people who actually want to hear from you, and it holds up well.

Disclosure: this guide references SimpleWA, an independent session-based WhatsApp API. It is not affiliated with WhatsApp Inc. or Meta.