Actions64
- Instance Actions
- Message Actions
- Group Actions
- Chat Actions
- Profile Actions
- Event Actions
- Integration Actions
Overview
This node, named "Evolution API," allows users to interact with the Evolution API service. Specifically, for the "Instance" resource and the "Delete Instance" operation, it enables deleting a specified instance by its name. This is useful in scenarios where you need to programmatically remove instances from your Evolution API environment, such as cleaning up unused or test instances.
Practical example: If you have multiple instances running and want to automate the removal of a particular instance by name, this node can be configured to delete that instance during an automated workflow.
Properties
Name | Meaning |
---|---|
Instance Name | The name of the instance to be deleted. This is a required string input identifying which instance will be removed. |
Output
The node outputs a JSON array containing the response from the Evolution API after attempting to delete the specified instance. The exact structure depends on the API's response but typically includes confirmation of deletion or error details if the operation failed.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Evolution API.
- The base URL for requests is set to
https://doc.evolution-api.com/api-reference
. - Proper configuration of the API authentication credential within n8n is necessary.
Troubleshooting
Common issues:
- Providing an incorrect or non-existent instance name will likely result in an error from the API indicating the instance could not be found.
- Missing or invalid API credentials will cause authentication failures.
- Network connectivity problems may prevent reaching the Evolution API endpoint.
Error messages:
"Operation not supported."
— This occurs if an unsupported operation or resource is requested; ensure the resource is "instances-api" and operation is "delete-instance".- API errors related to authorization or instance existence will be returned from the API and should be checked in the node’s output.
Links and References
- Evolution API Documentation (base URL used by the node)