Actions64
- Instance Actions
- Chat Actions
- Message Actions
- Group Actions
- Profile Actions
- Event Actions
- Integration Actions
Overview
The "Create Group" operation in the Group resource allows users to create a new group within an instance of the Evolution API platform. This node is useful for automating group management tasks such as setting up communication groups, organizing participants, or managing collaborative environments programmatically.
Typical use cases include:
- Automatically creating chat or discussion groups based on external triggers.
- Setting up groups with predefined participants for events or projects.
- Integrating group creation into larger workflows that manage user communications.
Properties
| Name | Meaning |
|---|---|
| Instance Name | The name of the instance where the group will be created. |
| Group Name | The name assigned to the new group being created. |
| Description | An optional text description providing details about the group. |
| Participants | A comma-separated list of participant phone numbers (e.g., 5511999999999,5511888888888) to add to the group. |
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 identifier, name, description, and participant information.
If the API supports it, the output may also contain status or error messages related to the creation process.
No binary data output is indicated by the source code.
Dependencies
- Requires an active connection to the Evolution API service.
- Needs an API authentication token or key configured in n8n credentials to authorize requests.
- The base URL for API requests is set to
https://doc.evolution-api.com/api-reference.
Troubleshooting
- Unsupported operation error: If the node throws an error stating the operation is unsupported, verify that the Resource is set to "Group" and Operation to "Create Group".
- Missing required parameters: Ensure all required fields (Instance Name, Group Name, Participants) are provided; missing these will likely cause API errors.
- Invalid participant format: Participants must be entered as comma-separated phone numbers without spaces; incorrect formatting may lead to request failures.
- API authentication issues: Confirm that the API key or token credential is correctly configured and has sufficient permissions.
- Network or API downtime: Connectivity problems or API unavailability can cause execution failures; check network access and API status.
Links and References
- Evolution API Documentation (base URL used in the node)
- General n8n documentation on creating custom nodes