@kunshort/n8n-nodes-wavesenda

github.com/kunshort/n8n-nodes-wavesenda is a generated mirror. It is force-pushed from the WaveSenda monorepo on every release, so anything committed here is overwritten. Issues and pull requests belong upstream — this repository exists because the package registry needs a public one, not because the code is developed in it.

WhatsApp for n8n, via WaveSenda — send and receive messages, check numbers, and start workflows from inbound conversations.

Install

In n8n: Settings → Community nodes → Install, then @kunshort/n8n-nodes-wavesenda.

Self-hosted n8n only — community nodes are not available on n8n Cloud.

Credentials

Issue a key under API keys in the WaveSenda console and paste it into a WaveSenda API credential. Use a ws_test_ key while you are building: it routes every send to a sandbox that acknowledges and emits webhooks without touching WhatsApp, so a workflow you are still debugging cannot message a real customer at 3am.

The Test button calls the API, so a bad key fails in the credential dialog rather than halfway through a production run.

WaveSenda node

| Operation | Does | | --- | --- | | Send Message | Text, image, video, document or location | | Check Numbers | Which numbers have a WhatsApp account | | List Conversations | Recent conversations | | Read Conversation | The messages in one thread | | Get Session Health | The ban-risk report for one number |

List operations emit one n8n item per record, so the next node iterates without a Split Out.

Idempotency

Every send carries an idempotency key. Leave the field blank and the node derives one from the execution id, node name and item index — so retrying a failed execution returns the original message rather than sending a second one. That matters more here than in most integrations: the recipient's phone has already buzzed, and there is no delete that unsends it from their notification shade.

Set the key yourself when the natural identity is a business one — an order reference, say — so two different workflow runs for the same order also collapse to a single message.

WaveSenda Trigger node

Select the events you want and activate the workflow. The node registers its own endpoint with WaveSenda and removes it on deactivation, so there is no URL to paste into two systems and no orphaned endpoint left behind.

Every delivery is verified against the HMAC signature captured at registration, and deliveries older than five minutes are rejected. An unauthenticated webhook URL is an open door for anyone who guesses it.

Subscribe narrowly. Selecting nothing gets you the full firehose including every delivery acknowledgement, which for a busy number is a lot of executions.

Events worth building on

• message.received — someone messaged you. The usual trigger.
• session.logged_out — the number was unlinked from the handset and needs a fresh QR scan. Worth alerting a human; session.disconnected usually recovers on its own and paging someone for it trains them to ignore the alert.
• session.at_risk — health crossed into risk. Fires before sending is throttled, not after.
• ai.handoff — an AI agent escalated to a person.

Deliveries are at-least-once. A retry after your workflow succeeded but the response was lost, or a manual replay from the console, will arrive twice — key on the message id if a duplicate would matter.

Before you send to anyone real

WaveSenda automates a standard WhatsApp account rather than using Meta's official Cloud API. That is contrary to WhatsApp's terms of service and a number can be rate-limited or banned — most often from unsolicited bulk sending. Use Check Numbers before a batch, watch Get Session Health, and message people who asked to hear from you.

MIT licensed.