AvantGuard - DNSFilterInstall

Overview

This node allows users to delete ("destroy") specific allowed URLs from a DNS filtering service's configuration. It is useful in scenarios where you want to programmatically remove URLs that were previously whitelisted or allowed through the DNS filter, for example, when cleaning up outdated exceptions or enforcing updated security policies.

A practical example would be an automated workflow that removes access to certain URLs after a project ends or when a URL is identified as malicious and should no longer be accessible.

Properties

• The "Additional Body Fields" property lets you add optional data to the deletion request, such as detailed URL filters in JSON format.

Output

The node outputs JSON data representing the response from the API after attempting to delete the specified allowed URL. This typically includes confirmation of deletion or error details if the operation failed.

No binary data output is involved.

Dependencies

• Requires an API key credential for authenticating with the AvantGuard DNSFilter API.
• The base URL for API requests is https://api.dnsfilter.com.
• The node depends on the @avantguardllc/n8n-openapi-node package and an OpenAPI specification (openapi.json) bundled within the node implementation.

Troubleshooting

• Common issues:

  • Providing an invalid or non-existent Id will likely result in an error indicating the resource was not found.
  • Malformed JSON in the "Allowed Url" additional field may cause request parsing errors.
  • Missing or incorrect API credentials will lead to authentication failures.

• Error messages:

  • "Resource not found" or similar indicates the Id does not correspond to any existing allowed URL.
  • "Invalid JSON" errors suggest the JSON input in additional fields is malformed.
  • Authentication errors require checking the API key credential setup.

Links and References

• AvantGuard DNSFilter API Documentation (general reference)
• n8n documentation on creating custom nodes