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 automate WhatsApp messaging tasks. Specifically, the "Send Seen" operation marks messages in a specified WhatsApp chat as seen (read). This is useful for workflows where you want to programmatically acknowledge message receipt without sending a textual reply.

Practical scenarios include:

  • Automatically marking incoming messages as read after processing them.
  • Managing customer support chats by confirming message visibility.
  • Synchronizing message status across multiple systems or dashboards.

Properties

Name Meaning
Session Name The name of the WhatsApp session to use. Defaults to a configured default session name.
Chat ID The WhatsApp chat identifier where the "seen" status will be sent. Format: phone number with @c.us or group ID with @g.us.
Additional Fields Optional extra parameters; for "sendSeen" specifically, no additional fields are required or used.

Output

The node outputs a JSON object representing the response from the WAHA API after marking the messages as seen. This typically includes confirmation details such as success status and any metadata returned by the API.

No binary data output is involved in this operation.

Example output structure (simplified):

{
  "success": true,
  "message": "Messages marked as seen",
  "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 WhatsApp session referenced by "Session Name" must be active and connected.
  • Proper configuration of the WAHA API endpoint and authentication is necessary.

Troubleshooting

  • Invalid Credentials: If the node throws errors related to API key validation, verify that both the WAHA API and n8n Tools API credentials are correctly set and active.
  • Session Not Found or Inactive: Ensure the specified WhatsApp session exists and is currently connected.
  • Invalid Chat ID: The chat ID must be correctly formatted (e.g., 5511999999999@c.us). Incorrect IDs will cause failures.
  • API Errors: Network issues or API downtime can cause request failures. Check connectivity and WAHA API status.
  • Permission Issues: The WAHA API user must have permissions to mark messages as seen in the target chat.

Links and References

Discussion