npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@kapso/n8n-nodes-kapso

v0.1.3

Published

Kapso nodes for WhatsApp inbound triggers and outbound messaging in n8n.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

rgaonagorgaonagoaamatteaamatte

Keywords

n8n-community-node-packagekapsowhatsappwhatsapp-cloud-apiautomation

Readme

@kapso/n8n-nodes-kapso

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

Installation

Follow the installation guide in the n8n community nodes documentation.

Package name: @kapso/n8n-nodes-kapso.

Operations

Kapso Trigger

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.created and workflow execution events.

Kapso

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.

Credentials

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.

Compatibility

Generated with the official @n8n/create-node scaffold and tested against the installed n8n node tooling in this repository.

Usage

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.

Example workflows

Inbound WhatsApp message to n8n workflow

  1. Add Kapso Trigger as the first node.
  2. Set Scope to Phone Number.
  3. Enter the Meta phone_number_id for the WhatsApp sender managed in Kapso.
  4. Keep Events set to whatsapp.message.received.
  5. Leave Verify Signature enabled in production.
  6. 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.

Send a WhatsApp reply through Kapso

  1. Add a Kapso node after any trigger or workflow step.
  2. Set Resource to WhatsApp Message.
  3. Set Operation to Send Text.
  4. Enter the sender Phone Number ID.
  5. Enter the recipient phone number in international format without +, for example 15551234567.
  6. 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.

Local testing

Run the package in a local n8n instance with:

npm run dev

This 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 dev

Use 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 5678

With 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.

Resources

Version history

0.1.2

Adds example workflow documentation and Kapso package author metadata for verification.

0.1.1

Adds an npm run test verification script for n8n Creator Portal checks.

0.1.0

Initial Kapso trigger and action nodes.