Evolution API icon

Evolution API

Interact with Evolution API

Actions64

Overview

The node "Evolution API" allows interaction with the Evolution API service. Specifically, for the resource Mensagem and operation Enviar Audio, it sends an audio message to a specified recipient via the Evolution API. This is useful in scenarios where automated audio notifications, voice messages, or alerts need to be sent programmatically to users or customers.

Practical examples include:

  • Sending voice reminders or confirmations to clients.
  • Delivering audio alerts in customer support workflows.
  • Broadcasting pre-recorded announcements to multiple recipients.

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 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 sending the message (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 indicated here), it would represent the audio 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 API call to fail.
    • Incorrect audio URL or malformed base64 string may result in message rejection.
    • Network connectivity problems can prevent communication with the Evolution API.
    • Delay option set too low might cause timing issues in message processing.

  • Error messages:

    • "Operação não suportada." indicates the selected operation-resource combination is not implemented.
    • API errors returned by the Evolution API will be passed through; check the API documentation for specific error codes.

  • Resolutions:

    • Verify all required fields are correctly filled.
    • Ensure the audio content is accessible and properly formatted.
    • Confirm API credentials are valid and have necessary permissions.
    • Increase delay if messages are sent too quickly in succession.

Links and References

Discussion