AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter

Actions277

Overview

This node interacts with the AvantGuard DNSFilter API to check for blocked URLs associated with a specific policy. The "Blocked Urls Has Mixed" operation verifies whether there is a mixture of different types of blocked URLs or domains under a given policy ID. This can be useful in scenarios where you want to audit or analyze the composition of blocked entries within a security policy, such as identifying if both exact URLs and domain patterns are blocked.

Practical examples include:

  • Security teams verifying the diversity of blocked URL types in a policy.
  • Automated workflows that trigger alerts if mixed types of blocks are detected.
  • Reporting tools that summarize the nature of blocked content per policy.

Properties

Name Meaning
Policy Id The unique identifier of the policy whose blocked URLs/domains you want to query.
Additional Query Parameters Optional filters to refine the query:
- Search: Text to search within value and note fields.
- Type: Filter by type of block; valid options are url, pattern, domain, tld.

Output

The node outputs JSON data representing the blocked URLs or domains associated with the specified policy. The structure typically includes details about each blocked entry, such as its value (URL or domain), type, and any notes attached.

If binary data were involved, it would represent downloadable content or files related to the blocked URLs, but this node focuses on JSON responses from the API.

Dependencies

  • Requires an API key credential for AvantGuard DNSFilter service.
  • The node makes HTTP requests to https://api.dnsfilter.com.
  • Proper configuration of the API authentication token in n8n credentials is necessary.

Troubleshooting

  • Missing or invalid Policy Id: Ensure the Policy Id is provided and corresponds to an existing policy in your AvantGuard DNSFilter account.
  • Authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
  • Invalid query parameters: When using additional query parameters, ensure that the type field uses one of the valid values (url, pattern, domain, tld).
  • Network issues: Confirm that your n8n instance can reach the external API endpoint without firewall restrictions.

Common error messages might include unauthorized access, resource not found, or bad request due to invalid parameters. Resolving these usually involves checking credentials, input values, and network connectivity.

Links and References

Discussion