AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter

Actions277

Overview

This node operation allows users to remove domains from the blocklist in bulk within a policy management system. It is useful for administrators who need to efficiently manage domain access policies by removing multiple domains from blocklists associated with one or more policies at once. For example, if certain domains were mistakenly blocked or are no longer considered harmful, this operation can quickly unblock them across selected policies.

Properties

Name Meaning
Additional Body Fields Optional fields to customize the request body:
- Domains A JSON array of domain names to be removed from the blocklist.
- Notes A JSON object containing key/value pairs for notes related to the domains being removed.
- Policy Ids A JSON array of policy IDs on which the removal action will be performed.

Output

The output contains a JSON structure representing the response from the API after attempting to remove the specified domains from the blocklist. This typically includes confirmation of success or details about any errors encountered. The node does not explicitly handle binary data output.

Dependencies

  • Requires an API key credential for authenticating requests to the DNS filtering service.
  • The node uses the base URL https://api.dnsfilter.com for its API calls.
  • The node depends on the external package @avantguardllc/n8n-openapi-node for building and handling OpenAPI-based requests.

Troubleshooting

  • Invalid JSON in Domains or Notes: Since the domains and notes fields expect JSON input, malformed JSON will cause errors. Ensure that these inputs are valid JSON arrays or objects.
  • Missing or Incorrect Policy IDs: If the policy IDs are missing or incorrect, the API may reject the request or fail to apply changes. Verify that the policy IDs exist and are correctly formatted.
  • Authentication Errors: Failure to provide a valid API key credential will result in authentication errors. Confirm that the API key is set up correctly in n8n credentials.
  • API Rate Limits or Network Issues: Temporary network problems or hitting API rate limits may cause failures. Retrying after some time or checking network connectivity can help.

Links and References

Discussion