Actions64
- Instance Actions
- Message Actions
- Group Actions
- Chat Actions
- Profile Actions
- Event Actions
- Integration Actions
Overview
This node, named "Evolution API," allows users to interact with the Evolution API service. Specifically, for the "Group" resource and the "Update Group Name" operation, it updates the name of an existing group identified by its Group ID. This is useful in scenarios where group names need to be changed dynamically based on business logic or user input, such as renaming project teams, chat groups, or organizational units within an application.
Practical example: Suppose you have a messaging platform integrated with Evolution API, and you want to rename a group chat when the project name changes. Using this node, you can automate updating the group name without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Name Da Instância | The instance name that identifies which Evolution API instance will perform the update. |
| Group ID | The unique identifier of the group whose name will be updated. |
| Novo Group Name | The new name to assign to the specified group. |
Output
The node outputs a JSON array containing the response from the Evolution API after attempting to update the group name. The exact structure depends on the API's response but typically includes confirmation of the update or details about the updated group.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Evolution API.
- The node expects the base URL
https://doc.evolution-api.com/api-referenceas the API endpoint. - Proper configuration of the API authentication credentials in n8n is necessary.
Troubleshooting
- Operation Not Supported Error: If the node throws an error stating the operation is not supported, verify that the resource is set to "groups-api" and the operation to "update-group-name".
- Invalid Group ID: Providing an incorrect or non-existent Group ID may cause the API to return an error. Ensure the Group ID is valid.
- Authentication Errors: Missing or invalid API credentials will prevent successful requests. Confirm that the API key or token is correctly configured.
- Empty or Invalid Input Fields: All three properties are required; missing any will likely cause the node to fail. Double-check that all required fields are filled.
Links and References
- Evolution API Documentation (base URL used by the node)
- n8n Documentation on Creating Custom Nodes