Actions64
- Instance Actions
- Chat Actions
- Message Actions
- Group Actions
- Profile Actions
- Event Actions
- Integration Actions
Overview
The node named "Evolution API" provides an interface to interact with the Evolution API service. Specifically, for the Resource "Group" and Operation "Fetch Invite Code," it fetches the invite code of a specified group within an instance. This is useful in scenarios where you need to programmatically retrieve the invite link or code to share with others for joining a particular group.
Practical examples include:
- Automating the retrieval of group invite codes for distribution via other communication channels.
- Integrating group management workflows where invite codes are needed dynamically.
- Monitoring or auditing group access by periodically fetching invite codes.
Properties
| Name | Meaning |
|---|---|
| Instance Name | The name of the instance from which the invite code will be fetched. |
| Group ID | The unique identifier (JID) of the group whose invite code you want to retrieve. |
Output
The output of the node is a JSON array containing the result of the invite code fetch operation. Each item in the array corresponds to one execution result and includes the invite code data retrieved from the Evolution API for the specified group.
If the API returns binary data (not indicated here), it would typically represent media or files related to the group invite, but based on the provided code and properties, the output is expected to be JSON structured data representing the invite code details.
Dependencies
- Requires an API key credential for authenticating with the Evolution API.
- The node depends on the Evolution API endpoint at
https://doc.evolution-api.com/api-reference. - Proper configuration of the API credentials in n8n is necessary to authorize requests.
Troubleshooting
- Unsupported operation error: If the node throws an error stating the operation is unsupported, verify that the resource is set to "groups-api" and the operation to "fetch-invite-code". This error indicates the function for the requested operation does not exist.
- Missing or invalid credentials: Ensure the API key or authentication token is correctly configured in n8n credentials; otherwise, API calls will fail.
- Invalid Group ID or Instance Name: Providing incorrect or empty values for these required fields will cause the API request to fail or return no data.
- Network or API errors: Check network connectivity and API availability if requests time out or return server errors.
Links and References
- Evolution API Documentation (base URL used by the node)
- n8n documentation on Creating Custom Nodes