WAHA API icon

WAHA API

Complete WhatsApp automation with WAHA API - Multi-engine support
Join our community

Actions55

Overview

This node integrates with the WAHA API to manage WhatsApp automation tasks. Specifically, for the Webhook resource and Set Webhook operation, it allows users to configure a webhook URL on a specified WhatsApp session. This webhook URL will receive real-time event notifications such as incoming messages, message reactions, session status changes, and group participant updates.

Practical scenarios include:

  • Automatically processing incoming WhatsApp messages by forwarding them to your backend via webhook.
  • Tracking session status or group participant changes in real time.
  • Integrating WhatsApp events into other systems like CRMs, helpdesks, or analytics platforms.

Properties

Name Meaning
Session Name The name of the WhatsApp session where the webhook will be set. Defaults to the credential's default session.
Webhook URL The URL endpoint that will receive WhatsApp event notifications from this session.
Additional Fields Optional extra parameters (not used directly in Set Webhook operation).

Output

The node outputs a JSON object representing the response from the WAHA API after setting the webhook configuration. This typically includes confirmation details about the webhook URL and the events subscribed to.

Example output structure:

{
  "url": "https://your-webhook-url.com",
  "events": [
    "message",
    "message.reaction",
    "session.status",
    "group.participant"
  ]
}

No binary data is output by this operation.

Dependencies

  • Requires an active WAHA API credential with a valid base URL and API key.
  • Optionally uses an additional API key credential for subscription validation via the n8n Tools API.
  • The node makes HTTP requests to the WAHA API endpoints.
  • The user must provide a reachable webhook URL to receive events.

Troubleshooting

  • Invalid Credentials: If the WAHA API key or base URL is incorrect, the node will fail to authenticate. Verify credentials in n8n settings.
  • Subscription Validation Failed: The node validates the subscription via an external API. Errors like 401 or 403 indicate invalid or expired subscription/API key for that service.
  • Webhook URL Not Reachable: Ensure the webhook URL is publicly accessible and can accept POST requests.
  • Unknown Operation or Resource: Using unsupported operations or resources will throw errors. Confirm you are using "Webhook" resource and "Set Webhook" operation.
  • API Rate Limits or Downtime: Temporary failures may occur if the WAHA API is down or rate limits are exceeded.

Links and References

Discussion