Actions64
- Instancia Actions
- Mensagem Actions
- Grupo Actions
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
Overview
This node allows users to update the description of a specific group within the Evolution API system. It is designed for scenarios where administrators or automated workflows need to programmatically change group descriptions, such as updating group info after organizational changes or automating group metadata management.
Practical examples include:
- Automatically updating group descriptions based on external data sources.
- Managing multiple groups' metadata in bulk via automation.
- Keeping group information current without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Server URL | The full URL of your Evolution API server (e.g., https://api.exemplo.com). |
| API Key | The API key credential required to authenticate requests to the Evolution API instance. |
| Nome Da Instância | The name of the specific Evolution API instance where the group description will be updated. |
| ID Do Grupo | The unique identifier (JID) of the group whose description you want to update. |
| Nova Descrição | The new description text that will be set for the specified group. |
Output
The node outputs a JSON array containing the response from the Evolution API after attempting to update the group's description. This typically includes confirmation details or the updated group object reflecting the new description.
No binary data output is involved.
Dependencies
- Requires access to an Evolution API endpoint.
- Needs a valid API key credential with permissions to update group information.
- The user must provide the correct server URL and instance name corresponding to their Evolution API setup.
Troubleshooting
Common issues:
- Incorrect or missing API key leading to authentication failures.
- Invalid group ID causing "group not found" errors.
- Wrong server URL or instance name resulting in connection errors.
- Insufficient permissions for the API key to perform updates.
Error messages:
"Operação não suportada."indicates the requested operation is not implemented or recognized by the node; verify the resource and operation parameters.- Authentication errors usually suggest invalid or expired API keys; ensure the API key is correct and active.
- Network or connection errors may require checking the server URL and network accessibility.
Links and References
- Evolution API official documentation: https://doc.evolution-api.com/api-reference
- n8n documentation on creating custom nodes: https://docs.n8n.io/integrations/creating-nodes/