Actions64
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
- Instancia Actions
- Mensagem Actions
- Grupo Actions
Overview
This node, named "Evolution API," allows users to interact with the Evolution API service. Specifically, for the resource "Instancia" and operation "Definir Presença" (Set Presence), 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 system, such as marking an instance as available or unavailable based on external triggers or workflows.
Practical examples include:
- Automatically setting an instance's presence to "available" when a related service starts.
- Marking an instance as "unavailable" during maintenance windows or error states.
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-setting operation. The exact structure depends on the Evolution API response but generally includes confirmation or status details about the updated presence state of the specified instance.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Evolution API.
- The node expects the Evolution API endpoint to be accessible and properly configured.
- No additional environment variables are explicitly required beyond the API authentication.
Troubleshooting
- Operation not supported error: If the node throws an error stating the operation is not supported, verify that the resource and operation names are correctly set to "instances-api" and "set-presence" respectively.
- Authentication errors: Ensure the API key credential is valid and has sufficient permissions to modify instance presence.
- Invalid instance name: Providing a non-existent or misspelled instance name may cause the API to reject the request or return an error.
- Network issues: Connectivity problems with the Evolution API endpoint will prevent successful execution.
Links and References
- Evolution API official documentation (not provided here; consult your API provider)
- n8n documentation on creating custom nodes and using credentials