Evolution API

Overview

This node allows you to delete an instance from the Evolution API by specifying its name. It is useful in scenarios where you need to programmatically remove or decommission instances managed by the Evolution platform, such as cleaning up unused resources or automating lifecycle management.

Practical Example:
You might use this node in a workflow that automatically deletes test or temporary instances after a certain period, or as part of a cleanup process triggered by specific business logic.

Properties

Output

The output will be a JSON object (or array of objects) representing the result of the deletion operation. The structure typically includes information about the success or failure of the request, and may contain details such as status messages or error codes, depending on the Evolution API's response.

Dependencies

• External Service: Requires access to the Evolution API.
• API Key/Credentials: You must configure valid Evolution API credentials in n8n under the name evolutionApi.
• n8n Configuration: No additional configuration is needed beyond setting up the credentials.

Troubleshooting

• Common Issues:

  • Invalid Instance Name: If the provided instance name does not exist, the API may return an error indicating that the resource was not found.
  • Missing Credentials: If the Evolution API credentials are not configured, the node will fail to authenticate.
  • Unsupported Operation: If the operation or resource is not supported, you may see an error message like "Operação não suportada."

• Error Messages:

  • "Operação não suportada."
    Resolution: Ensure you have selected the correct resource ("Instancia") and operation ("Deletar Instancia").
  • API-specific errors (e.g., authentication failures, permission denied, etc.)
    Resolution: Check your API credentials and permissions.

Links and References

• Evolution API Documentation
• n8n Documentation: Custom Nodes