N8N Tools - Uazapi icon

N8N Tools - Uazapi

Complete Uazapi integration - Premium WhatsApp API with advanced messaging and automation

Actions37

Overview

This node integrates with the Uazapi WhatsApp API to manage WhatsApp messages and related resources. Specifically, the "Message" resource with the "Mark as Read" operation allows users to mark a particular WhatsApp message as read programmatically. This is useful in automation workflows where you want to update message status after processing or responding to messages, ensuring that the message state is synchronized between your system and WhatsApp.

Practical examples include:

  • Automatically marking incoming customer support messages as read once they have been logged or replied to.
  • Marking notification messages as read after sending follow-up actions.
  • Managing message states in bulk workflows to keep track of processed conversations.

Properties

Name Meaning
Additional Fields Optional extra parameters:
• Reply to Message ID (string): ID of message to reply to.
• Delay (seconds) (number): Delay before sending message.
• Disable Link Preview (boolean): Disable link previews in messages.
• Mention Users (string): Phone numbers to mention, comma-separated.

Note: For the "Mark as Read" operation, the node expects the following input properties (not listed in the provided JSON but inferred from code):

  • phoneNumber (string, required): The WhatsApp number with country code.
  • messageId (string, required): The ID of the message to mark as read.

These are essential for identifying which message to mark as read.

Output

The node outputs a JSON object representing the response from the Uazapi service after attempting to mark the message as read. The structure typically includes confirmation of the action or error details if the operation failed.

Example output JSON structure:

{
  "status": "success",
  "message": "Message marked as read",
  "data": {
    "instance": "instance_id",
    "number": "5511999999999",
    "messageId": "abc123"
  }
}

If an error occurs, the output will contain an error field with the error message.

The node does not output binary data for this operation.

Dependencies

  • Requires an active Uazapi WhatsApp API account.
  • Needs credentials including an API key, API token, API URL, and instance ID configured in n8n.
  • The node sends requests through a proxy endpoint at https://n8ntools.io/api/v1/proxy/uazapi using the provided API key credential.
  • Proper network connectivity to the Uazapi service is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing messageId or phoneNumber will cause the API call to fail.
    • Incorrect or expired API credentials will result in authorization errors.
    • Network issues or proxy misconfiguration can prevent successful API calls.

  • Error messages:

    • "Unauthorized" or "Invalid API key": Check that the API key and token are correctly set and valid.
    • "Message not found": Verify the messageId corresponds to an existing message for the given phone number.
    • "Instance not found": Confirm the instance ID is correct and active.

  • Resolution tips:

    • Double-check all required input fields are provided and correctly formatted.
    • Ensure credentials are up-to-date and have sufficient permissions.
    • Test connectivity to the Uazapi API outside n8n to isolate network issues.

Links and References

Discussion