Actions64
- Instance Actions
- Message Actions
- Group Actions
- Integration Actions
- Chat Actions
- Profile Actions
- Event Actions
Overview
The node "Evolution API" allows users to interact with the Evolution API, specifically supporting operations on various resources. For the provided Resource "Instance" and Operation "Set Presence," this node sets the presence status of a specified instance. This is useful in scenarios where you want to programmatically update the availability state of an instance, for example, marking it as "Available" or "Unavailable" based on external triggers or workflows.
Practical examples include:
- Automatically setting an instance's presence to "Unavailable" during maintenance windows.
- Marking an instance as "Available" when it comes back online after downtime.
Properties
| Name | Meaning |
|---|---|
| Instance Name | The name of the instance whose presence status you want to set. |
| Presence | The presence status to assign to the instance. Options: "Available", "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 or relevant metadata about the 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 within n8n credentials is necessary.
Troubleshooting
- Operation not supported error: If the node throws an error stating that the operation is not supported, verify that the resource and operation names are correctly set to "Instance" and "Set Presence" respectively.
- Authentication errors: Ensure that the API key credential is valid and has the necessary permissions to update instance presence.
- Invalid instance name: Providing an incorrect or non-existent instance name may cause the API to reject the request; double-check the instance name input.
- Network issues: Connectivity problems to the Evolution API endpoint will prevent successful execution.
Links and References
- Evolution API Documentation (base URL used by the node)