Actions64
- Instance Actions
- Message Actions
- Group Actions
- Integration Actions
- Chat Actions
- Profile Actions
- Event Actions
Overview
The node "Evolution API" allows interaction with the Evolution API service. Specifically, for the Group resource and the Update Group Description operation, it updates the description of a specified group within an instance. This is useful in scenarios where group metadata needs to be kept current or modified programmatically, such as updating team descriptions in collaboration platforms or managing group information dynamically.
Practical example: Automatically update the description of a project group when project details change, ensuring all members see the latest information without manual edits.
Properties
| Name | Meaning |
|---|---|
| Instance Name | The name of the instance that will perform the update on the group's description. |
| Group ID | The unique identifier of the group whose description is to be updated. |
| New Description | The new text that will replace the current description of the group. |
Output
The node outputs a JSON array containing the result of the update operation. The exact structure depends on the Evolution API's response but typically includes confirmation of the update or the updated group data. There is no indication that binary data is output by this node.
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 credential in n8n is necessary for successful execution.
Troubleshooting
- Operation not supported error: If you select an unsupported operation or resource, the node throws an error indicating the function is not supported. Ensure the resource and operation names are correct.
- 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 set up.
- Invalid Group ID: Providing an incorrect or non-existent group ID may cause the API to return an error. Double-check the group ID before running the node.
- Empty or invalid description: The new description must be a valid string; otherwise, the API might reject the request.
Links and References
- Evolution API Documentation (base URL used by the node)
- Refer to your Evolution API provider’s documentation for detailed information on group management endpoints and authentication setup.