AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter

Actions277

Overview

This node integrates with the AvantGuard DNSFilter API to manage blocked URLs. Specifically, the "Blocked Urls Destroy" operation allows users to delete a blocked URL entry by specifying its unique identifier. This is useful in scenarios where you want to remove previously blocked URLs from your DNS filtering rules, for example, when a URL is no longer considered harmful or needs to be unblocked for business reasons.

Practical examples:

  • Removing a mistakenly blocked website from the DNS filter.
  • Cleaning up outdated or irrelevant blocked URL entries.
  • Dynamically managing blocked URLs based on changing security policies.

Properties

Name Meaning
Id The unique identifier of the blocked URL entry to delete. Required to specify which blocked URL to remove.
Additional Body Fields Optional additional fields to include in the request body. Currently supports:
- Blocked Url: A JSON object representing the URL filter resource to send along with the delete request.

Output

The node outputs JSON data representing the response from the AvantGuard DNSFilter API after attempting to delete the specified blocked URL. The exact structure depends on the API's response but typically includes confirmation of deletion or error details.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for AvantGuard DNSFilter service authentication.
  • Uses the base URL https://api.dnsfilter.com for API requests.
  • Depends on the @avantguardllc/n8n-openapi-node package and the bundled OpenAPI specification (openapi.json) for request building and execution.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent Id will likely result in an error from the API indicating that the resource was not found.
    • Malformed JSON in the "Blocked Url" additional field may cause request failures.
    • Missing or incorrect API credentials will prevent successful authentication.
  • Error messages:

    • "Resource not found" — Check that the Id corresponds to an existing blocked URL.
    • "Unauthorized" or "Authentication failed" — Verify that the API key credential is correctly configured.
    • "Invalid JSON" — Ensure that any JSON provided in the "Blocked Url" field is well-formed.

Links and References

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

Discussion