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 by performing various operations on different resources. Specifically, for the resource "Instancia" and operation "Conectar Instancia," it enables connecting to a particular instance by its name. This is useful in scenarios where you need to programmatically manage or query instances within the Evolution system, such as automating instance connections or integrating instance data into workflows.
Practical example: You might use this node to connect to a specific instance by providing its name, then proceed to retrieve or manipulate data related to that instance in subsequent workflow steps.
Properties
| Name | Meaning |
|---|---|
| Nome Da Instância | The name of the instance you want to connect to. This is a required string input. |
Output
The node outputs a JSON array containing the result of the "Conectar Instancia" operation. The exact structure depends on the Evolution API's response when connecting to an instance but generally includes details about the connected instance.
If the node supports binary data output (not evident from the provided code), it would typically represent files or media related to the instance connection, but no such indication is present here.
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 or external services are explicitly required beyond the API authentication.
Troubleshooting
- Operation not supported error: If you receive an error stating the operation is not supported, ensure that the resource is set to "Instancia" and the operation to "Conectar Instancia." This error occurs if the combination is invalid or not implemented.
- Missing or invalid instance name: Since the instance name is required, leaving it empty or incorrect will likely cause the API call to fail. Verify the instance name before execution.
- Authentication errors: Ensure the API key credential is correctly configured and has sufficient permissions to perform the connection operation.
- API connectivity issues: Network problems or incorrect API endpoint configurations can cause failures. Check your network and API settings.
Links and References
- Evolution API Documentation (Replace with actual URL)
- n8n Documentation on Creating Custom Nodes