This is an n8n community node package for Kapso WhatsApp automations.
It includes a trigger for inbound Kapso/WhatsApp webhook events and an action node for sending outbound WhatsApp messages through Kapso.
n8n is a fair-code licensed workflow automation platform.
Installation Operations Credentials Compatibility Usage Example workflows Local testing Resources Version history
Follow the installation guide in the n8n community nodes documentation.
Package name: @kapso/n8n-nodes-kapso.
Starts workflows from Kapso webhooks:
- Phone-number events such as
whatsapp.message.received, delivery statuses, and conversation lifecycle events. - Project events such as
whatsapp.phone_number.createdand workflow execution events.
Actions available in workflows:
- List connected WhatsApp phone numbers.
- List WhatsApp messages stored by Kapso.
- Send WhatsApp text messages.
- Send WhatsApp template messages.
- Send raw WhatsApp Cloud API message payloads.
- Mark WhatsApp messages as read, optionally with a typing indicator.
Create a Kapso API credential with:
- API Key: your Kapso API key. The node sends it as
X-API-Key. - Base URL: defaults to
https://api.kapso.ai. - Meta Graph Version: defaults to
v24.0.
Generated with the official @n8n/create-node scaffold and tested against the installed n8n node tooling in this repository.
For inbound WhatsApp messages, use Kapso Trigger with scope Phone Number, enter the Meta phone_number_id, and subscribe to whatsapp.message.received.
For outbound messages, use Kapso with the Send Text, Send Template, or Send Raw Payload operations. The raw payload operation mirrors the WhatsApp Cloud API payload sent to /{phone_number_id}/messages.
- Add Kapso Trigger as the first node.
- Set Scope to Phone Number.
- Enter the Meta
phone_number_idfor the WhatsApp sender managed in Kapso. - Keep Events set to
whatsapp.message.received. - Leave Verify Signature enabled in production.
- Connect any downstream n8n nodes that should process the inbound message payload.
This workflow starts whenever Kapso delivers a WhatsApp inbound message webhook to n8n.
- Add a Kapso node after any trigger or workflow step.
- Set Resource to WhatsApp Message.
- Set Operation to Send Text.
- Enter the sender Phone Number ID.
- Enter the recipient phone number in international format without
+, for example15551234567. - Set Message to a static value or an n8n expression from an earlier node.
Use Send Template instead when sending approved WhatsApp template messages outside the customer service window.
Run the package in a local n8n instance with:
npm run devThis compiles the node and starts n8n with the local package loaded. For inbound webhook testing, expose local n8n to the internet and set n8n's public webhook URL before starting it:
WEBHOOK_URL=https://your-public-n8n-url.example.com/ N8N_PROXY_HOPS=1 npm run devUse Tailscale Funnel, not Tailscale Serve, when Kapso needs to call your local n8n instance. tailscale serve 5678 is only reachable inside your tailnet. Kapso is outside your tailnet, so expose n8n with:
tailscale funnel 5678With Tailscale Funnel, the public URL should forward to local port 5678. The Kapso Trigger webhook endpoint is generated by n8n and shown in the node UI. The node registers that generated URL with Kapso when the workflow is activated or when n8n starts listening for a manual test webhook. The trailing path configured by this node is webhook, but the full URL includes n8n's workflow-specific webhook ID. If the editor also runs behind the same public URL, set N8N_EDITOR_BASE_URL to that URL too.
If you create the Kapso webhook yourself, set Registration Mode to Manual on the Kapso Trigger node. For n8n's test URL, you must click Test workflow before sending the WhatsApp message; /webhook-test/... URLs are temporary and n8n only keeps them registered while the workflow is listening for a test event. For persistent delivery, use the production URL shown by n8n, activate the workflow, and register that /webhook/... URL in Kapso.
For local manual testing, disable Verify Signature or send a valid X-Webhook-Signature HMAC header. In production, leave signature verification enabled and either let Kapso return the webhook secret during registration or paste the secret into Webhook Secret.
Adds example workflow documentation and Kapso package author metadata for verification.
Adds an npm run test verification script for n8n Creator Portal checks.
Initial Kapso trigger and action nodes.