Actions64
- Instancia Actions
- Mensagem Actions
- Grupo Actions
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
Overview
This node, named "Evolution API," allows users to interact with the Evolution API service. Specifically, for the resource "Instancia" and operation "Deletar Instancia," it enables deleting an instance by specifying its name. This is useful in scenarios where you need to programmatically remove instances from the Evolution API system, such as cleaning up unused or obsolete instances.
Practical example: If you manage multiple instances within the Evolution API platform and want to automate the deletion of a specific instance based on its name, this node can be integrated into your workflow to perform that action without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Nome Da Instancia | The name of the instance to be deleted. This is a required string input. |
Output
The node outputs a JSON array containing the result of the delete operation. The exact structure depends on the Evolution 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 in n8n is necessary.
Troubleshooting
- Operation not supported error: If you select an unsupported operation or resource, the node throws an error stating the operation is not supported. Ensure you use the correct resource ("instances-api") and operation ("delete-instance").
- Missing or incorrect instance name: Since the instance name is required, leaving it empty or providing an incorrect name may cause the API call to fail. Verify the instance name before running the node.
- Authentication errors: If the API key credential is missing or invalid, requests will fail. Confirm that the API key is correctly configured in n8n.
- API endpoint issues: Network problems or changes in the Evolution API endpoint could cause failures. Check connectivity and API documentation for updates.
Links and References
- Evolution API Documentation (base URL used by the node)