Kapso TriggerInstall

Summary

Receive selected Kapso WhatsApp or project events through an n8n webhook and start the workflow with each payload. Configure the scope, subscribed events, webhook kind, and registration mode; phone-number scope also requires a phone number ID.

Inputs

• Scope — Choose Phone Number to receive WhatsApp message, conversation, or contact events for a phone number, or Project for WhatsApp configuration, phone-number lifecycle, or workflow execution events.
• Phone Number ID (required) — Meta phone_number_id to subscribe to when Scope is Phone Number.
• Events (required) — Select one or more events for the chosen scope. Phone-number events default to whatsapp.message.received; project events default to whatsapp.phone_number.created.
• Webhook Kind — Choose Kapso for filtered Kapso payloads, with payload version and optional inbound message buffering, or Meta for raw Meta webhook forwarding.
• Registration Mode — Automatic creates and deletes the webhook through the Kapso API. Manual skips API registration and requires an existing webhook targeting the n8n URL.
• Payload Version — Kapso payload version to deliver (v1 or v2); shown for Kapso webhook kind and defaults to v2.
• Buffer Received Messages — For Kapso webhooks in Phone Number scope, enable batching of rapid whatsapp.message.received events; defaults to off.
• Buffer Window Seconds — When buffering is enabled, set how long to wait for more inbound messages (1–60 seconds; default 5).
• Max Buffer Size — When buffering is enabled, set the maximum inbound messages per batch (1–100; default 10).
• Verify Signature — Validate the incoming X-Webhook-Signature using the Kapso webhook secret; defaults to enabled. A missing secret or signature, or an invalid signature, rejects the request.
• Webhook Secret — Optional secret used for signature verification. If omitted, the node uses a secret saved from Kapso webhook creation when available.

Output shape

One n8n item per webhook body item, sent on the main output to start the workflow.

Each item contains the body fields at the top level when the body item is an object, otherwise the value is placed in payload. The node adds a _kapso object with event, idempotencyKey, payloadVersion, isBatch, and batchSize metadata read from webhook headers; absent headers may yield undefined values. Automatic registration and signature verification require a public HTTPS webhook URL and the Kapso API credential.

Links

• n8n community nodes installation guide