Evolution API

Interagir com a Evolution API v2
Join our community

Actions53

Overview

This node integrates with the Evolution API v2 to send various types of WhatsApp messages and manage instances, groups, chats, events, and integrations. Specifically, the "Mensagem" resource with the "Enviar Áudio" operation allows users to send audio messages via WhatsApp by providing an audio URL and recipient number.

Common scenarios for this node include automating customer support communications, sending voice notifications or alerts, and broadcasting audio content to WhatsApp contacts. For example, a business could use it to send personalized audio messages to clients or deliver audio-based updates in bulk.

Properties

Name Meaning
Instance Name The name of the Evolution API instance to use for sending the message.
Number The recipient's phone number to which the audio message will be sent.
Audio URL The URL of the audio file to be sent as a WhatsApp audio message.

Output

The node outputs a JSON object containing the response from the Evolution API after attempting to send the audio message. The output includes:

  • success: Boolean indicating if the operation was successful.
  • timestamp: ISO string timestamp of when the operation completed.
  • Additional fields returned by the API, which may include message IDs or status details.

If the API returns multiple items (e.g., batch operations), the output will be an array of parsed JSON objects representing each item.

The node does not output binary data; all responses are JSON-formatted.

Dependencies

  • Requires an active Evolution API v2 credential configured in n8n for authentication.
  • The node makes HTTP requests to the Evolution API endpoints.
  • The user must provide valid URLs for audio files accessible by the API.

Troubleshooting

  • Invalid or inaccessible Audio URL: Ensure the provided audio URL is publicly accessible and points to a supported audio format. Otherwise, the API may reject the request.
  • Incorrect Instance Name: Verify that the instance name matches an existing and connected Evolution API instance.
  • API Authentication Errors: Confirm that the API key or token credential is correctly set up and has necessary permissions.
  • Network Issues: Check network connectivity between n8n and the Evolution API service.
  • Error Messages: If the node throws errors, they typically contain the API error message. Review these messages for clues such as invalid parameters or quota limits.

To resolve issues, verify input parameters, credentials, and network access. Enable "Continue On Fail" in the node settings to handle errors gracefully during batch processing.

Links and References

Discussion