Actions64
- Instance Actions
- Message Actions
- Group Actions
- Integration Actions
- Chat Actions
- Profile Actions
- Event Actions
Overview
The node named "Evolution API" provides integration with the Evolution API, allowing users to perform various operations on different resources. Specifically for the Group resource and the Temporary Messages operation, this node enables configuring ephemeral (temporary) message settings within a group chat. This is useful in scenarios where messages should automatically disappear after a certain period, enhancing privacy or reducing clutter.
Practical examples include:
- Setting a group chat so that all messages expire after 24 hours, suitable for sensitive discussions.
- Disabling temporary messages to keep chat history indefinitely.
- Configuring expiration times like 7 days or 90 days depending on organizational policies.
Properties
| Name | Meaning |
|---|---|
| Instance Name | The name of the Evolution API instance to connect to. |
| Group ID | The unique identifier of the group whose temporary message settings you want to modify. |
| Expiration | The duration after which messages expire. Options: Disabled (0), 24 Hours, 7 Days, 90 Days |
Output
The node outputs a JSON array containing the result of the temporary message configuration operation. The exact structure depends on the Evolution API response but generally includes confirmation of the updated ephemeral message setting for the specified group.
No binary data output is indicated.
Dependencies
- Requires an active connection to the Evolution API service.
- Needs an API authentication credential configured in n8n to authorize requests.
- The base URL for API requests is set to
https://doc.evolution-api.com/api-reference.
Troubleshooting
- Operation not supported error: If the selected resource-operation combination is not implemented, the node throws an error stating the function is unsupported. Ensure the correct resource and operation names are used.
- Authentication errors: Missing or invalid API credentials will cause request failures. Verify that the API key or token is correctly configured.
- Invalid Group ID: Providing an incorrect or non-existent group identifier may lead to API errors. Double-check the group ID format and existence.
- Expiration value issues: Only the predefined expiration options are valid; using unsupported values might cause errors.
Links and References
- Evolution API Documentation (official API reference)
- n8n documentation on Creating Custom Nodes