Actions64
- Instance Actions
- Message Actions
- Group Actions
- Chat Actions
- Profile Actions
- Event Actions
- Integration Actions
Overview
The node "Evolution API" allows interaction with the Evolution API service. Specifically, for the Resource "Group" and Operation "Update Settings," it updates configuration settings of a group identified by its Group ID. This operation is useful for managing group permissions and behaviors such as who can send messages or edit group settings.
Practical examples include:
- Restricting message sending to only admins in a group.
- Allowing all members to send messages.
- Locking group settings so only admins can edit them.
- Unlocking group settings so all members can edit them.
This node is beneficial in automating group management tasks within workflows that require dynamic control over group communication policies.
Properties
| Name | Meaning |
|---|---|
| Name Da Instância | The name of the instance where the group exists; used to identify the target environment. |
| Group ID | The unique identifier of the group whose settings will be updated. |
| Ação (Action) | The setting to apply to the group. Options: |
| - Only Admins Send Messages (announcement) | |
| - Everyone Sends Messages (not_announcement) | |
| - Only Admins Edit Settings (locked) | |
| - Everyone Edits Settings (unlocked) |
Output
The node outputs a JSON array containing the result of the update operation. The exact structure depends on the Evolution API response but typically includes confirmation of the applied settings or error details if the update failed.
No binary data output is indicated.
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
- Unsupported Operation Error: If the specified operation or resource is not supported, the node throws an error indicating the function is not supported. Ensure the resource is "groups-api" and operation is "update-settings".
- Invalid Group ID: Providing an incorrect or non-existent Group ID may cause the API to return errors. Verify the Group ID before running the node.
- Authentication Failures: Missing or invalid API credentials will prevent the node from connecting to the Evolution API.
- Network Issues: Connectivity problems can cause request failures; check network access and API availability.
Links and References
- Evolution API Documentation (base URL referenced in the node)