n8n & Integrations

Rapiwa works out of the box with n8n and any no-code/low-code tool that can make HTTP requests. No special endpoints — the same Device Key auth, the same send-message body, and the same receive-message webhook.

n8n

Rapiwa provides two building blocks:

Node	Maps to	Credential
Rapiwa Trigger	the `receive-message` webhook	Device Key
Rapiwa action	`POST /api/send-message`	Device Key

Trigger — receive messages

The Trigger node registers a stable production webhook URL as your device's Webhook URL. Every inbound message fires the workflow with the receive-message payload (contact_id, message, message_id, media_info, …).

Action — send a message

The action node calls send-message with your Device Key credential. Wire the fields from earlier nodes — e.g. reply to {{$json.contact_id}} with computed text.

Byte-compatible

The Device-Key Bearer auth, the send-message body, and the receive-message payload are kept stable so existing n8n workflows keep working across updates.

Generic HTTP (Make, Zapier, custom)

Any platform that can POST JSON with a Bearer header can drive Rapiwa:

POST https://app.rapiwa.com/api/send-message
Authorization: Bearer YOUR_DEVICE_KEY
Content-Type: application/json

{ "number": "8801234567890", "message_type": "text", "message": "Order #1234 shipped 📦" }

Point the tool's inbound webhook at your device's Webhook URL to receive messages, and call send-message to reply. That's the whole integration surface.

Common recipes

Order/shipping alerts — trigger on your store's events → send-message a status update.
Support auto-reply — Rapiwa Trigger → branch on keywords → send-message (quote the inbound message_id for threading).
Lead capture — inbound message → append to a sheet/CRM → send a confirmation.
Broadcasts — schedule a job → send-bulk-message (paced, anti-ban) → reconcile via the status webhook.