Actions37
- Instance Actions
- Message Actions
- Group Actions
- Contact Actions
- Chat Actions
- Campaign Actions
- Chatbot Actions
Overview
This node integrates with the UazAPI service, which provides extensive WhatsApp automation capabilities through more than 90 endpoints. Specifically, for the Instance - Delete operation, the node deletes a specified WhatsApp instance managed by UazAPI.
Typical use cases include:
- Removing an obsolete or no longer needed WhatsApp instance from your automation setup.
- Cleaning up instances that are no longer active or required to maintain an organized environment.
- Automating lifecycle management of WhatsApp instances in workflows.
Example scenario: You have multiple WhatsApp instances for different departments and want to programmatically delete one when it is decommissioned.
Properties
| Name | Meaning |
|---|---|
| Instance Name | Unique name of the WhatsApp instance to delete |
The property "Instance Name" is a required string input representing the unique identifier of the WhatsApp instance you want to delete.
Output
The node outputs a JSON object containing the response from the UazAPI after attempting to delete the instance. This typically includes status information about the deletion request, such as success confirmation or error details.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the UazAPI service.
- The base URL for the UazAPI must be configured in the credentials.
- The node uses HTTP requests authenticated via the provided API key to communicate with UazAPI endpoints.
Troubleshooting
Common issues:
- Incorrect or missing instance name will cause the deletion to fail.
- Invalid or expired API credentials will result in authentication errors.
- Network connectivity problems can prevent successful communication with UazAPI.
Error messages:
- Authentication errors: Check that the API key credential is correctly set and valid.
- Instance not found: Verify the instance name exists and is spelled correctly.
- HTTP errors (e.g., 404, 500): Inspect the UazAPI service status and logs for more details.
Resolution tips:
- Ensure the "Instance Name" property matches exactly the instance registered in UazAPI.
- Confirm API credentials are current and have necessary permissions.
- Test connectivity to the UazAPI base URL outside n8n if needed.
Links and References
- UazAPI Documentation (Replace with actual link if available)
- WhatsApp Automation Concepts
- n8n HTTP Request Node Documentation