An n8n community node for Volara — the omnichannel WhatsApp/messaging and CRM platform. Use it to send messages, manage contacts, launch broadcasts, read conversations, and start workflows when Volara events arrive.

n8n is a workflow automation tool. Volara is a messaging and customer platform. Together you can wire up things like "when a new WhatsApp message comes in, look up the contact, and post it to Slack" without writing code.

Installation

In n8n (community nodes)

Open your n8n instance.
Go to Settings → Community Nodes.
Click Install, enter n8n-nodes-volara, and confirm.

After installation the Volara and Volara Trigger nodes appear in the node panel.

Community nodes are available on self-hosted n8n. On n8n Cloud, verified community nodes can be installed from the same panel.

Manual / development install

git clone https://github.com/volara-asia/volara-n8n.git
cd volara-n8n
npm install
npm run build
# link into your n8n custom nodes folder

Credentials

The node uses one credential, Volara API:

In Volara, go to Settings → API keys and create a key.
In n8n, add a new Volara API credential.
Paste the API Key.
Leave Base URL as https://api.volara.chat unless you run a self-hosted or region-specific Volara deployment.
Click Test — it calls GET /api/v1/metrics/dashboard to confirm the key works.

The key is sent as Authorization: Bearer <key> on every request and is never logged.

Operations (Volara node)

Message

Send — send a message into a conversation (POST /api/v1/conversations/{id}/messages). Provide a plain Text body, or a structured Content JSON payload for templates/media, plus an optional Type hint.

Contact

Create — create a contact in the CRM (POST /api/v1/customers). Fields: name, email, phone number (E.164, e.g. +6281234567890), source.
Get — fetch one contact by ID (GET /api/v1/customers/{id}).
List — list or search contacts (GET /api/v1/customers) with search, sort, order, and optional auto-paging via Return All.

Broadcast

Create — create a broadcast campaign (POST /api/v1/broadcasts). Fields: title, message content, target audience JSON.
List — list broadcasts (GET /api/v1/broadcasts).

Conversation

Get — fetch one conversation by ID (GET /api/v1/conversations/{id}).
List — list or search conversations (GET /api/v1/conversations) filtered by status and free-text search, with optional auto-paging.

Trigger (Volara Trigger node)

The trigger starts a workflow when Volara delivers a webhook event such as a new message, a new or updated conversation, or a ticket.

Add a Volara Trigger node and open it.
Copy the node's Production URL.
In Volara, go to Settings → Webhooks, paste the URL, and choose which events to send.
Optionally narrow the events the node reacts to with the Events field.

Volara delivers a JSON body of the form:

{
  "id": "evt_...",
  "type": "message.received",
  "createdAt": "2026-06-23T10:00:00Z",
  "data": { },
  "organizationId": "org_..."
}

Signature verification (pending)

Volara signs the raw request body with HMAC-SHA256 and sends it in the x-volara-signature header (hex, optionally prefixed sha256=). Verifying that header protects the endpoint from forged events.

Automatic subscription registration and HMAC verification are not yet active — they firm up once the Volara webhook signing API is finalized. The node already exposes a Signing Secret option so workflows are ready to switch verification on without reconfiguration. Until then, treat the webhook URL as a shared secret.