AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter

Actions277

Overview

This node fetches total client statistics from Traffic Reports. It is useful for network administrators or MSPs who want to retrieve aggregated traffic data over a specified time range and filtered by various organizational parameters. For example, you can use it to get the total number of clients connected across multiple networks within a given date range, helping with usage analysis or reporting.

Properties

Name Meaning
Additional Query Parameters Optional filters and parameters to customize the report query:
- From UTC start datetime for the report (format: YYYY-MM-DDThh:mm:ss or with Z). Defaults to 1 day before now.
- To UTC end datetime for the report (same format as From). Defaults to current UTC datetime.
- Msp Id Numeric ID of the Managed Service Provider (MSP) to filter the report.
- Network Ids Comma-separated list of network IDs to include in the report. Defaults to all networks if empty.
- Organization Id Numeric ID of the organization to filter the report. Defaults to the user's organization if not set.

Output

The node outputs JSON data containing the total client statistics as returned by the Traffic Reports API. The exact structure depends on the API response but typically includes aggregated counts and metrics related to client traffic over the specified period and filters.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating requests to the Traffic Reports service.
  • The node uses HTTP requests to the Traffic Reports API endpoint at https://api.dnsfilter.com.
  • Proper configuration of the API authentication credential in n8n is necessary.

Troubleshooting

  • Invalid Date Format: If the "From" or "To" parameters are not in the correct ISO datetime format, the API may default to fallback values or return errors. Ensure dates follow YYYY-MM-DDThh:mm:ss or YYYY-MM-DDThh:mm:ssZ.
  • Authentication Errors: Missing or invalid API credentials will cause authentication failures. Verify that the API key credential is correctly configured.
  • Empty or Incorrect Filters: Providing invalid MSP, organization, or network IDs may result in empty responses or errors. Double-check these IDs.
  • API Rate Limits: Excessive requests might be throttled by the API. Implement retry logic or reduce request frequency if needed.

Links and References

Discussion