N8N Tools - Uazapi icon

N8N Tools - Uazapi

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

Actions37

Overview

This node integrates with a premium WhatsApp API service to perform various operations related to WhatsApp contacts, messages, media, groups, instance management, and webhooks. Specifically, for the Contact resource with the Check Number operation, it checks whether a given phone number is registered on WhatsApp.

This functionality is useful in scenarios where you want to verify if a phone number is active on WhatsApp before attempting to send messages or add contacts. For example, businesses can use this to validate customer numbers before launching marketing campaigns or automating customer support workflows.

Properties

Name Meaning
Phone Number The WhatsApp phone number to check, including country code (e.g., 5511999999999).
Additional Fields Optional extra parameters:
- Reply to Message ID: ID of message to reply to
- Delay (seconds): Wait time before sending
- Disable Link Preview: Whether to disable link previews
- Mention Users: Comma-separated phone numbers to mention

Output

The output JSON contains the response from the WhatsApp API indicating the status of the checked phone number. Typically, it will include information such as whether the number exists on WhatsApp and possibly additional metadata about the contact.

No binary data is output by this operation.

Example output structure (simplified):

{
  "exists": true,
  "number": "5511999999999",
  "status": "valid"
}

Dependencies

  • Requires an API key credential and authentication token for the WhatsApp API service.
  • Needs configuration of the API base URL and instance identifier.
  • The node sends requests through a proxy endpoint provided by the integration service.
  • Proper network access to the WhatsApp API endpoints is necessary.

Troubleshooting

  • Common Issues:

    • Invalid or missing phone number format: Ensure the phone number includes the country code without spaces or special characters.
    • Authentication errors: Verify that the API key and token credentials are correctly configured and valid.
    • Network connectivity problems: Confirm that the n8n instance can reach the external API endpoints.

  • Error Messages:

    • "Unknown resource": Occurs if the resource parameter is incorrect; ensure "contact" is selected.
    • API authorization failures: Check API keys and tokens.
    • Rate limiting or quota exceeded: May require upgrading the API plan or adjusting request frequency.

Links and References

Discussion