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 explicitly shown here), it would represent the audio file or related media; 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 service to be reachable and properly configured.
  • No additional environment variables are explicitly required beyond the API authentication.

Troubleshooting

  • Operation Not Supported Error: If you select an unsupported operation or resource, the node throws an error indicating the operation is not supported. Ensure you use valid combinations of resource and operation.
  • Invalid or Missing Parameters: Required fields such as instance name, recipient number, and audio must be provided. Missing these will cause errors.
  • API Authentication Failures: Ensure the API key credential is correctly set up and has necessary permissions.
  • Network Issues: Connectivity problems to the Evolution API endpoint can cause failures; verify network access.
  • Audio Format Issues: The audio must be a valid URL or base64 string representing an audio file. Invalid formats may cause the API to reject the request.

Links and References

Discussion