WAHA API icon

WAHA API

Complete WhatsApp automation with WAHA API - Multi-engine support

Overview

The node integrates with the WAHA API to manage WhatsApp chats and perform various chat-related operations. Specifically, the "Unarchive Chat" operation allows users to unarchive a previously archived WhatsApp chat, making it active and visible again in the chat list.

This node is beneficial for automating WhatsApp chat management workflows, such as restoring important conversations that were archived by mistake or as part of a cleanup process. For example, a customer support team could automatically unarchive chats when a customer sends a new message, ensuring no conversation is missed.

Properties

Name Meaning
Session Name The name of the WhatsApp session to use. Defaults to the configured default session.
Chat ID The unique identifier of the WhatsApp chat to unarchive. This can be a phone number with @c.us or a group ID with @g.us.
Additional Fields Optional extra parameters (not specifically used for unarchive but available for other operations).

Output

The node outputs a JSON object representing the response from the WAHA API after attempting to unarchive the specified chat. This typically includes status information about the success or failure of the operation and any relevant metadata returned by the API.

No binary data output is involved in 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 requires proper configuration of the WhatsApp session name to target the correct session.
  • Network access to the WAHA API endpoints is necessary.

Troubleshooting

  • Invalid Credentials: If the API key or session name is incorrect, the node will fail. Verify credentials and session names.
  • Chat ID Format: Ensure the Chat ID is correctly formatted as a phone number with @c.us or a group ID with @g.us.
  • API Validation Errors: The node performs a subscription validation call before executing the main request. Errors like 401 or 403 indicate invalid subscription or API key issues.
  • Unknown Operation or Resource: If the operation or resource is not recognized, the node throws an error. Confirm that "chat" is selected as the resource and "unarchiveChat" as the operation.
  • Network Issues: Connectivity problems to the WAHA API endpoint will cause failures. Check network settings and API availability.

Links and References

Discussion