AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter

Actions277

Overview

This node interacts with the AvantGuard DNSFilter API to count allowed URLs associated with a specific policy. It is useful for network administrators or security professionals who want to monitor or audit the number of allowed URLs/domains configured under a given policy in their DNS filtering setup. For example, it can be used to quickly retrieve how many URLs are whitelisted for a particular policy, helping in compliance checks or policy reviews.

Properties

Name Meaning
Policy Id The unique identifier of the policy whose allowed URLs/domains you want to count.
Additional Query Parameters Optional filters to refine the count query:
- Search: Text to search within URL values and notes.
- Type: Filter by type of allowed URL (valid types: url, pattern, domain, tld).
Additional Body Fields Optional body parameters to further specify which URL filters to count:
- Ids: JSON array of specific URL filter IDs to count, overrides other filters if provided.
- Exclude Ids: JSON array of URL filter IDs to exclude from the count when using filters.

Output

The node outputs a JSON object containing the count of allowed URLs matching the specified criteria. The exact structure depends on the API response but typically includes a numeric count field indicating how many allowed URLs meet the query conditions.

No binary data output is expected from this operation.

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

  • Missing or invalid Policy Id: The node requires a valid policy ID; ensure this is provided and corresponds to an existing policy.
  • API authentication errors: If the API key is missing, expired, or incorrect, the node will fail to authenticate. Verify the API key credential setup.
  • Invalid filter parameters: Providing unsupported types or malformed JSON in additional fields may cause API errors. Double-check input formats.
  • Network issues: Connectivity problems to the API endpoint will result in request failures; verify network access.

Common error messages will relate to authentication failure, invalid parameters, or resource not found. Resolving these involves checking credentials, input correctness, and policy existence.

Links and References

  • AvantGuard DNSFilter API documentation (refer to official AvantGuard resources)
  • n8n documentation on creating and configuring API credentials

Discussion