Integrations
For the cases where the point is not to write code at all. Each one sends through a number you own, so messages arrive from the business rather than from a shortcode nobody recognises.
What each one is
These are not all the same shape, and the difference matters before you go looking for something to install. Two are packages you add to software you already run. One is an application you connect to your store, with nothing to download.
| Shape | Where it comes from | |
|---|---|---|
| n8n | Community node | @kunshort/n8n-nodes-wavesenda |
| WordPress | Plugin | Plugin directory, wavesenda |
| WooCommerce | Plugin | Plugin directory, wavesenda-for-woocommerce |
| Shopify | Connected app | Installed from a listing or an install link — there is nothing to download |
n8n
Two nodes: an action node with five operations, and a trigger that starts a workflow from anything that happens on your number. Between them you can answer an inbound message, check a list of numbers before a campaign, or route a conversation into whatever else n8n reaches.
Install it from Settings → Community nodes → Install, then create a WaveSenda API credential from a key issued under API keys in the console. The credential’s Test button calls the API, so a wrong key fails in the dialog rather than halfway through a production run.
ws_test_ key while you are still wiring things up. It acknowledges every send and fires the same webhooks without touching WhatsApp, so a half-finished workflow cannot message a real customer at three in the morning.| Operation | What it does |
|---|---|
| Send Message | Text, image, video, document or location |
| Check Numbers | Which of these numbers are reachable on WhatsApp |
| List Conversations | Threads, most recently active first |
| Read Conversation | The messages in one thread |
| Get Session Health | Deliverability and warm-up state for a number |
The trigger fires on sixteen events, which are the same events the webhooks deliver — the node is a way to receive them without hosting an endpoint.
| Events | |
|---|---|
| Messages | received, sent, delivered, read, failed, reaction |
| Sessions | connected, disconnected, logged_out, at_risk |
| AI agents | replied, handoff |
| Other | call.received, campaign.completed, contact.opted_out, group.participants_changed |
WordPress
Two plugins, because a shop and a brochure site want different things. Both are in the WordPress plugin directory and install the usual way.
| Plugin | For | What it does |
|---|---|---|
wavesenda | Any site | The chat widget, form submissions forwarded to your WhatsApp, a click-to-chat button, and alerts for comments, registrations and publishes. |
wavesenda-for-woocommerce | Shops | Order status notifications and one abandoned-cart reminder, with consent collected at checkout. |
Running both is supported and does not double anything up: the first messages you about your own site, the second messages your customers about their orders. They are configured separately and bill separately.
Shopify
Not a package. The Shopify integration is an application you connect to your store, and it sends order confirmations, fulfilment and tracking, cancellations, refunds, and one abandoned-checkout reminder.
Or write the four lines yourself
None of this is doing anything you could not do directly. An integration exists to save you hosting something; the API underneath is the same one.
curl -X POST https://api.wavesenda.com/api/v1/messages/send/ \
-H "Authorization: Bearer $WAVESENDA_API_KEY" \
-H "Content-Type: application/json" \
-d '{"session":"support","to":"+237670000000","text":"Your order is ready."}'