AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter

Actions277

Overview

This node interacts with the AvantGuard DNSFilter API to retrieve a list of network subnets associated with a specified network. The "Network Subnets Index" operation fetches subnet information for a given network ID, optionally supporting pagination through additional query parameters.

Common scenarios where this node is useful include:

  • Managing and auditing network configurations by listing all subnets within a network.
  • Integrating network subnet data into workflows for monitoring or compliance purposes.
  • Automating network inventory updates by periodically fetching subnet details.

For example, a user might use this node to get all subnets of a particular network to verify their IP ranges or to feed this data into a security monitoring system.

Properties

Name Meaning
Id Network ID (number) — Identifies the specific network whose subnets are to be listed.
Additional Query Parameters Optional parameters to customize the request; currently supports:
- Page (JSON) — Specifies pagination details such as page number and size.

Output

The node outputs JSON data representing the list of network subnets retrieved from the API. Each item in the output typically contains subnet details such as subnet ID, address range, and related metadata as provided by the AvantGuard DNSFilter service.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating with the AvantGuard DNSFilter API.
  • The node uses the base URL https://api.dnsfilter.com for API requests.
  • Proper configuration of the API authentication credential in n8n is necessary.

Troubleshooting

  • Invalid Network ID: If the provided network ID does not exist or is incorrect, the API may return an error or empty results. Verify the network ID before running the node.
  • Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key credential is correctly set up.
  • Pagination Issues: Incorrectly formatted pagination parameters in "Additional Query Parameters" may lead to unexpected results or errors. Use valid JSON format for the page parameter.
  • API Rate Limits: Frequent requests might hit rate limits imposed by the API. Implement retry logic or reduce request frequency if needed.

Links and References

Discussion