AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter

Actions277

Overview

This node interacts with a network management API to retrieve information about networks within a specified organization. Specifically, the "Networks Msp" operation under the "Networks" resource fetches network data filtered by an organization ID and optional query parameters. This node is useful for IT administrators or MSPs (Managed Service Providers) who need to programmatically access network details for monitoring, reporting, or automation purposes.

Practical examples include:

  • Retrieving basic network info for all networks under a given organization.
  • Fetching network data without IP addresses for privacy or compliance reasons.
  • Paginating through large sets of network data using page parameters.

Properties

Name Meaning
Organization Id The unique numeric identifier of the organization whose networks are being queried.
Additional Query Parameters Optional fields to refine the network query:
- Basic Info: Return only the most basic network information (boolean, defaults to true).
- Force Truncate Ips: Exclude IP address details from the returned network info (boolean, defaults to true).
- Page: JSON object specifying pagination details such as page number and size.

Output

The node outputs JSON data containing network information corresponding to the specified organization and query parameters. The structure typically includes network attributes such as network IDs, names, and other metadata depending on the query options selected (e.g., basic info only or full details).

If IP addresses are truncated via the force_truncate_ips option, the output will omit those sensitive fields.

No binary data output is indicated in the source code.

Dependencies

  • Requires an API key credential for authenticating requests to the external network management service.
  • The node sends HTTP requests to the service's API endpoint, so internet connectivity and proper API credentials configured in n8n are necessary.

Troubleshooting

  • Missing or invalid Organization Id: The node requires a valid numeric organization ID; ensure this is provided and correct.
  • API authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
  • Unexpected empty or incomplete results: Check if query parameters like basic_info or force_truncate_ips are filtering out expected data.
  • Pagination issues: When dealing with large datasets, ensure the page parameter is correctly formatted as JSON and specifies valid page numbers and sizes.

Common error messages would likely relate to HTTP request failures, invalid parameters, or authentication problems. Resolving these involves verifying input values and credential configurations.

Links and References

  • Refer to the external network management API documentation for detailed descriptions of query parameters and response formats.
  • Consult n8n documentation on setting up API key credentials and HTTP request nodes for additional context on authentication and request handling.

Discussion