Actions64
- Instance Actions
- Message Actions
- Group Actions
- Chat Actions
- Profile Actions
- Event Actions
- Integration Actions
Overview
This node interacts with the Evolution API, specifically supporting operations on various resources. For the Group resource and the Temporary Messages operation, it allows users to configure ephemeral (temporary) message settings in a group chat by toggling message expiration times. This is useful for managing message retention policies in group conversations, such as automatically deleting messages after a set period.
Practical examples include:
- Setting a group’s messages to disappear after 24 hours to enhance privacy.
- Disabling ephemeral messages to keep all messages permanently.
- Configuring longer expiration times like 7 or 90 days depending on organizational needs.
Properties
| Name | Meaning |
|---|---|
| Name Da Instância | The name of the instance to connect to the Evolution API. |
| Group ID | The identifier of the group where temporary message settings will be applied. |
| Expiração | The expiration time for messages in the group. Options: Disabled, 24 Hours, 7 Days, 90 Days |
Output
The node outputs a JSON array containing the result of the toggle ephemeral messages operation. The exact structure depends on the Evolution API response but generally includes confirmation of the updated ephemeral message settings for the specified group.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Evolution API.
- The node uses the base URL
https://doc.evolution-api.com/api-referencefor requests. - Proper configuration of the API authentication credential within n8n is necessary.
Troubleshooting
- Unsupported Operation Error: If the selected operation or resource is not supported, the node throws an error indicating the function is not supported. Ensure that "Group" resource and "Temporary Messages" operation are correctly selected.
- Missing Required Parameters: The node requires the instance name, group ID, and expiration time. Missing any of these will cause errors.
- API Authentication Issues: Invalid or missing API credentials will prevent successful calls.
- Invalid Group ID: Providing an incorrect or non-existent group ID may result in API errors.
To resolve issues:
- Verify all required parameters are provided and valid.
- Check API credentials and permissions.
- Confirm the group ID exists and is accessible.
Links and References
- Evolution API Documentation (base URL used by the node)
- n8n documentation on creating custom nodes