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, providing a comprehensive set of operations to manage WhatsApp messaging, media, contacts, groups, instance settings, and webhooks. Specifically, the Instance - Get QR Code operation retrieves the QR code needed to connect or authenticate a WhatsApp instance.

Use cases for the Get QR Code operation include:

  • Automating the retrieval of the WhatsApp connection QR code during initial setup or re-authentication.
  • Integrating WhatsApp instance management into workflows that require dynamic connection handling.
  • Monitoring or triggering actions based on the availability of the QR code for user scanning.

Example scenario: A workflow automatically fetches the current WhatsApp instance QR code and sends it via email or stores it in a database for an administrator to scan and connect the WhatsApp session.

Properties

Name Meaning
Additional Fields Optional extra parameters to customize the request. Includes:
- Reply to Message ID: ID of message to reply to
- Delay (seconds): Delay before sending message
- Disable Link Preview: Whether to disable link previews in messages
- Mention Users: Comma-separated phone numbers to mention

Note: For the Instance - Get QR Code operation, no additional specific input properties are required beyond selecting the resource and operation.

Output

The node outputs a JSON object containing the response from the Uazapi API endpoint /v1/instance/qr. This typically includes data representing the QR code for connecting the WhatsApp instance. The exact structure depends on the API but generally contains:

  • The QR code image or data string (e.g., base64 or URL).
  • Metadata about the instance or QR code status.

No binary data output is indicated for this operation.

Dependencies

  • Requires an active Uazapi API credential with:

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

  • The node makes authenticated HTTP requests to the Uazapi service endpoints.

  • n8n configuration must include these credentials properly set up to authorize API calls.

Troubleshooting

  • Common issues:

    • Invalid or expired API token or instance ID may cause authentication failures.
    • Network connectivity problems can prevent reaching the Uazapi API.
    • Incorrectly configured credentials will result in authorization errors.

  • Error messages:

    • Errors returned by the API will be included in the node output if "Continue On Fail" is enabled.
    • Typical error messages might indicate invalid credentials, missing instance ID, or rate limiting.

  • Resolution tips:

    • Verify that the API key, token, and instance ID are correct and active.
    • Ensure network access to the Uazapi API endpoint.
    • Check API usage limits and quotas.

Links and References

Discussion