WAHA API icon

WAHA API

Complete WhatsApp automation with WAHA API - Multi-engine support

Overview

This node integrates with the WAHA API to automate WhatsApp chat management and messaging. Specifically, the "Pin Chat" operation allows users to pin a particular chat in their WhatsApp session, making it easier to access important conversations quickly.

Common scenarios where this node is beneficial include:

  • Prioritizing important chats by pinning them for quick access.
  • Automating chat organization in customer support or sales workflows.
  • Managing group or individual chats programmatically within larger automation processes.

For example, a user can automatically pin a VIP customer's chat when a new message arrives, ensuring the conversation stays at the top of their chat list.

Properties

Name Meaning
Session Name The name of the WhatsApp session to use (defaults to the credential's default session).
Chat ID The unique identifier of the WhatsApp chat to pin (e.g., phone number with @c.us or group ID).
Additional Fields Optional extra parameters; for pinning chat, no specific additional fields are required.

Output

The node outputs a JSON object representing the response from the WAHA API after attempting to pin the specified chat. This typically includes confirmation of the action or details about the pinned chat.

No binary data output is involved in this operation.

Example output structure (simplified):

{
  "success": true,
  "message": "Chat pinned successfully",
  "chatId": "5511999999999@c.us"
}

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 requires proper configuration of these credentials in n8n before use.

Troubleshooting

  • Invalid Credentials: If the WAHA API key or session name is incorrect, the node will fail. Verify that the API key and session exist and are active.
  • Chat ID Format: Ensure the Chat ID is correctly formatted as a phone number with @c.us suffix or a valid group ID.
  • API Validation Errors: The node performs a validation call to the N8N Tools API. Errors like "Invalid subscription or API key" indicate issues with the secondary API key credential.
  • Unknown Operation or Resource: If the operation or resource is misspelled or unsupported, the node throws an error indicating the unknown operation/resource.
  • Network Issues: Connectivity problems to the WAHA API endpoint will cause request failures. Check network access and API availability.

Links and References


If you need further details on other operations or resources, feel free to ask!

Discussion