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" allows interaction with the Evolution API service. Specifically, for the resource Mensaje and operation Enviar Audio, it sends an audio message to a specified recipient through the Evolution API. This is useful in scenarios where automated audio notifications, voice messages, or audio alerts need to be sent programmatically to users or clients.
Practical examples include:
- Sending voice reminders or alerts to customers.
- Delivering audio confirmations or instructions.
- Broadcasting audio announcements via messaging platforms integrated with Evolution API.
Properties
| Name | Meaning |
|---|---|
| Nombre De La Instancia | The name of the instance that will send the audio message. |
| Número Del Destinatario | The recipient's phone number or identifier to whom the audio will be sent. |
| Audio | The audio content to send, provided as a URL or base64 encoded string. |
| Opciones | Additional options for sending the message: |
| - Retraso | Delay in milliseconds before the message is sent (default is 1200 ms). |
Output
The node outputs a JSON array containing the response from the Evolution API after attempting to send the audio message. The exact structure depends on the API response but typically includes status information about the message delivery.
If the node supports binary data output (not explicitly shown here), it would represent the audio content or related media; however, in this case, the audio is input only, and output is JSON metadata.
Dependencies
- Requires an active connection to the Evolution API service.
- Needs an API authentication token or key configured in n8n credentials (referred generically as "an API key credential").
- Network access to the Evolution API endpoint
https://doc.evolution-api.com/api-reference.
Troubleshooting
Common issues:
- Invalid or missing instance name or recipient number will cause the request to fail.
- Incorrect audio URL or malformed base64 string may result in errors or failed message delivery.
- Network connectivity problems or invalid API credentials will prevent successful communication with the Evolution API.
Error messages:
"Operação não suportada."indicates the selected operation is not supported for the chosen resource; verify correct resource and operation names.- API errors returned by Evolution API will be passed through; check the error details for authentication, authorization, or payload format issues.
Resolutions:
- Ensure all required fields are correctly filled.
- Validate audio input format and accessibility.
- Confirm API credentials are valid and have necessary permissions.
- Check network connectivity and Evolution API service status.
Links and References
- Evolution API Documentation (official API reference)
- n8n documentation on creating custom nodes for further customization guidance