Evolution API Direct icon

Evolution API Direct

Interact with Evolution API using direct URL and API Key

Actions64

Overview

The node "Evolution API Direct" allows users to interact with the Evolution API by sending requests directly using a specified server URL and an API key. Specifically, for the resource Mensagem and operation Enviar Audio, this node sends an audio message to a recipient via the Evolution API. This is useful in scenarios where automated audio messages need to be sent programmatically, such as notifications, alerts, or customer engagement through voice messages.

Practical examples include:

  • Sending a voice alert to a user when a certain event occurs.
  • Delivering personalized audio messages in marketing campaigns.
  • Automating customer support responses with pre-recorded audio clips.

Properties

Name Meaning
Server URL The full URL of your Evolution API server endpoint (e.g., https://api.exemplo.com).
API Key The API key credential required to authenticate requests to the Evolution API instance.
Nome Da Instância The name of the specific Evolution API 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 either as a URL or base64 encoded string.
Opções (Delay) Optional delay in milliseconds before the message is sent; default is 1200 ms (1.2 seconds).

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, but in this case, the audio is input only.

Dependencies

  • Requires access to the Evolution API server via the provided Server URL.
  • Requires a valid API key credential for authentication.
  • The node expects the Evolution API instance name and recipient number to be correctly specified.
  • No additional external dependencies are indicated beyond standard HTTP request capabilities.

Troubleshooting

  • Common Issues:

    • Incorrect Server URL or API Key will result in authentication errors.
    • Invalid or missing recipient number may cause message delivery failure.
    • Improperly formatted audio (neither valid URL nor base64) can cause the API to reject the request.
    • Delay value must be a positive number; negative or non-numeric values might cause unexpected behavior.

  • Error Messages:

    • "Operação não suportada." indicates the requested operation is not implemented for the selected resource.
    • API errors related to authentication or invalid parameters will be returned from the Evolution API and surfaced by the node.

  • Resolution Tips:

    • Verify all required fields are filled correctly.
    • Ensure the API key has sufficient permissions.
    • Confirm the audio data format matches expected input (URL or base64).
    • Check network connectivity to the specified Server URL.

Links and References

Discussion