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 contacts and perform various messaging-related operations. Specifically, the "Unblock Contact" operation allows users to unblock a previously blocked WhatsApp contact by providing their phone number.

Common scenarios for this node include:

  • Unblocking a contact who was mistakenly blocked.
  • Automating contact management workflows where contacts need to be unblocked based on certain triggers or conditions.
  • Integrating WhatsApp contact status changes into broader CRM or customer support systems.

For example, a user might automate unblocking customers who have resolved disputes or reactivated their accounts, ensuring they can receive messages again.

Properties

Name Meaning
Phone Number The WhatsApp phone number of the contact to unblock, including country code (e.g., 5511999999999).
Additional Fields Optional extra parameters that can be set when unblocking, including:
- Reply to Message ID: ID of a message to reply to (not typically used in unblock).
- Delay (seconds): Delay before sending the unblock request.
- Disable Link Preview: Whether to disable link previews in messages (not relevant here).
- Mention Users: Comma-separated phone numbers to mention (not relevant here).

Note: For the "Unblock Contact" operation, only the "Phone Number" is strictly required; additional fields are generally not applicable but available due to shared property structure.

Output

The node outputs a JSON object representing the response from the Uazapi API after attempting to unblock the contact. This typically includes confirmation of the unblock action or error details if the operation failed.

Example output structure (simplified):

{
  "status": "success",
  "message": "Contact unblocked successfully",
  "data": {
    "number": "5511999999999"
  }
}

If an error occurs, the output JSON will contain an error field describing the issue.

The node does not output binary data.

Dependencies

  • Requires an active Uazapi WhatsApp API account.
  • Needs credentials configured in n8n containing:
    • An API key credential for authenticating requests.
    • API URL endpoint.
    • API token for authorization.
    • Instance ID identifying the WhatsApp instance.
  • The node sends HTTP requests via a proxy service hosted at https://n8ntools.io/api/v1/proxy/uazapi.

Troubleshooting

  • Common issues:

    • Invalid or missing phone number format: Ensure the phone number includes the country code without spaces or symbols.
    • Authentication errors: Verify that the API key, token, and instance ID credentials are correctly set and valid.
    • Network or proxy errors: Check connectivity to the proxy URL and ensure no firewall blocks outgoing requests.
    • Attempting to unblock a contact that is not blocked may return an error or no-op response.

  • Error messages:

    • "Unauthorized" or "Invalid API key": Check API credentials.
    • "Contact not found": Confirm the phone number exists on WhatsApp and is correct.
    • "Instance not found": Validate the instance ID.
    • "Rate limit exceeded": Slow down request frequency or check API usage limits.

Resolving these usually involves verifying input data, credentials, and network access.

Links and References

Discussion