Actions64
- Instancia Actions
- Mensagem Actions
- Grupo Actions
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
Overview
The "Desconectar Instância" operation for the "Instancia" resource in this custom n8n node allows users to disconnect (log out) a specific instance from the Evolution API. This is useful in scenarios where you need to remotely terminate or reset an active session for a given instance, such as managing user access, performing maintenance, or troubleshooting connectivity issues.
Practical Example:
If you have multiple instances connected to the Evolution API and need to forcefully log out one (e.g., due to security concerns or to refresh its state), you can use this operation by specifying the instance's name.
Properties
| Display Name | Type | Description |
|---|---|---|
| Nome Da Insticância | String | Digite o nome da instância que deseja pesquisar (Required). |
- Nome Da Insticância: Enter the name of the instance you wish to disconnect. This field is required.
Output
The output will be a JSON object (or array of objects) containing the result of the logout operation. The exact structure depends on the response from the Evolution API, but typically it may include fields such as:
[
{
"success": true,
"message": "Instance disconnected successfully",
"instanceName": "example-instance"
}
]
success: Indicates if the operation was successful.message: Provides additional information about the result.instanceName: The name of the instance that was disconnected.
Note: The actual output fields may vary depending on the Evolution API's response.
Dependencies
- External Service: Requires access to the Evolution API.
- API Key/Credentials: You must configure valid credentials for the "evolutionApi" in n8n.
- n8n Configuration: Ensure the node is properly configured with the correct base URL and authentication details.
Troubleshooting
Common Issues:
- Invalid Instance Name: If the provided instance name does not exist, the API may return an error indicating the instance was not found.
- Missing Credentials: If the required credentials are not set up in n8n, the node will fail to authenticate with the Evolution API.
- Unsupported Operation: If the operation or resource is not supported, you may see an error like:
Resolution: Double-check that you selected the correct resource and operation.Operação não suportada. A função "logout-instance" para o recurso "instances-api" não é suportada!
Error Messages:
"Operação não suportada."— The selected operation/resource combination is not implemented.- Authentication errors — Check your API credentials and permissions.