Actions64
- Instancia Actions
- Mensaje Actions
- Grupo Actions
- Crear Grupo
- Actualizar Imagen Del Grupo
- Actualizar Nombre Del Grupo
- Actualizar Descripción Del Grupo
- Actualizar Configuraciones
- Actualizar Miembros
- Buscar Enlace De Invitación
- Revocar Enlace De Invitación
- Enviar Enlace De Invitación
- Buscar Grupos
- Encontrar Participantes
- Mensajes Temporales
- Unirse Al Grupo
- Salir Del Grupo
- Chat Actions
- Perfil Actions
- Evento Actions
- Integración Actions
Overview
The node "Evolution API" allows interaction with the Evolution API service. Specifically, for the resource Instancia and operation Definir Presencia, 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 state of an instance within the Evolution system, such as marking an instance as available or unavailable based on external triggers or workflows.
Practical examples:
- Automatically mark an instance as "Disponible" (available) when a related service starts.
- Set an instance to "No Disponible" (unavailable) during maintenance windows or outages.
Properties
| Name | Meaning |
|---|---|
| Nombre De La Instancia | The name of the instance whose presence status you want to set. |
| Presencia | The presence status to assign to the instance. Options: "Disponible" (available), "No Disponible" (unavailable). |
Output
The node outputs a JSON array containing the result of the presence update operation. Each item in the output corresponds to the response from the Evolution API after setting the presence status. The exact structure depends on the API response but generally includes confirmation of the updated presence state.
There is no indication that the node outputs binary data.
Dependencies
- Requires an API key credential to authenticate 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 you use the correct resource ("instances-api") and operation ("set-presence").
- Authentication errors: If the API key or credentials are missing or invalid, the node will fail to authenticate. Verify that the API key credential is correctly configured.
- Invalid instance name: Providing an empty or incorrect instance name may cause the API to reject the request. Always provide a valid instance name.
- Network or API errors: Connectivity issues or API downtime can cause failures. Check network connectivity and API status.
Links and References
- Evolution API Documentation (base URL referenced in the node)
- n8n documentation on API Credentials