Wuzapi Chat icon

Wuzapi Chat

Perform chat operations with Wuzapi WhatsApp API

Actions6

Overview

This node enables interaction with WhatsApp chats via the Wuzapi WhatsApp API, providing multiple chat-related operations. Specifically, the "Mark as Read" operation allows users to mark one or more messages in a specified chat as read. This is useful for automating message status updates, such as acknowledging receipt of messages without manual intervention.

Practical examples include:

  • Automatically marking incoming messages as read after processing them in a workflow.
  • Managing message states in customer support scenarios to keep track of handled conversations.
  • Synchronizing message read statuses across multiple systems or devices.

Properties

Name Meaning
Message IDs Comma-separated list of message IDs to mark as read (e.g., AABBCC11223344,DDEEFF55667788). Required.
Chat JID The unique identifier (Jabber ID) of the chat containing the messages (e.g., 5491155553934.0:1@s.whatsapp.net). Required.
Sender JID The unique identifier of the message sender (e.g., 5491155553111.0:1@s.whatsapp.net). Optional; used to specify the sender of the messages.

Output

The node outputs JSON data representing the response from the Wuzapi WhatsApp API after marking messages as read. The structure depends on the API's response but generally includes confirmation of the operation's success or details about any errors.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Wuzapi WhatsApp API.
  • Needs an API key credential configured in n8n to authenticate requests to the Wuzapi service.
  • The node uses the /chat/markread endpoint of the Wuzapi API to perform the operation.

Troubleshooting

  • Common Issues:

    • Invalid or incorrectly formatted Message IDs may cause the API request to fail.
    • Incorrect Chat JID or Sender JID values can result in no messages being marked as read.
    • Network or authentication issues with the Wuzapi API will prevent successful execution.

  • Error Messages:

    • Errors returned from the API typically include descriptive messages indicating the problem (e.g., "Invalid message ID", "Unauthorized").
    • If the node throws an error related to missing parameters, ensure all required fields (Message IDs and Chat JID) are correctly set.

  • Resolution Tips:

    • Verify that Message IDs are accurate and correspond to messages in the specified chat.
    • Confirm that the Chat JID matches the target chat where messages reside.
    • Check API credentials and network connectivity.
    • Use the node's "Continue On Fail" option to handle errors gracefully within workflows.

Links and References

Discussion