WhatsApp middleware
waboom
The middleware between WhatsApp and your flows.
waboom turns WhatsApp into an API: every message becomes an event, you switch on signed webhooks and wire them into your flows — Shopify Flow, n8n, Make. Conversations pass through: we don't keep an archive of them.
By the numbers
0
messages written to the gateway disk
HMAC
signature on every webhook delivery
/v1
versioned API with an OpenAPI spec
GDPR
per-contact export and deletion
What it is
waboom sits between the WhatsApp number you already use and the systems you want to automate. Every message — text, media, transcribed voice notes, groups, calls — becomes an event; you switch on webhooks and route them wherever you need: Shopify Flow, n8n, Make or your own endpoint. Every delivery is HMAC-signed, and the queue is persistent with retries, dead-letter and replay from the console.
It's built as a bridge, not an archive. Messages transit toward your flows and remain on the gateway only in a temporary in-memory window; the database holds instance and chat metadata with hashed tokens. If you configure a webhook, the delivery log keeps the event payload for your plan's retention window so you can retry and replay — with per-contact export and deletion whenever you want.
The problem
WhatsApp is where your customers write, and it's the one channel that doesn't talk to your stack.
A customer asks for a return over WhatsApp and someone, by hand, opens the order, tags the customer, generates the code. Every message is a missed automation because the channel emits no events. waboom fills exactly that gap: it makes WhatsApp a webhook source like any other service in your stack, without forcing you to build and maintain a gateway.
What it does
Signed webhooks and flows
HMAC signature on every delivery, a persistent queue with retries, dead-letter and replay from the console. Wire up Shopify Flow, n8n or Make in minutes, with no code to maintain.
Every message type as an event
Text, photos and video, transcribed voice notes, groups with participants, call events: everything reaches your endpoint in the same shape, ready to route.
Real-time events
Reactions, edited and deleted messages, group updates and catalog orders or carts also become webhook events you can use in your flows.
Multi-tenant and teams
Organisations, owner/admin/member roles and one instance per client with dedicated, revocable tokens. Built for agencies running several numbers on behalf of several clients.
Broadcast and anti-ban
Paced sending per number, idempotency on sends, and list broadcasts with per-recipient status to reduce the risk of a block. Versioned /v1 API with an OpenAPI spec.
AI-native, MCP server
The official @waboom/mcp server lets you send WhatsApp messages from Claude, Cursor and any AI agent, with number verification and code-based pairing.
How it works
- 01
Connect the number
Create an instance from the console and pair your WhatsApp number by QR or code. One instance per number, with dedicated, revocable tokens.
- 02
Switch on webhooks
Point at your destination endpoint and pick the events. Every delivery travels HMAC-signed, with automatic retries and dead-letter on persistent failure.
- 03
Wire the flows
From there the event lands in Shopify Flow, n8n or Make: tag the customer, open a draft order, send a return code. No code to maintain.
- 04
Run it from the console
Instance status, delivery log, replay of an event that went wrong, and export or deletion of a single contact's data.
Who it's for
E-commerce and customer care
Teams fielding returns, tracking and support requests on WhatsApp who want them to become automations on the store instead of manual work.
Teams that automate
People already living inside n8n, Make or Shopify Flow who want WhatsApp added to their event sources with the same reliability as every other trigger.
Agencies and software houses
Anyone who needs one number per client with isolation, roles and separate tokens, without building and maintaining an in-house WhatsApp gateway.
The technical choice
A Barikreativa product: design, architecture and full-stack development in-house. Published on the Shopify App Store.
Works with
Pricing
Free
€0/mo
To start and try the API.
- 1 WhatsApp number
- 1,000 messages per month
- Basic webhooks
- 24-hour log retention
Starter
€19/mo
One number, in production.
- 1 WhatsApp number
- 10,000 messages per month
- Signed webhooks + retry
- Organisation API key
- 7-day retention
Pro
€49/mo
For teams automating seriously.
- 3 WhatsApp numbers
- 50,000 messages per month
- Broadcast, idempotency, replay
- Configurable rate limit
- 30-day retention and priority support
Business
€149/mo
Volume and teams.
- 10 WhatsApp numbers
- 250,000 messages per month
- 99.5% SLA and backups
- GDPR export and IP allowlist
- Custom webhook domain
Monthly prices, VAT excluded, per connected number. Above the plan cap: €2 per 1,000 messages, with no sudden cut-off — just a warning at 80% and 100%. Enterprise is priced to fit, with unlimited numbers, a dedicated isolated instance, DPA, SSO and the official WhatsApp API on request.
Frequently asked questions
- Does waboom store my conversations?
- No, we don't keep an archive of them. It's a pass-through middleware: on the gateway, messages live only in a temporary in-memory window. The database holds instance and chat metadata with hashed tokens. If you configure a webhook, the delivery log keeps the event payload — text included — for your plan's retention window, so you can retry and replay.
- Do I need to know how to code?
- For standard use cases, no: connect the number, point at an endpoint, and build the automation in Shopify Flow, n8n or Make. If you'd rather use your own endpoint, the API is versioned /v1 with an OpenAPI spec.
- How do the webhooks work?
- Every event is delivered to your endpoint with an HMAC signature to verify. The queue is persistent: on failure the system retries, dead-letters what keeps failing, and lets you replay it from the console.
- What does it integrate with?
- Natively with Shopify Flow, n8n and Make, and with any HTTP endpoint of your own. There's also an official MCP server for sending messages from Claude, Cursor or other AI agents.
- How do I connect my WhatsApp number?
- Create an instance from the console and pair the number by QR or code. Every instance has dedicated tokens you can revoke at any time.
- What happens if I go over my plan's message cap?
- Nothing gets cut off: you get a warning at 80% and 100%, and messages above the cap cost €2 per 1,000.
Put waboom to work on your store
Designed, built and maintained by our own team. If you need a hand fitting it into your stack or customising it, we do that too.