UazapiGo Unofficial

Overview

This node integrates with the unofficial uazapiGO API, enabling users to manage WhatsApp instances and send messages programmatically. It supports a variety of administrative tasks such as creating and listing WhatsApp instances, updating instance metadata, managing webhooks, and controlling privacy settings. Additionally, it allows sending text and media messages to contacts or groups.

Common scenarios where this node is beneficial include automating WhatsApp messaging workflows, managing multiple WhatsApp instances centrally, setting up event-driven integrations via webhooks, and customizing privacy configurations for WhatsApp instances.

Practical examples:

• Automatically sending notifications or alerts to WhatsApp contacts.
• Creating and configuring new WhatsApp instances dynamically.
• Setting up webhooks to listen for incoming WhatsApp events like messages or connection status changes.
• Updating profile information or privacy settings of WhatsApp instances through automation.

Properties

Since the Resource and Operation are both "Default" in your request, only the "Url" property applies here based on the provided JSON.

Output

The node outputs an array of JSON objects corresponding to each input item processed. Each output object contains the raw JSON response from the uazapiGO API for the requested operation.

• The structure of the JSON depends on the specific API endpoint called and the operation performed.
• No binary data output is produced by this node.

Example output snippet (generic):

[
  {
    "json": {
      "status": "success",
      "data": { /* operation-specific data */ }
    }
  }
]

Dependencies

• Requires access to the uazapiGO API endpoint specified by the "Url" property.
• For administrative operations, an API key credential (admin token) must be configured in n8n credentials and will be used automatically.
• For other operations, an authentication token specific to the WhatsApp instance must be provided as a parameter.
• The node uses standard HTTP requests with JSON payloads.

Troubleshooting

• Missing Credentials Error: If performing admin operations without configured admin API credentials, the node throws an error indicating missing admin credentials. To fix, configure the required API key credential in n8n.
• Invalid Token or Authentication Failure: Operations requiring instance tokens may fail if the token is invalid or expired. Ensure the correct token is provided.
• Incorrect URL Format: The base URL should start with https://. The node normalizes the URL but providing an incorrect or unreachable URL will cause request failures.
• Empty Required Parameters: Some operations require mandatory parameters (e.g., instance ID, phone number). Omitting these will result in errors.
• API Errors: The node returns API error messages in the output JSON under an error field if the request fails. Review the API documentation for error codes and meanings.

Links and References

• uazapiGO Official API Documentation (assumed public API docs)
• n8n HTTP Request Node Documentation (for understanding underlying HTTP calls): https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/

If you want details about specific resources or operations, please provide their names so I can extract targeted information.