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 provide comprehensive WhatsApp automation capabilities. It supports multiple resources such as sessions, messages, chats, contacts, groups, webhooks, and status checks. Specifically, for the Status resource with the Get Version operation, the node retrieves the current version of the WAHA system.

Common scenarios where this node is beneficial include:

  • Monitoring the WAHA API system version to ensure compatibility.
  • Automating WhatsApp messaging workflows including sending texts, media, managing groups, and contacts.
  • Managing WhatsApp sessions programmatically.
  • Setting up and retrieving webhook configurations for event-driven automation.

Practical example for the Status > Get Version operation:

  • Use this node to periodically check the WAHA API version to trigger alerts or updates if a new version is available.

Properties

Name Meaning
Additional Fields Optional extra parameters depending on the operation; includes:
- Filename: Custom filename for media files
- Mimetype: MIME type of the file
- Link Description: Description for link preview
- Link Title: Title for link preview
- Contact Name: Name for contact vCard
- Contact Number: Phone number for contact vCard
- Reaction: Emoji reaction to send (default 👍)
- Limit: Limit number of results (default 100)
- Download Media: Boolean to download media files in messages (default false)

Note: For the Status > Get Version operation, no additional fields are required.

Output

The node outputs a JSON object containing the response from the WAHA API for the requested operation.

For the Status > Get Version operation, the output JSON will contain the WAHA system version information, typically including version number and related metadata.

If the node operation involves media (not applicable here), it can also handle binary data representing media files.

Example output structure for Get Version might look like:

{
  "version": "1.2.3",
  "buildDate": "2024-01-15T12:00:00Z",
  "commitHash": "abc123def"
}

Dependencies

  • Requires an active WAHA API credential with a valid base URL and API key.
  • Optionally uses an additional API key credential for validating subscription via the n8n Tools API.
  • The node makes HTTP requests to the WAHA API endpoints.
  • Proper configuration of credentials in n8n is necessary for authentication.

Troubleshooting

  • Invalid subscription or API key error:
    If the node throws errors indicating invalid subscription or API key, verify that the WAHA API credentials and the optional n8n Tools API credentials are correctly set and active.

  • Unknown resource or operation error:
    This occurs if an unsupported resource or operation name is used. Ensure the Resource is set to "Status" and Operation to "Get Version" for this use case.

  • Network or request failures:
    Check network connectivity and that the WAHA API base URL is reachable. Also confirm that the API key has sufficient permissions.

  • Continue On Fail behavior:
    If enabled, the node will return error details in the output JSON instead of stopping execution on failure.

Links and References

Discussion