AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter

Actions277

Overview

This node interacts with the AvantGuard DNSFilter API to retrieve detailed information about a specific Block Page by its ID. It is useful in scenarios where users need to inspect or manage block pages configured in their DNS filtering setup, such as viewing the content or metadata of a block page that is shown when a user attempts to access a blocked site.

Practical examples include:

  • Fetching details of a particular block page to audit or verify its configuration.
  • Integrating block page data into workflows for reporting or alerting purposes.
  • Dynamically retrieving block page information to customize user notifications or logs.

Properties

Name Meaning
Id The unique identifier (ID) of the Block Page to retrieve.
Additional Query Parameters Optional parameters to modify the request; currently supports:
- Include Relationships: Boolean flag to include related entities in the response (true/false). Defaults to true.

Output

The node outputs JSON data representing the details of the requested Block Page. This includes all standard fields returned by the API for a block page entity, potentially enriched with related entities if the "Include Relationships" option is enabled.

No binary data output is produced by this node.

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 network connectivity to the DNSFilter API endpoint is necessary.

Troubleshooting

  • Invalid or missing BlockPage ID: If the provided ID does not exist or is invalid, the API will likely return an error. Ensure the ID is correct and corresponds to an existing block page.
  • Authentication errors: Missing or incorrect API credentials will cause authentication failures. Verify that the API key credential is correctly configured.
  • Network issues: Connectivity problems can prevent the node from reaching the API. Check internet connection and firewall settings.
  • Unexpected API responses: If the API changes or returns unexpected data, the node might fail. Review API documentation and update the node accordingly.

Links and References

Discussion