Actions64
- Instancia Actions
- Mensagem Actions
- Grupo Actions
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
Overview
This node interacts with the Evolution API to manage proxy settings for instances. It supports two main operations under the "Instancia" resource: setting a proxy configuration and checking the current proxy status. This is useful in scenarios where you need to route instance communications through a proxy server, either enabling or disabling it, or verifying the existing proxy setup.
Practical examples include:
- Enabling a corporate proxy for an instance to comply with network policies.
- Disabling the proxy when direct internet access is required.
- Checking if a proxy is currently configured before performing network operations.
Properties
| Name | Meaning |
|---|---|
| Nome Da Instancia | The name of the instance that will send the message; identifies which instance to configure. |
| O Que Deseja Fazer | Choose between "Definir Proxy" (set proxy) or "Verificar Proxy" (check proxy). |
| Ativar Proxy | Boolean option to enable or disable proxy integration (only for setting proxy). |
| Protocolo Do Proxy | Protocol used by the proxy; options are HTTP or HTTPS (only for setting proxy). |
| Host Do Proxy | The hostname or IP address of the proxy server (only for setting proxy). |
| Porta Do Proxy | The port number on which the proxy server listens (only for setting proxy). |
| Usuário Do Proxy | Username for authenticating with the proxy server (only for setting proxy). |
| Senha Do Proxy | Password for authenticating with the proxy server (only for setting proxy). |
Output
The node outputs a JSON array containing the result of the proxy operation performed:
- For setting the proxy, the output typically confirms success or failure of the configuration change.
- For checking the proxy, the output returns the current proxy settings or status for the specified instance.
No binary data output is involved.
Dependencies
- Requires an API key credential to authenticate with the Evolution API.
- The node expects the Evolution API service to be accessible and properly configured.
- No additional environment variables are explicitly required beyond the API authentication.
Troubleshooting
Common issues:
- Incorrect instance name may cause the API to fail to find the target instance.
- Invalid proxy host, port, username, or password can lead to authentication or connection errors.
- Choosing an unsupported operation or resource combination results in an error.
Error messages:
"Operação não suportada."indicates the selected operation-resource pair is not implemented; verify the chosen operation and resource.- Authentication failures usually stem from invalid or missing API credentials.
- Network errors may occur if the proxy details are incorrect or unreachable.
To resolve these, ensure all input properties are correctly filled, credentials are valid, and the Evolution API endpoint is reachable.
Links and References
- Evolution API official documentation (not provided here; consult your API provider)
- n8n documentation on creating custom nodes and using API credentials