Actions64
- Instancia Actions
- Mensagem Actions
- Grupo Actions
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
Overview
The node "Evolution API" allows interaction with the Evolution API service. Specifically, for the resource Instancia and operation Definir Presença, it sets the presence status of a given instance by its name. This is useful in scenarios where you want to programmatically update or manage the availability status of instances within the Evolution platform, such as marking an instance as available or unavailable.
Practical examples include:
- Automatically setting an instance's presence to "available" when a system comes online.
- Marking an instance as "unavailable" during maintenance windows or outages.
Properties
| Name | Meaning |
|---|---|
| Nome Da Instância | The name of the instance whose presence status you want to set. |
| Presença | The presence status to assign to the instance. Options: "Disponível" (available), "Indisponível" (unavailable). |
Output
The node outputs a JSON array containing the result of the presence update operation. The exact structure depends on the Evolution API response but generally includes confirmation of the updated presence status for the specified instance.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Evolution API.
- The base URL for requests is
https://doc.evolution-api.com/api-reference. - Proper configuration of the API authentication credentials in n8n is necessary.
Troubleshooting
- Operation not supported error: If you select an unsupported operation or resource, the node throws an error indicating the operation is not supported. Ensure that the resource is "instances-api" and the operation is "set-presence".
- Authentication errors: If the API key or credentials are missing or invalid, the node will fail to authenticate. Verify that the correct API key credential is configured.
- Invalid instance name: Providing an incorrect or non-existent instance name may cause the API to return an error or no effect. Double-check the instance name spelling.
- Network issues: Connectivity problems to the Evolution API endpoint can cause request failures. Check network access and proxy settings if applicable.
Links and References
- Evolution API Documentation (base URL used by the node)
- n8n documentation on API Credentials for configuring API keys