Actions64
- Instance Actions
- Message Actions
- Group Actions
- Chat Actions
- Profile Actions
- Event Actions
- Integration Actions
Overview
The node "Evolution API" provides integration with the Evolution API service, allowing users to perform various operations on different resources. Specifically, for the Group resource and the Find Participants operation, this node enables retrieving the list of participants in a specified group. This is useful in scenarios where you need to manage or analyze group membership data, such as monitoring active members, auditing participation, or syncing group participant information with other systems.
Practical examples include:
- Fetching all participants of a chat group to display in a dashboard.
- Automating notifications or actions based on group membership.
- Integrating group participant data into CRM or communication platforms.
Properties
| Name | Meaning |
|---|---|
| Name Da Instância | The name of the instance to connect to (required). |
| Group ID | The unique identifier of the group whose participants you want to find (required). |
Output
The node outputs a JSON array containing the participants found in the specified group. Each item in the array represents a participant with their associated details as returned by the Evolution API. The exact structure depends on the API response but typically includes participant identifiers and related metadata.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Evolution API.
- The base URL for requests is set to
https://doc.evolution-api.com/api-reference. - Proper configuration of the API authentication credentials within n8n is necessary.
Troubleshooting
- Operation Not Supported Error: If you select an unsupported operation or resource, the node throws an error indicating the operation is not supported. Ensure that the resource is set to "groups-api" and the operation to "find-participants".
- Missing Required Parameters: Both "Name Da Instância" and "Group ID" are required. Omitting these will likely cause errors or empty results.
- Authentication Issues: Invalid or missing API credentials will prevent successful API calls. Verify that the API key credential is correctly configured.
- API Endpoint Changes: Since the base URL points to documentation, ensure the actual API endpoint URLs are correct and accessible.
Links and References
- Evolution API Documentation (for detailed API usage and endpoints)