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 retrieve their profile photos. Specifically, the Contact - Get Profile Photo operation fetches the profile picture of a WhatsApp contact by their phone number.

Common scenarios where this node is useful include:

  • Automatically retrieving and displaying contact profile pictures in customer support dashboards.
  • Enriching contact records in CRMs or databases with profile images.
  • Verifying contact identity visually before sending messages.

For example, you can input a WhatsApp phone number (with country code) and get back the URL or data representing that contact's profile photo, which can then be used downstream in your workflow.

Properties

Name Meaning
Phone Number The WhatsApp phone number including country code (e.g., 5511999999999) for the target contact.
Additional Fields Optional extra parameters (not specifically used for this operation but available).

The Additional Fields collection includes options like:

  • Reply to Message ID
  • Delay (seconds)
  • Disable Link Preview
  • Mention Users (comma-separated phone numbers)

These additional fields are generally relevant for messaging operations and do not affect the "Get Profile Photo" operation.

Output

The output JSON contains the response from the Uazapi API endpoint /v1/contacts/photo for the specified phone number. This typically includes:

  • Data representing the contact's profile photo, such as a URL or base64 encoded image.
  • Metadata about the photo if provided by the API.

The exact structure depends on the Uazapi API response but will be accessible under the json property of the output item.

No binary data output is indicated for this operation; the profile photo is returned as part of the JSON response.

Dependencies

  • Requires an active Uazapi WhatsApp API account with valid credentials:

    • An API key credential.
    • API token.
    • Instance ID.
    • API base URL.

  • The node uses these credentials to authenticate requests to the Uazapi service.

  • No additional external dependencies beyond the configured Uazapi API credentials.

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, token, and instance ID are correctly set and have not expired.
    • Contact does not exist or has no profile photo: The API may return empty or error responses if the contact is not found or has no photo.

  • Error messages:

    • Errors from the API will be returned in the node output if "Continue On Fail" is enabled.
    • Typical errors include unauthorized access, invalid parameters, or resource not found.

  • Resolution:

    • Double-check all input parameters.
    • Confirm API credentials and permissions.
    • Handle cases where the profile photo is missing gracefully in your workflow.

Links and References

Discussion