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 send audio messages via WhatsApp. It allows users to send audio media files to specified phone numbers using either URLs or base64-encoded data. This is useful for automating voice message delivery in customer support, marketing campaigns, notifications, or any scenario where sending audio content through WhatsApp is beneficial.

For example, a business could use this node to automatically send recorded voice reminders or promotional audio clips to customers.

Properties

Name Meaning
Phone Number The recipient's WhatsApp number including country code (e.g., 5511999999999).
Media URL The URL or base64 string of the audio file to be sent.
Additional Fields Optional extra parameters:
• Reply to Message ID: ID of a message to reply to.
• Delay (seconds): Delay before sending the message.
• Disable Link Preview: Whether to disable link previews.
• Mention Users: Comma-separated phone numbers to mention in the message.

Output

The node outputs a JSON object containing the response from the WhatsApp API after attempting to send the audio message. This typically includes status information about the message delivery.

No binary data output is produced by this operation.

Example output structure (simplified):

{
  "status": "success",
  "messageId": "abc123",
  "details": { ... }
}

Dependencies

  • Requires an API key credential and authentication token for the WhatsApp API service.
  • Needs configuration of instance ID and API base URL as part of credentials.
  • The node sends requests through a proxy endpoint provided by the integration service.
  • Network access to the media URL must be available if using external URLs.

Troubleshooting

  • Common issues:

    • Invalid or missing phone number format can cause message sending failures.
    • Incorrect or inaccessible media URL/base64 data will result in errors.
    • API authentication failures due to invalid or expired tokens.
    • Delays in message delivery if a delay parameter is set.

  • Error messages:

    • Errors returned from the API are passed through in the output JSON under an error field if the node is configured to continue on failure.
    • Common error hints include authorization errors, invalid media format, or unsupported media types.

  • Resolutions:

    • Verify phone number formatting with country code.
    • Ensure media URL is accessible and points to a valid audio file.
    • Check API credentials and renew tokens if necessary.
    • Use the delay option carefully to avoid unintended message timing.

Links and References

Discussion