Avisa App icon

Avisa App

Integration with Avisa App API

Actions5

Overview

This node integrates with the Avisa App API to send WhatsApp messages and perform related operations. Specifically, for the Message - Send Text operation, it sends a plain text message to a specified phone number in international format or JID (WhatsApp identifier). This is useful for automating notifications, alerts, customer support messages, or any scenario where sending WhatsApp text messages programmatically is needed.

For example, you could use this node to:

  • Send order confirmation messages to customers.
  • Notify users about appointment reminders.
  • Deliver real-time alerts or updates via WhatsApp.

Properties

Name Meaning
Phone Number The recipient's phone number in international format or WhatsApp JID to which the message will be sent.
Message The text content of the message to send via WhatsApp.

Output

The node outputs an array of JSON objects corresponding to each input item processed. Each object contains the response from the Avisa App API after attempting to send the message. The structure typically includes success status and any returned data or error information.

Example output JSON snippet:

[
  {
    "success": true,
    "messageId": "abc123",
    "status": "sent"
  }
]

If an error occurs (e.g., invalid phone number or authentication failure), the output will include an error field describing the issue:

[
  {
    "success": false,
    "error": "Invalid phone number format"
  }
]

The node does not output binary data for this operation.

Dependencies

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

Troubleshooting

  • Common issues:

    • Invalid or missing phone number format can cause API errors.
    • API token misconfiguration or expiration leads to authentication failures.
    • Network connectivity problems may cause request timeouts or failures.
    • Sending messages larger than allowed size limits (not applicable for text but relevant for media).

  • Error messages:

    • 400 Bad Request or 401 Unauthorized: Usually indicates invalid input or authentication issues. Verify phone number format and API token validity.
    • Errors returned by the API are included in the output under the error field for easier debugging.

  • Resolution tips:

    • Ensure phone numbers are in correct international format without extra characters.
    • Confirm that the API token credential is correctly set up and has necessary permissions.
    • Check network access to the Avisa App API endpoint.
    • Use the node’s built-in error handling and enable "Continue On Fail" if processing multiple items to avoid stopping on single errors.

Links and References

Discussion