Via API and webhooks

Connect WhatsApp to n8n with Haiya's webhooks.

The same mechanism as Zapier, with n8n's Webhook node. Haiya posts its eight business events to the node's address, and a workflow starts a Haiya automation by calling an incoming-webhook URL. There is no n8n node for Haiya.

Start free trial Book a demo

An n8n HTTP Request node calling a Haiya webhook URL, the automation it starts, and the order template in a WhatsApp chat

What you can do with n8n and WhatsApp.

Haiya to n8n

Run a workflow when something happens in Haiya.

Haiya sends eight business events: lead.created, lead.stage_changed, lead.owner_assigned, request.opened, request.status_changed, payment.received, order.placed and form.completed. You choose them on the web dashboard under Settings → Integrations → Webhooks & events.

Each delivery is a signed JSON POST to your Webhook node
Pick the events per destination

n8n to Haiya

Start a WhatsApp automation from a workflow.

When your workflow sees a new order in your own database for Baraka Otieno (+254722555046), an HTTP Request node posts to a Haiya incoming-webhook URL with his phone number. Haiya checks the call and starts the automation, which can send him an approved WhatsApp template.

The body needs the customer's phone number
A repeated delivery is dropped

For developers

Send a message straight through the WhatsApp API.

The Haiya WhatsApp API takes requests shaped like Meta's Cloud API, with a Haiya API key, so an HTTP Request node can send a message without a Meta developer app of your own.

API keys are made by an owner or admin in Haiya

Read the API and webhook docs

What you need

An n8n workflow whose Webhook node can be reached over https from the internet, on n8n's cloud or your own server.
An owner or admin in Haiya: only they can add an event destination.
The Haiya web dashboard: event destinations and automations are set up on the web.
A WhatsApp number connected in Haiya. You do not need a Meta developer app of your own.

How to connect n8n to WhatsApp with Haiya.

Start a workflow with a Webhook node
In n8n, start a workflow with the Webhook node, set it to accept POST and copy its production URL. That URL answers once the workflow is live.
In the other tool
Add it as an event destination
On the Haiya web dashboard, open Settings → Integrations → Webhooks & events, add a destination, paste the n8n URL and choose which of the eight business events to send.
In Haiya
Paste your n8n webhook URL and choose which business events to send.
Keep the signing key
Haiya shows the destination's signing key once. Keep it in your workflow if you check each delivery's X-Haiya-Signature-256 header.
In Haiya
Send a test event
Use the destination's test button in Haiya and look at the delivery in n8n's executions, then map its fields in the next nodes.
In Haiya and the other tool
To go the other way, call Haiya
Add the Incoming webhook trigger to a Haiya automation and copy its URL. In your workflow, an HTTP Request node posts to that URL with the customer's phone number.
In Haiya and the other tool

How the data moves

Haiya
A signed business event (Webhook node)
Your n8n workflow
n8n's own nodes
Your other systems

Your n8n workflow to Haiya: A POST to an incoming-webhook URL

Technical details.

The eight business events

lead.created
lead.stage_changed
lead.owner_assigned
request.opened
request.status_changed
payment.received
order.placed
form.completed

Each delivery to n8n

POST, application/json
X-Haiya-Signature-256: sha256=<hex>
X-Haiya-Event-Type
id, event, occurredAt, workspaceId, data

n8n nodes this guide uses

Webhook (trigger)
HTTP Request

Calls from n8n into Haiya

POST /hooks/automations/<token>
POST /whatsapp/<version>/<phone-number-id>/messages

Read the API and webhook docs

What the n8n connection does not do.

There is no n8n node for Haiya: no Haiya node to pick inside n8n. You use n8n's own Webhook and HTTP Request nodes.
Haiya sends these eight business events and no others. A business event never carries a message body.
A phone number in a business event is masked to its country code and last four digits, so a workflow cannot message a customer from an event alone.
Haiya posts only to a public https address. A workflow on a laptop or a private network does not receive events.
Up to 10 event destinations per workspace. Only owners and admins can add, change or remove one.
A delivery that fails is retried for up to 7 days. A destination that has failed without a break for the whole 7 days is switched off.
Every delivery is signed with X-Haiya-Signature-256, and a destination's signing key is shown once, when you create it.
An incoming-webhook URL needs the customer's phone number. Without one, nothing starts.

Questions about n8n and WhatsApp.

Is there a Haiya node for n8n?

No. There is no n8n node for Haiya. You connect the two with n8n's own Webhook node, to receive Haiya's business events, and its HTTP Request node, to call Haiya.

Which Haiya events can start a workflow?

Eight business events: lead.created, lead.stage_changed, lead.owner_assigned, request.opened, request.status_changed, payment.received, order.placed and form.completed. You choose them per destination under Settings → Integrations → Webhooks & events.

Do I need my own Meta developer app?

No. Your WhatsApp number is connected in Haiya, so n8n talks to Haiya, not to Meta. An HTTP Request node can send a message through the Haiya WhatsApp API with a Haiya API key.

Does it work with self-hosted n8n?

Yes, if the Webhook node's address is public and uses https. Haiya does not post to private or internal addresses.

How do I check that a delivery came from Haiya?

Each delivery carries an X-Haiya-Signature-256 header: an HMAC-SHA256 of the body, made with the destination's signing key. Haiya shows that key once, when you create the destination.

Connect n8n to WhatsApp with Haiya.

Start in the app, or book a demo and we will walk you through the set-up.