Actions64
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
- Instancia Actions
- Mensagem Actions
- Grupo Actions
Overview
This node, named "Evolution API," allows users to interact with the Evolution API service. Specifically, for the resource "Mensagem" and operation "Enviar Audio," it enables sending an audio message to a specified recipient via the Evolution platform. This is useful in scenarios where automated or programmatic audio messaging is required, such as customer support callbacks, notifications, or marketing campaigns that use voice messages.
For example, you can configure this node to send a pre-recorded audio clip to a customer's phone number after a certain event triggers in your workflow.
Properties
| Name | Meaning |
|---|---|
| Nome Da Instância | The name of the instance that will send the audio message. |
| Número Do Destinatário | The recipient's phone number or identifier to whom the audio message will be sent. |
| Audio | The audio content to send, provided as a URL or base64-encoded string. |
| Opções (Delay) | Optional delay in milliseconds before the message is sent. Default is 1200 ms if not set. |
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 media content or related binary attachments; however, based on the provided code and properties, the output is JSON only.
Dependencies
- Requires an API key credential for authenticating with the Evolution API.
- The node expects the Evolution API endpoint to be reachable and properly configured.
- No additional external dependencies are indicated beyond the Evolution API service itself.
Troubleshooting
- Operation Not Supported Error: If you see an error stating the operation is not supported, verify that the resource and operation names are correctly set to "messages-api" and "send-audio" respectively.
- Authentication Failures: Ensure the API key credential is valid and has the necessary permissions.
- Invalid Audio Format: The audio property must be a valid URL or base64 string representing audio data. Invalid formats may cause the API call to fail.
- Delay Misconfiguration: Setting an extremely low or high delay might affect message timing; use reasonable values (e.g., 1200 ms default).
- Network Issues: Confirm network connectivity to the Evolution API endpoint.
Links and References
- Evolution API official documentation (link not provided in source)
- n8n documentation on creating custom nodes and using credentials
- General best practices for sending media messages via APIs