wavesflo

Send and receive WhatsApp through a WavesFlo deployment — messages, groups, contacts, channels, and every event as a trigger.

Package Information

Released: this month
Downloads: 0 weekly / 0 monthly
Latest Version: 1.1.0
Author: WavesFlo

Documentation

n8n-nodes-wavesflo

Send and receive WhatsApp through your own WavesFlo deployment.

Two nodes:

  • WavesFlo — every catalogued public API action: messages, groups,
    contacts, chats, channels, media, account, plus the Work and Sales surface
    (conversations, tickets, calls, pipelines, opportunities, companies, tasks).
  • WavesFlo Trigger — starts a workflow on any published event, including
    ticket.*, conversation.*, opportunity.*, company.* and task.*. It
    registers its own webhook when you activate the workflow and removes it when
    you delete it.

Both are built from generated/descriptors.json, so the operation and event
lists are whatever the API publishes — this README deliberately states no count
that could go stale.

Install

Settings → Community Nodes → Install → n8n-nodes-wavesflo.

Credentials

Two fields: your deployment's base URL, and a scoped API key from
Integration → API keys. The key is shown once. The trigger needs
webhooks:manage; each operation needs its own scope.

Grant only the scopes the workflow needs. The destructive scopes — retract a
message, administer groups, block a contact, delete a channel, change the account
— are grantable but deliberately have no operations in this node. A
retraction reachable from a spreadsheet trigger is a mass retraction one
misconfiguration away; if you need those, call the API directly with a key that
carries the scope.

AI agents: use MCP instead

For an n8n AI Agent, add the MCP Client Tool and point it at the
WavesFlo MCP endpoint (Server Transport: HTTP Streamable; Authentication:
Header Auth, Authorization: Bearer <key>). The agent then sees exactly the
tools the key's scopes allow. Integration → AI apps (MCP) in WavesFlo builds
the exact settings.

Sending is governed

Every send passes the opt-out register, group consent, quiet hours and the
per-number daily cap. Two refusals, needing different handling:

  • 403 SEND_BLOCKED — the recipient opted out. Retrying never works.
  • 429 SEND_DEFERRED — quiet hours, a cooldown, a resting account. The same
    send is accepted later; Retry-After says when.

Treat them alike and you will either keep messaging somebody who asked you to
stop, or abandon a send that was merely postponed.

Idempotency

Operations that create something carry an Idempotency Key field, defaulted to
a value unique per item per execution. Leave it. n8n retries on timeout, and a
send that timed out may already have been delivered — without the key the retry
sends a second message and spends the daily cap twice.

The trigger verifies signatures

On by default, and worth leaving on: anyone who learns the callback URL can post
to it, and the HMAC is the only thing that says a delivery came from your
deployment. The node also deduplicates on the envelope id, because delivery is
at-least-once and a retry is otherwise indistinguishable from a genuine second
event.

This package is generated

nodes/WavesFlo/generated/descriptors.json is produced from the API's own route
table by npm run generate:connectors in the backend, and CI fails if the
committed copy has drifted. Do not hand-edit it — the point is that this node and
the API cannot describe different products.

Discussion