WAHA API icon

WAHA API

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

Actions55

Overview

The "Get Webhook" operation of the WAHA API node retrieves the current webhook configuration for a specified WhatsApp session. This allows users to view which webhook URL is set to receive events such as messages, reactions, session status updates, and group participant changes.

This operation is useful when you want to verify or audit the webhook settings of your WhatsApp automation setup, ensuring that event notifications are being sent to the correct endpoint.

Practical example:
You have configured a webhook URL to receive incoming WhatsApp messages and session events. Before troubleshooting or updating your integration, you use this operation to confirm the currently active webhook URL and its associated event subscriptions.

Properties

Name Meaning
Session Name The name of the WhatsApp session from which to retrieve the webhook configuration.
Additional Fields (Not used in this operation)

Output

The output JSON contains the webhook configuration details for the specified WhatsApp session. It typically includes:

  • The webhook URL currently set to receive events.
  • The list of subscribed event types (e.g., message, message reaction, session status, group participant).

Example output structure:

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

This information helps you understand where and what kind of WhatsApp events are being forwarded by the WAHA API.

Dependencies

  • Requires an active WAHA API credential with a valid base URL and API key.
  • Requires a valid WhatsApp session name configured in the credentials or provided explicitly.
  • Optionally uses an additional API validation service requiring its own API key and URL (referred to generically as an API validation step).
  • The node makes HTTP requests to the WAHA API endpoints.

Troubleshooting

  • Invalid subscription or API key error: If the node throws an error about invalid subscription or API key, verify that both the WAHA API credentials and the optional API validation credentials are correctly set up and active.
  • Unknown webhook operation error: This indicates a misconfiguration or unsupported operation; ensure the operation is set exactly to "Get Webhook".
  • Session not found or invalid session name: Confirm that the session name provided exists and is active in your WAHA API environment.
  • Network or connectivity issues: Ensure the WAHA API base URL is reachable from your n8n instance.

Links and References

Discussion