Self-hostable · Unmetered · Official Meta API

WappBlaster + n8n Integration

Send WhatsApp messages from n8n workflows. Because n8n can be self-hosted, this is the route for teams whose data cannot pass through a third-party automation cloud, and for anyone who wants unmetered runs.

Connect n8n See pricing

Data flow

What moves between n8n and WappBlaster

n8n → WappBlaster

n8n workflows (cloud or self-hosted) → WappBlaster (WhatsApp send)

  • HTTP request node calls the send endpoint
  • Database or queue change triggers a message
  • Scheduled workflow sends a batch
  • Internal system event triggers a notification

Frequency: Real-time or scheduled

Setup

Connecting it

  1. 1

    Get API credentials

    Generate WappBlaster API access for the sending channel.

    ~5 minutes

  2. 2

    Add an HTTP Request node

    Point it at the WappBlaster send endpoint with your auth header.

    ~10 minutes

  3. 3

    Map the payload

    Recipient number, template name and variables from the previous node's output.

    ~10 minutes

  4. 4

    Activate the workflow

    Test against your own number first, then activate.

    ~5 minutes

Use cases

What teams do with it

On-premise system alerts

Internal systems that cannot reach a public automation cloud still notify over WhatsApp.

IT and DevOps

Database-triggered messaging

A row change in your own database sends the customer message.

Engineering

Scheduled batch sends

Cron-style workflows that assemble and send a daily batch.

Operations

Data-residency-sensitive flows

Customer data stays inside your infrastructure until the moment of send.

Regulated industries

High-volume unmetered automation

Self-hosted n8n has no per-task charge, which matters at scale.

Technical teams

Frequently asked questions

Can n8n send WhatsApp messages?

Yes, through an HTTP Request node calling the WappBlaster send API, which delivers on the official Meta WhatsApp Business Platform.

Link to this answer
Why use n8n instead of Zapier or Make?

Two reasons: it can be self-hosted, so sensitive data never leaves your infrastructure, and self-hosted runs are not metered per task. The trade-off is that you are running and maintaining the infrastructure yourself.

Link to this answer
Does this need a developer?

Realistically yes. n8n assumes comfort with HTTP requests, JSON and authentication headers. Non-technical teams are better served by the built-in automations builder.

Link to this answer

Still not answered?

Ask a real person. We reply on WhatsApp, usually within the hour.

Ask on WhatsApp

We will wire it up with you

Integration setup is part of onboarding, not a paid add-on. Bring your n8n account to the call and we will connect it together.

Book a setup call