Actions64
- Instance Actions
- Message Actions
- Group Actions
- Chat Actions
- Profile Actions
- Event Actions
- Integration Actions
Overview
The node "Evolution API" allows interaction with the Evolution API service. Specifically, for the Resource "Group" and Operation "Send Invite Link," it sends an invitation link to specified recipients to join a group. This is useful in scenarios where you want to automate inviting multiple users to a group chat or community by sending them a personalized invite message along with the group link.
Practical examples include:
- Automatically inviting new customers or members to a support or interest group.
- Sending batch invitations to event participants or team members.
- Integrating group invites into onboarding workflows.
Properties
| Name | Meaning |
|---|---|
| Name Da Instância | The name of the instance that will send the invite. |
| Group ID | The unique identifier of the group to which the invite link will be sent. |
| Mensagem Do Convite | The message that will accompany the invite link when sent to recipients. |
| Destinatários | Comma-separated list of recipient phone numbers (e.g., 5511999999999,5511888888888) to receive the invite. |
Output
The node outputs a JSON array containing the response from the Evolution API after attempting to send the invite links. The exact structure depends on the API response but typically includes status information about the invite operation for each recipient.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Evolution API.
- The base URL for requests is
https://doc.evolution-api.com/api-reference. - Proper configuration of the API credential within n8n is necessary.
Troubleshooting
- Operation not supported error: If the node throws an error stating the operation is not supported, verify that the resource and operation names are correctly set to "groups-api" and "send-invite-link" respectively.
- Invalid or missing parameters: Ensure all required properties (instance name, group ID, message, and recipient numbers) are provided and correctly formatted.
- API authentication errors: Confirm that the API key credential is valid and has the necessary permissions.
- Incorrect recipient number format: Recipient numbers must be comma-separated without spaces and include country codes as shown in the example.
Links and References
- Evolution API Documentation (base URL referenced in the node)