Actions64
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
- Instancia Actions
- Mensagem Actions
- Grupo Actions
Overview
This node, named "Evolution API," allows users to interact with the Evolution API by performing various operations on different resources. Specifically, for the resource "Instancia" and operation "Reiniciar Instancia" (Restart Instance), the node enables restarting a specified instance by its name. This is useful in scenarios where an instance needs to be rebooted or refreshed remotely via API calls, such as recovering from errors, applying updates, or resetting state.
Practical example: A user managing multiple instances of a service can automate the restart process of a particular instance by specifying its name, avoiding manual intervention and ensuring smoother maintenance workflows.
Properties
| Name | Meaning |
|---|---|
| Nome Da Insticância | The name of the instance to search for and restart. This is a required string property. |
Output
The node outputs a JSON array containing the response from the Evolution API after attempting to restart the specified instance. The exact structure depends on the API's response but typically includes status information about the restart operation, such as success confirmation or error details.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Evolution API.
- The node expects the Evolution API to be accessible and properly configured.
- No additional environment variables are explicitly required beyond the API authentication setup.
Troubleshooting
Common issues:
- Providing an incorrect or non-existent instance name will likely cause the API to return an error or no results.
- Network connectivity problems may prevent successful communication with the Evolution API.
- Missing or invalid API credentials will result in authentication failures.
Error messages:
"Operação não suportada."indicates that the requested operation is not supported for the given resource. Ensure the resource and operation names are correct.- API errors returned from the Evolution API will be passed through; check the API documentation for specific error codes and resolutions.
Links and References
- Evolution API official documentation (link not provided in source)
- n8n documentation on creating custom nodes and using API credentials