Evolution API icon

Evolution API

Interact with Evolution API

Actions64

Overview

The "Enviar Audio" operation of the "Mensagem" (Message) resource in this custom n8n node allows users to send audio messages via the Evolution API. This is particularly useful for automating communication workflows where sending voice notes or audio files to recipients through an API is required. Common scenarios include customer support bots, notification systems, or marketing campaigns that utilize audio messages.

Practical Example:
A business could use this node to automatically send a pre-recorded audio message to customers when their order status changes, or as part of a WhatsApp automation workflow.

Properties

Below are the supported input properties for this operation:

Display Name Type Description
Nome Da Instância String Digite o nome da instância que vai enviar o áudio (Enter the instance name that will send the audio). Required.
Número Do Destinatário String Número do destinatário (Recipient's number). Required.
Audio String URL ou base64 do áudio (URL or base64-encoded audio file). Required.
Opções Collection Additional options for the message.
- Delay Number Digite quantos milisegundos de delay a mensagem terá antes de ser enviada (Specify how many milliseconds of delay before the message is sent). Default: 1200

Output

The output of this node is a JSON object (or array of objects) representing the result of the audio message send operation. The exact structure depends on the Evolution API's response, but typically includes fields such as:

{
  "status": "success",
  "messageId": "string",
  "timestamp": "string",
  // ...other API-specific fields
}

If the API returns binary data (not typical for a send-audio operation), it would be summarized as containing the raw response from the service.

Dependencies

  • External Service: Requires access to the Evolution API.
  • API Key/Credentials: You must configure valid Evolution API credentials in n8n under the credential type evolutionApi.
  • n8n Configuration: No additional configuration beyond setting up the credentials and using the node in a workflow.

Troubleshooting

Common Issues

  • Missing or Invalid Credentials: If the Evolution API credentials are not set up correctly, the node will fail to authenticate.

  • Unsupported Operation: If the operation or resource is not implemented, you may see an error like:

    Operação não suportada.
A função "send-audio" para o recurso "messages-api" não é suportada!

    Resolution: Ensure you are using the correct resource and operation names as defined by the node.

  • Invalid Input Data: Supplying an invalid recipient number, malformed audio URL/base64, or missing required fields will cause the API call to fail.

  • Delay Option Misuse: Setting an extremely high or negative delay value may result in unexpected behavior or errors.

Error Messages

  • "Operação não suportada."
    The selected operation is not available for the chosen resource. Double-check your resource and operation selection.

  • API Response Errors:
    Any errors returned by the Evolution API (such as authentication failures, invalid parameters, etc.) will be passed through in the output JSON. Review the error message and adjust your inputs accordingly.

Links and References

Note: Always ensure your audio files are properly formatted and accessible (if using URLs) or correctly encoded (if using base64) to avoid transmission issues.

Discussion