AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter

Actions277

Overview

This node operation fetches usage reports by SKU (Stock Keeping Unit) for distributors on a specified date. It is useful for analyzing product or service consumption data distributed through various organizations and managed service providers (MSPs). Typical use cases include generating daily usage summaries, auditing distributor activity, or integrating SKU usage data into business intelligence workflows.

For example, a company might use this node to retrieve the number of licenses consumed per SKU on a given day across multiple MSPs and organizations, helping them track sales performance or compliance.

Properties

Name Meaning
Date The report date in ISO8601 format (e.g., "2022-12-31"). This specifies which day's usage data to retrieve.
Additional Query Parameters Optional parameters to refine the report:
• Include In Trial: Whether to include organizations currently in trial (true/false).
• Include Parent Organization: Whether to include MSP parent organizations (true/false).
• Msp Ids: JSON array of MSP IDs to filter the report (e.g., [1,2,3]).
• Organization Ids: JSON array of organization IDs to filter the report (e.g., [4,5,6]).

Output

The node outputs JSON data representing the usage report by SKU for the specified date and filters. The structure typically includes details such as SKU identifiers, usage counts, and associated organization or MSP information.

If binary data were output, it would represent downloadable report files or attachments, but this node focuses on JSON response data.

Dependencies

  • Requires an API key credential for authenticating requests to the external distributor reporting service.
  • The node sends HTTP GET requests with query parameters based on input properties.
  • No additional environment variables are explicitly required beyond standard API authentication setup.

Troubleshooting

  • Missing or invalid date: The "Date" property is mandatory. Omitting it or providing an incorrectly formatted date will likely cause errors or empty responses.
  • Invalid JSON in MSP or Organization IDs: The MSP and Organization ID fields expect valid JSON arrays. Malformed JSON will cause request failures.
  • API authentication errors: Ensure the API key credential is correctly configured and has sufficient permissions.
  • Empty results: If no data is returned, verify that the date and optional filters correspond to existing records in the distributor system.

Links and References

Discussion