Avisa API icon

Avisa API

Integration with Avisa API

Actions9

Overview

This node integrates with the Avisa API to send WhatsApp messages and perform related operations. Specifically, for the Message resource and Send Image operation, it allows sending an image file encoded in Base64 format to a specified phone number via WhatsApp.

Common scenarios where this node is beneficial include:

  • Sending promotional or informational images directly to customers.
  • Delivering product photos or visual content as part of customer support.
  • Automating image-based notifications or alerts.

For example, a business could use this node to automatically send a product catalog image to a customer after they request it through a chatbot.

Properties

Name Meaning
Phone Number The recipient's phone number in international format (e.g., +1234567890).
Message Optional text message to accompany the image.
Image (Base64) The image file encoded as a Base64 string 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.

The json output field contains the API response object, which typically includes success status and any relevant metadata returned by the API about the sent image message.

No binary data is output by this node; all responses are JSON objects representing the result of the send operation.

Dependencies

  • Requires an active connection to the Avisa API service.
  • Needs an API authentication token credential configured in n8n to authorize requests.
  • The base URL for the API is derived from the credential and used for HTTP POST requests.
  • The node uses HTTP POST requests with JSON payloads to communicate with the API endpoints.

Troubleshooting

  • Invalid or missing API token: If the API token is incorrect or missing, the node will receive 401 Unauthorized errors. Ensure the API key credential is correctly set up.
  • Malformed Base64 image: If the Base64 string is invalid or truncated, the API may return a 400 Bad Request error. Verify that the image is properly encoded.
  • Incorrect phone number format: The phone number must be in international format without spaces or special characters. Invalid numbers may cause errors or message delivery failure.
  • Timeouts: Large images might cause longer processing times; the node sets a timeout of 5 minutes for media-related requests. If timeouts occur, try reducing image size or check network stability.
  • Error messages: The node captures error messages from the API response and returns them in the output under an error property for easier debugging.

Links and References

Discussion