AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter

Actions277

Overview

This node operation retrieves detailed information about a specific subnet within a network. It is useful when you need to inspect or manage individual subnets by their unique identifiers, such as for auditing, configuration verification, or integration with other systems that require subnet details.

Practical examples include:

  • Fetching subnet details before applying firewall rules.
  • Verifying subnet configurations during network automation workflows.
  • Integrating subnet data into reporting dashboards.

Properties

Name Meaning
Id Network ID (numeric identifier of the network containing the subnet)
Subnet Id Subnet ID (numeric identifier of the specific subnet to retrieve)

Both properties are required to specify exactly which subnet's information should be fetched.

Output

The output will contain JSON data representing the details of the requested subnet. This typically includes subnet attributes such as its address range, associated network, status, and any metadata provided by the API.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authentication with the AvantGuard DNSFilter service.
  • The node communicates with the DNSFilter API endpoint at https://api.dnsfilter.com.
  • Proper configuration of the API key credential in n8n is necessary for successful requests.

Troubleshooting

  • Missing or invalid API key: Ensure the API key credential is correctly set up and has the necessary permissions.
  • Invalid Network ID or Subnet ID: Verify that the numeric IDs provided correspond to existing resources; otherwise, the API may return errors or empty results.
  • Network connectivity issues: Confirm that n8n can reach the DNSFilter API endpoint without firewall or proxy restrictions.
  • Unexpected API responses: Check if the API version or schema has changed, requiring updates to the node or credentials.

Links and References

Discussion