Registry / http-networking / n8n-nodes-waha

n8n-nodes-waha

library2024.11.5jsnpmunverified

The `@devlikeapro/n8n-nodes-waha` package provides community-contributed nodes for n8n, enabling seamless integration with WAHA (WhatsApp HTTP API). This allows n8n users to automate WhatsApp messaging and interactions within their workflows, leveraging a self-hosted WhatsApp API solution. The current stable version is 2024.11.5, with frequent releases indicated by the recent `2024.9.x` and `2024.11.x` versioning. Key differentiators include its open-source nature, the ability to operate WhatsApp automation without Meta's per-message fees, and the nodes being generated from WAHA's OpenAPI specification, ensuring comprehensive API coverage.

http-networking communication

npm install n8n-nodes-waha

github ↗package ↗homepage ↗

INSTALL

IMPORT

SIG · N8N-NODES-WAHA

n8n-nodes-waha

http-networkingjavascriptv2024.11.5

Install

—

Import

—

Disk

—

Pass rate

0/ 6

Env Coverage0 / 6

glibc

18–22

musl

18–22

Install & Compatibility

Where this runs

tested against v? · npm install

Install × environment matrix

Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux

musl

node 18–226 runs

build_error

glibc

node 18–226 runs

build_error

Code

Verified usage

Verified import paths — ran on the pinned version, not inferred.

WahaNode

✓ /* End-users do not directly import symbols from n8n community nodes. */

This package provides n8n nodes which are installed into an n8n instance and used via its graphical interface. Direct JavaScript imports are typically only for developers building or extending the node itself, not for end-users. If developing, a node class (e.g., 'WahaNode') implementing `INodeType` would be exported.

WAHACredential

✓ /* End-users do not directly import symbols from n8n community nodes. */

Similar to WahaNode, credentials for n8n nodes (like 'WAHACredential') are managed within the n8n application UI and not imported directly in user-facing JavaScript code.

Demonstrates how to install the n8n-nodes-waha community node, configure WAHA API credentials, and build a basic n8n workflow using the WAHA Trigger and WAHA Send Text Message nodes to create an 'echo' bot.

# 1. Install n8n (if not already installed, e.g., via npm or Docker) npm install -g n8n # 2. Add the WAHA community node to your n8n instance via CLI: n8n add:community-node @devlikeapro/n8n-nodes-waha # 3. Start your n8n instance (if not running): n8n start # 4. In the n8n UI (e.g., http://localhost:5678): # a. Go to 'Credentials' and add a new 'WAHA API' credential. # - Name: MyWahaAPI # - Base URL: http://localhost:3000 (or your WAHA instance URL) # - API Key: YOUR_WAHA_API_KEY (if WAHA is configured with one) # b. Create a new workflow. Drag and drop: # - 'WAHA Trigger' node: Configure it to listen for 'message' events. # - Webhook URL: Copy the URL provided by the node after saving the workflow and configure your WAHA session to send events to this URL. # - Session: 'default' (or your WAHA session name) # - 'Set' node (to extract message text): # - Mode: 'Merge Data' # - Keep Only Set: true # - Add Field: # - Name: 'text' # - Value: `{{$json.body.message.text.body}}` # - 'WAHA' (action) node (to send a reply): # - Credential: 'MyWahaAPI' # - Operation: 'Send Text' # - Chat ID: `{{$json.body.message.chatId}}` (to reply to the sender) # - Text: `Echo: {{$json.text}}` # - Session: 'default' # This workflow sets up an 'echo' bot: any message received by WAHA will be echoed back to the sender via n8n.

Debug

Known issues

gotchaThe WAHA API, which this node connects to, utilizes unofficial WhatsApp Web sessions. This carries a risk of WhatsApp account restrictions or bans if used irresponsibly or if WhatsApp changes its policies.

fix

Adhere strictly to WhatsApp's terms of service and best practices to minimize risk. Use the API responsibly and be aware of potential changes.

affects: >=2024.9.1

gotchaOperating WAHA requires a separate, self-hosted instance of the WAHA application to be running and accessible to your n8n instance. This incurs infrastructure and maintenance overhead, even though WAHA Core is open-source.

fix

Ensure a WAHA instance is properly installed, configured, and running before attempting to use the n8n nodes. Monitor its health and accessibility.

affects: >=2024.9.1

gotchaPublicly exposing an unsecured WAHA instance can lead to security vulnerabilities and abuse, as reported by the community.

fix

Implement robust security measures for your WAHA instance, including strong authentication, network firewalls, and restricting public access where possible.

affects: >=2024.9.1

gotchaDue to the nodes being generated from the WAHA OpenAPI specification, breaking changes in the underlying WAHA API might lead to unexpected behavior or require node updates, especially during major WAHA version upgrades.

fix

Regularly update the `@devlikeapro/n8n-nodes-waha` package. Consult WAHA and n8n-nodes-waha release notes for compatibility information before upgrading WAHA.

affects: >=2024.9.1

gotchaWhen configuring WAHA API credentials in n8n, a known issue might prevent saving if the API Key field is left empty, even if your WAHA instance doesn't require one.

fix

If encountering this, input any placeholder string (e.g., 'none') into the API Key field to allow saving the credential, if your WAHA instance truly does not require an API key.

affects: >=2024.9.1

Errors

Common errors & fixes

Error during the installation of @devlikeapro/n8n-nodes-waha: “Class extends value undefined is not a constructor or null”

This error often indicates an issue with n8n's environment or a potential conflict during community node installation, possibly related to JavaScript module loading.

fix

Ensure your n8n instance is up-to-date. Try restarting n8n after the installation attempt. If running in Docker, ensure correct volume mounts and permissions. Consider clearing the n8n cache or reinstalling the node.

{ "errorMessage": "The service was not able to process your request", "errorDescription":... } or "Node execution failed"

These errors typically indicate a problem communicating with the external WAHA API, or an issue within the WAHA service itself (e.g., WAHA not running, incorrect API key, WAHA session not active, or a malformed request).

fix

Verify that your WAHA instance is running and accessible from n8n. Check your WAHA API credentials in n8n. Inspect WAHA's own logs for specific error messages. Ensure the WAHA session you're targeting is active and configured correctly.

WAHA nodes (e.g., 'WAHA Trigger', 'WAHA Send Message') do not appear in the n8n node palette after installation.

The community node was not successfully installed or loaded by n8n. This often happens if the `n8n add:community-node` command failed or if n8n wasn't restarted.

fix

Verify the installation command completed without errors. Ensure n8n was restarted after installation. Check n8n's logs for any errors related to loading community nodes. Confirm `n8n-community-node-package` keyword is in package.json.

Upgrade

Version history

2024.11.5latest on npm

Audit

Dependencies

n8nrequiredThis is an n8n community node package and requires an n8n instance to function. n8n is a peer dependency.

WAHA (WhatsApp HTTP API)requiredThe nodes connect to a running WAHA instance; WAHA is a separate self-hosted service, not a JavaScript dependency, but essential for the node's operation.

Agent activity

11 hits · last 30 days

node

OpenAI (training)

Resources

githubhttps://github.com/devlikeapro/n8n-nodes-waha ↗

packagehttps://www.npmjs.com/package/n8n-nodes-waha ↗

homepagehttps://n8n.io ↗