Integration
Messaging nodes for n8n
The community node is generated from our OpenAPI specification, so every endpoint the REST API exposes is available as a node operation — not a hand-picked subset that drifts out of date.
Install
@waapiapp/n8n-nodes-waapiIn n8n: Settings → Community nodes → Install, then paste the package name. Self-hosted n8n only — community nodes are not available on n8n Cloud.
Three steps to a working flow
Add the credential
Create a WaAPI API credential in n8n and paste the API token from your dashboard. The node authenticates with a bearer token — there is no OAuth dance and no callback URL to register.
Pick a resource and operation
Resources mirror the API: instances, messages, chats, contacts, groups, channels, labels, stories and polls. Choosing a resource narrows the operation list, and the parameter fields are generated from the spec.
Receive with a webhook node
Point your instance webhook at an n8n Webhook node to drive a flow from an incoming message. Outbound uses the WaAPI node; inbound is a plain webhook, so it works on any n8n version.
The chat ID is the one thing to get right
Every send operation takes a chatId.
Its suffix decides where the message lands, and it is the single most common cause of a
flow that runs green but delivers nothing.
| Target | Format |
|---|---|
| One person | 50664083362@c.us |
| Group | 123456789-123456789@g.us |
| Channel | 123456789@newsletter |
n8n questions
What the node does and where its limits are.
-
No. Community nodes can only be installed on self-hosted n8n. On Cloud you can still use the service through plain HTTP Request nodes against the REST API, and a Webhook node for incoming events.
-
It is generated from our OpenAPI specification rather than written by hand, so operations track the API. When we ship an endpoint, regenerating the node exposes it.
-
Set your instance webhook URL to an n8n Webhook node. Incoming events arrive as JSON, including the chat ID you need to reply to, so a send node can answer in the same flow.
-
No. Billing is a flat rate per connected account regardless of how many workflow executions or messages you run through it.
-
Check the chat ID suffix first — a group ID sent as @c.us is accepted and goes nowhere. If the format is right, the sending number may be under a restriction, which the API cannot see at send time.
Connect an account and start sending
One flat rate per connected account. Unlimited messages, no approval process, no per-message invoice.