Actions64
- Instance Actions
- Message Actions
- Group Actions
- Integration Actions
- Chat Actions
- Profile Actions
- Event Actions
Overview
The "Evolution API" node allows users to interact with the Evolution API service, specifically providing operations related to different resources such as groups. For the Group resource and the Fetch Invite Link operation, this node fetches an invite code (link) for a specified group within an instance. This is useful in scenarios where you want to programmatically retrieve invite links to share or manage group memberships without manual intervention.
Practical examples include:
- Automatically retrieving invite links for new groups created in your system.
- Integrating with other workflows that require sending group invite links via email or messaging platforms.
- Managing group access by fetching and validating invite codes dynamically.
Properties
| Name | Meaning |
|---|---|
| Instance Name | The name of the instance from which the invite code will be fetched. |
| Group ID | The unique identifier (ID) of the group for which the invite code is requested. |
Output
The node outputs a JSON array containing the result of the fetch invite link operation. Each item in the array corresponds to the data returned by the Evolution API for the invite code request. Typically, this includes the invite link/code associated with the specified group.
If the API supports binary data (e.g., QR codes or images representing the invite), it would be included in the binary output field; however, based on the provided code and properties, the primary output is JSON data containing the invite link information.
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 the API is set to
https://doc.evolution-api.com/api-reference. - Proper configuration of the "Evolution API" credential in n8n is necessary.
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 you use valid resource-operation combinations.
- Missing required parameters: Both "Instance Name" and "Group ID" are mandatory. Omitting these will cause errors or failed API calls.
- Authentication failures: Incorrect or missing API credentials will prevent successful communication with the Evolution API.
- API response errors: If the group ID does not exist or the instance name is invalid, the API may return errors or empty results. Verify input values before execution.
Links and References
- Evolution API Documentation (base URL used in the node)
- n8n documentation on Creating Custom Nodes