Actions64
- Mensagem Actions
- Grupo Actions
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
- Instancia Actions
Overview
The Conectar Instância operation of the Instancia resource in this custom n8n node allows users to connect to a specific instance by providing its name. This is useful for workflows that need to interact with or retrieve information from a particular instance managed by the Evolution API. Common scenarios include automating tasks that require connecting to different instances dynamically, such as monitoring, configuration, or data retrieval.
Practical Example
- Automatically connect to an instance named "ProductionServer" to fetch its status or perform further automated actions within your workflow.
Properties
| Display Name | Type | Description |
|---|---|---|
| Nome Da Instância | String | Digite o nome da instância que deseja pesquisar (required). |
- Nome Da Instância: The user must provide the name of the instance they wish to connect to.
Output
- The output will be a JSON array containing the result of the connection attempt to the specified instance.
- The structure of the output JSON depends on the response from the Evolution API for the "Conectar Instância" operation. Typically, it may include fields such as instance details, connection status, or error messages if the connection fails.
Dependencies
- External Service: Requires access to the Evolution API at
https://doc.evolution-api.com/api-reference. - API Key/Credentials: Needs valid credentials configured in n8n under the name
evolutionApi.
Troubleshooting
Common Issues:
- Missing or incorrect instance name will likely result in an error or no data returned.
- Invalid or missing API credentials will prevent the node from connecting to the Evolution API.
- Network issues or incorrect base URL can cause connection failures.
Error Messages:
"Operação não suportada.": This means the selected operation is not supported for the chosen resource. Ensure you have selected the correct resource and operation.- API errors from the Evolution API may be passed through in the output JSON; check the message and description fields for more details.