Actions64
- Instance Actions
- Message Actions
- Group Actions
- Integration Actions
- Chat Actions
- Profile Actions
- Event Actions
Overview
The node interacts with the Evolution API to manage groups. Specifically, the "Create Group" operation allows users to create a new group within a specified instance by providing details such as the group name, description, and participants. This is useful in scenarios where automated group management is needed, for example, setting up communication groups for teams or customer segments dynamically based on external triggers.
Practical examples:
- Automatically creating a new customer support group when a new product launch occurs.
- Setting up event-specific chat groups with predefined participants.
- Managing user groups in an application that integrates with the Evolution API.
Properties
| Name | Meaning |
|---|---|
| Instance Name | The name of the instance that will create the group. |
| Group Name | The name of the group to be created. |
| Description | Optional description text for the group. |
| Participants | Comma-separated list of participant phone numbers (e.g., 5511999999999,5511888888888). |
Output
The node outputs a JSON array containing the response from the Evolution API after attempting to create the group. This typically includes details about the newly created group such as its ID, name, description, participants, and status. The exact structure depends on the API response but generally confirms successful creation or provides error information.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Evolution API.
- The node uses the base URL
https://doc.evolution-api.com/api-referencefor API requests. - Proper configuration of the API authentication token or key in n8n credentials is necessary.
Troubleshooting
Common issues:
- Missing required fields like Instance Name, Group Name, or Participants will cause errors.
- Invalid participant number format (should be comma-separated phone numbers) may lead to API rejection.
- Authentication failures if the API key credential is not set or invalid.
- Network or API endpoint issues can cause request failures.
Error messages:
"Operation not supported."indicates the selected resource-operation combination is not implemented.- API error responses will be passed through; check the message for details such as invalid parameters or permission issues.
Resolutions:
- Ensure all required properties are filled correctly.
- Verify participant numbers follow the expected format.
- Confirm API credentials are valid and have necessary permissions.
- Check network connectivity and API endpoint availability.
Links and References
- Evolution API Documentation (base URL used by the node)