Wassenger icon

Wassenger

Interact with Wassenger WhatsApp API
Join our community

Actions148

Overview

This node interacts with the Wassenger WhatsApp API, specifically providing functionality to manage and retrieve information about webhooks configured in the Wassenger system. The "Get Webhooks" operation under the "Webhooks" resource allows users to fetch a list of webhooks filtered by various criteria such as device IDs, status, search terms, and pagination options.

Common scenarios where this node is beneficial include:

  • Monitoring and managing webhook configurations for different devices.
  • Filtering webhooks based on their operational status (active, disabled, pending).
  • Searching for specific webhooks by text to quickly locate relevant webhook entries.
  • Paginating through large sets of webhook data to handle them efficiently.

Practical example:

  • A user wants to retrieve all active webhooks associated with certain devices to audit or update their configurations.
  • Another use case is fetching a paginated list of webhooks matching a search term to display in a dashboard or report.

Properties

Name Meaning
Filters Collection of filters to narrow down the webhooks retrieved.
├─ Device IDs Select one or multiple device IDs to filter webhooks associated with those devices.
├─ Status Filter webhooks by their status. Options: Active, Disabled, Pending.
├─ Search Term Text string to search webhooks by matching content.
├─ Results Page Size Number specifying how many results to return per page (default 20).
└─ Page Number Number indicating which page of results to retrieve, starting from 0 (default 0).

Output

The output is an array of JSON objects representing the webhooks that match the specified filters. Each object contains the details of a webhook as returned by the Wassenger API. The exact structure depends on the API response but typically includes webhook identifiers, associated device info, status, URL, and other metadata.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating with the Wassenger WhatsApp API.
  • The node depends on the external Wassenger service being accessible and properly configured.
  • Pagination and filtering rely on the API's support for these query parameters.

Troubleshooting

  • Common issues:

    • Invalid or missing API key will cause authentication failures.
    • Providing invalid device IDs or statuses may result in empty responses or errors.
    • Requesting pages beyond available data may return empty arrays.

  • Error messages:

    • Authentication errors: Check that the API key credential is correctly set up.
    • Validation errors on filters: Ensure device IDs exist and status values are among allowed options.
    • Network or API downtime: Verify connectivity and Wassenger service status.

Resolving these usually involves verifying credentials, input parameters, and network conditions.

Links and References

Discussion