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 Message resource and Send Audio operation, it sends an audio message to a specified recipient number via a chosen instance of the Evolution API.

This node is useful in scenarios where automated sending of audio messages is required, such as:

  • Sending voice notifications or alerts to users.
  • Delivering pre-recorded audio content in customer support workflows.
  • Broadcasting audio announcements to multiple recipients programmatically.

Example: Automatically send a welcome audio message to a new user’s phone number after registration.

Properties

Name Meaning
Instance Name The name of the Evolution API instance that will send the audio message.
Recipient Number The phone number (in appropriate format) of the message recipient.
Audio The audio content to send, provided as a URL or base64 encoded string.
Options Additional options for sending the message:
- Delay Time delay in milliseconds before the audio message is sent (default 1200 ms).

Output

The node outputs a JSON array containing the response from the Evolution API after attempting to send the audio message. This typically includes status information about the message delivery.

If the node supports binary data output (not explicitly shown in the code), it would represent any media or file data returned by the API, but here the focus is on JSON responses.

Dependencies

  • Requires an active Evolution API account and valid API credentials configured in n8n.
  • The node depends on the Evolution API endpoint at https://doc.evolution-api.com/api-reference.
  • Proper network access to the Evolution API service is necessary.
  • The node expects the audio input either as a URL accessible by the API or as a base64 encoded string.

Troubleshooting

  • Unsupported operation error: If you select an operation not implemented for the resource, the node throws an error indicating unsupported operation. Ensure the operation and resource names are correct.
  • Invalid or missing parameters: Required fields like Instance Name, Recipient Number, and Audio must be provided; otherwise, the API call will fail.
  • API authentication errors: Verify that the API credentials are correctly set up and have sufficient permissions.
  • Network issues: Ensure the server running n8n can reach the Evolution API endpoint.
  • Audio format issues: The audio must be a valid URL or properly encoded base64 string; invalid formats may cause message sending failure.

Links and References

Discussion