Actions64
- Instancia Actions
- Mensaje Actions
- Grupo Actions
- Crear Grupo
- Actualizar Imagen Del Grupo
- Actualizar Nombre Del Grupo
- Actualizar Descripción Del Grupo
- Actualizar Configuraciones
- Actualizar Miembros
- Buscar Enlace De Invitación
- Revocar Enlace De Invitación
- Enviar Enlace De Invitación
- Buscar Grupos
- Encontrar Participantes
- Mensajes Temporales
- Unirse Al Grupo
- Salir Del Grupo
- Chat Actions
- Perfil Actions
- Evento Actions
- Integración Actions
Overview
The node "Evolution API" provides an interface to interact with the Evolution API, specifically supporting operations related to groups. The operation "Enviar Enlace De Invitación" (Send Invitation Link) allows users to send invitation links to specified recipients for a particular group instance. This is useful in scenarios where you want to programmatically invite multiple contacts to join a group by sending them a customized message along with the invitation link.
Practical examples include:
- Automatically inviting new members to a community or team group.
- Sending batch invitations to customers or users for joining a support or interest group.
- Integrating group invitation workflows into larger automation processes.
Properties
Name | Meaning |
---|---|
Nombre De La Instancia | The name of the instance that will send the invitation. |
ID Del Grupo | The unique identifier of the group to which the invitation link will be sent. |
Mensaje De La Invitación | The message text that accompanies the invitation link when sent to recipients. |
Destinatarios | Comma-separated list of recipient phone numbers to whom the invitation will be sent (e.g., 5511999999999,5511888888888). |
Output
The node outputs a JSON array containing the response from the Evolution API after attempting to send the invitation link(s). Each item in the output array corresponds to the result of the invitation request, typically including status information and any relevant metadata returned by the API.
If the API supports binary data responses (not indicated here), it would be summarized accordingly, but based on the provided code and properties, the output is purely JSON.
Dependencies
- Requires an API key credential for authenticating with the Evolution API.
- The node expects the Evolution API base URL
https://doc.evolution-api.com/api-reference
. - Proper configuration of the API credentials within n8n is necessary to authorize requests.
- Network access to the Evolution API endpoint must be available.
Troubleshooting
Common Issues:
- Invalid or missing API credentials can cause authentication failures.
- Incorrect group ID or instance name may lead to errors or failed invitations.
- Malformed recipient numbers (wrong format or missing commas) can prevent messages from being sent.
- Network connectivity issues can block communication with the API.
Error Messages:
"Operação não suportada."
indicates that the requested operation is not supported for the selected resource; verify that the resource and operation names are correct.- API error responses may include details about invalid parameters or authorization failures; check the message and description fields for guidance.
Resolution Tips:
- Double-check all input property values for correctness and completeness.
- Ensure the API key credential is valid and has sufficient permissions.
- Format recipient numbers exactly as required, separated by commas without extra spaces.
- Test network connectivity to the API endpoint outside n8n if needed.
Links and References
- Evolution API Documentation (official API reference)
- n8n documentation on Creating Custom Nodes