Avisa API icon

Avisa API

Integration with Avisa API

Actions9

Overview

This node integrates with the Avisa API to manage webhook URLs among other messaging and contact-related operations. Specifically, for the Webhook - Post operation, it allows users to set or update the webhook URL that will receive notifications from the Avisa service.

Common scenarios where this node is beneficial include:

  • Configuring a webhook endpoint to receive real-time event notifications (e.g., incoming messages, status updates) from the Avisa platform.
  • Automating the setup of webhook URLs as part of deployment or integration workflows.
  • Updating webhook URLs dynamically based on environment or workflow requirements.

For example, a user can use this node to programmatically set their server’s webhook URL so that all WhatsApp message events are forwarded to their application for processing.

Properties

Name Meaning
Webhook URL URL to receive webhook notifications

The node requires the user to provide the full URL where webhook notifications should be sent.

Output

The output of the node is a JSON array containing the response from the Avisa API after attempting to set the webhook URL. The structure typically includes success indicators or error messages returned by the API.

Example output JSON might look like:

[
  {
    "success": true,
    "message": "Webhook URL set successfully"
  }
]

Or in case of failure:

[
  {
    "success": false,
    "error": "Invalid webhook URL"
  }
]

No binary data is output by this 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 configuration.
  • The node makes HTTP POST requests to the /webhook endpoint of the Avisa API.

Troubleshooting

Common Issues

  • Invalid or unreachable webhook URL: The API may reject URLs that are malformed or not accessible from the Avisa servers.
  • Authentication errors: If the API token is missing, expired, or incorrect, the request will fail with authorization errors.
  • Network issues: Connectivity problems between n8n and the Avisa API endpoint can cause timeouts or failures.

Error Messages and Resolutions

  • 400 Bad Request or 401 Unauthorized: Usually indicates invalid input or authentication failure. Verify the webhook URL format and ensure the API token credential is correct and has necessary permissions.
  • Errors containing messages like "Invalid webhook URL": Check that the URL is properly formatted (including protocol, e.g., https://) and publicly accessible.
  • Timeout or network errors: Confirm network connectivity and that the Avisa API endpoint is reachable from your n8n instance.

If the node is configured to continue on failure, errors will be included in the output JSON for further inspection.

Links and References

Discussion