Avisa API icon

Avisa API

Integration with Avisa API

Actions9

Overview

This node integrates with the Avisa API to send various types of WhatsApp messages programmatically. Specifically, for the Message resource and Send Audio operation, it allows sending an audio file encoded in Base64 format to a specified phone number in international format.

Common scenarios where this node is beneficial include:

  • Sending voice notes or audio alerts to customers or users.
  • Automating delivery of audio content such as podcasts, announcements, or instructions via WhatsApp.
  • Integrating audio messaging into customer support workflows or marketing campaigns.

Example use case: Automatically send a recorded audio message to a client after they complete a form on your website.

Properties

Name Meaning
Phone Number The recipient's phone number in international format (e.g., +1234567890).
Audio (Base64) The audio file content encoded as a Base64 string. This is the audio message to be sent.

Output

The node outputs a JSON array where each element corresponds to the response from the Avisa API for each input item processed.

For the Send Audio operation, the output JSON object typically contains the API response indicating success or failure of the audio message sending request. If the request fails due to client errors (e.g., invalid number or authentication issues), the output includes an error object with details.

No binary data is output by this node; all responses are JSON objects representing the API's reply.

Dependencies

  • Requires an API key credential for authenticating with the Avisa API.
  • The node uses the base URL configured in the credentials to make HTTP POST requests to the endpoint /actions/sendAudio.
  • The API token must be provided and is used in the Authorization header as a Bearer token.
  • The audio file must be provided as a Base64-encoded string within the node parameters.

Troubleshooting

  • Invalid Phone Number Format: Ensure the phone number is in the correct international format including country code, without spaces or special characters.
  • Authentication Errors: If you receive 401 Unauthorized errors, verify that the API key credential is correctly set up and has not expired.
  • 400 Bad Request Errors: These may occur if the Base64 audio string is malformed or missing required fields. Confirm the audio data is properly encoded and included.
  • Timeouts or Network Issues: Large audio files might cause timeouts; ensure the audio size is reasonable and network connectivity is stable.
  • Error Messages: The node captures error messages returned by the API and includes them in the output under an error field for easier debugging.

Links and References

Discussion