Actions64
- Instancia Actions
- Mensagem Actions
- Grupo Actions
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
Overview
The node "Evolution API" allows interaction with the Evolution API service, specifically supporting operations on various resources. For the resource Grupo and operation Criar Grupo, this node creates a new group instance within the specified Evolution API environment. This is useful for automating group management tasks such as setting up communication groups or team channels programmatically.
Practical examples include:
- Automatically creating project-specific groups when a new project is initiated.
- Setting up user groups for event coordination or customer segmentation.
- Managing participant lists dynamically by specifying phone numbers.
Properties
| Name | Meaning |
|---|---|
| Nome Da Instância | The name of the instance where the group will be created. |
| Nome Do Grupo | The name of the group to be created. |
| Descrição | Optional description text for the group. |
| Participantes | 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 any status or metadata returned by the API.
If the API supports binary data in responses (not evident here), it would be summarized accordingly, but this node primarily deals with JSON data.
Dependencies
- Requires an active connection to the Evolution API via an API key credential configured in n8n.
- The node expects the Evolution API endpoint to be reachable and properly authenticated.
- No additional external dependencies are indicated beyond the API access.
Troubleshooting
- Operation not supported error: If you select an unsupported operation or resource, the node throws an error indicating the function is not supported. Ensure the resource and operation names match exactly those implemented.
- API authentication errors: If the API key or credentials are invalid or missing, the node will fail to authenticate. Verify that the API key credential is correctly set up in n8n.
- Invalid participant format: Participants must be provided as comma-separated phone numbers without spaces. Incorrect formatting may cause API rejection.
- Network issues: Connectivity problems to the Evolution API endpoint will result in request failures. Check network settings and API availability.
Links and References
- Evolution API official documentation (please refer to your API provider's docs)
- n8n documentation on creating custom nodes and using API credentials
- General REST API best practices for handling JSON payloads and authentication