AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter

Actions277

Overview

This node interacts with the AvantGuard DNSFilter API to retrieve a list of blocked URLs associated with a specific policy. It is useful for security and network administrators who want to audit or monitor URLs that have been blocked by their DNS filtering policies. For example, it can be used to generate reports on blocked content or to integrate blocked URL data into broader security workflows.

Properties

Name Meaning
Policy Id The identifier of the policy whose blocked URLs you want to retrieve.
Additional Query Parameters Optional filters and options to refine the query results:
- Ids: Filter results by specific blocked URL IDs (JSON array).
- Include Categories And Applications: Whether to include category and application details (boolean).
- Search: Search term to filter blocked URLs by value or note (string).
- Sort: Comma-separated attributes to sort by, valid values are type and value.
- Type: Filter by type of blocked URL, valid types are url or pattern.

Output

The node outputs JSON data representing the list of blocked URLs retrieved from the specified policy. Each item in the output typically includes details such as the URL or pattern blocked, its ID, associated categories and applications (if requested), and any notes or metadata provided by the API.

If binary data were involved, it would represent file attachments or similar, but this node focuses solely on JSON data about blocked URLs.

Dependencies

  • Requires an API key credential for authenticating with the AvantGuard DNSFilter service.
  • The node sends requests to the base URL https://api.dnsfilter.com.
  • Proper configuration of the API key credential within n8n is necessary for successful operation.

Troubleshooting

  • Missing or invalid Policy Id: Ensure the Policy Id is correctly set and corresponds to an existing policy in your DNSFilter account.
  • Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
  • Invalid query parameters: Check that optional filters like ids, type, and sort use valid formats and values.
  • Empty results: If no blocked URLs are returned, confirm that the policy actually has blocked URLs matching the query criteria.
  • API rate limits or connectivity issues: Network problems or hitting API limits may cause failures; retry after some time or check network settings.

Links and References

Discussion