Actions64
- Instancia Actions
- Mensagem Actions
- Grupo Actions
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
Overview
This node interacts with the "Evolution API" to perform various operations related to groups. Specifically, for the Resource "Grupo" and Operation "Enviar Link De Convite," it sends an invitation link to specified recipients to join a group. This is useful in scenarios where you want to automate sending group invite links via a messaging or communication platform, streamlining the process of onboarding new members.
Practical examples include:
- Automatically inviting users to a project collaboration group.
- Sending event or community group invitations to multiple contacts at once.
- Managing group memberships by distributing invite links programmatically.
Properties
| Name | Meaning |
|---|---|
| Nome Da Instância | The name of the instance that will send the invitation. |
| ID Do Grupo | The unique identifier of the group to which the invitation link will be sent. |
| Mensagem Do Convite | The message text that accompanies the invitation 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 link(s). The exact structure depends on the API response but typically includes status information about the invitation delivery.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Evolution API.
- The node expects the Evolution API base URL and headers to be configured internally.
- No additional external dependencies are explicitly required beyond the API access.
Troubleshooting
Common Issues:
- Invalid or missing API credentials can cause authentication failures.
- Incorrect group ID or instance name may result in errors or failed invitations.
- Improperly formatted recipient numbers (not comma-separated or invalid phone formats) can cause the operation to fail.
Error Messages:
"Operação não suportada."indicates that the requested operation is not implemented or recognized; verify the resource and operation names.- API errors returned from the Evolution API should be checked for details such as invalid parameters or quota limits.
Resolutions:
- Ensure all required properties are correctly filled.
- Validate phone number formatting.
- Confirm API credentials are valid and have necessary permissions.
- Check network connectivity and API endpoint availability.
Links and References
- Evolution API Documentation (as referenced in the node's base URL)