AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter

Actions277

Overview

This node operation allows bulk deletion of allowed URLs associated with a specific policy in the AvantGuard DNSFilter system. It is useful for administrators who want to efficiently remove multiple URL filters at once, rather than deleting them individually. Common scenarios include cleaning up outdated or irrelevant allowed URLs, enforcing updated security policies, or managing large sets of URL exceptions.

For example, an admin might use this node to delete all allowed URLs of a certain type (e.g., domain or pattern) that are no longer needed, or to remove specific URLs by their IDs in bulk.

Properties

Name Meaning
Policy Id The unique identifier of the policy to which the allowed URLs belong. Required to specify the target policy.
Additional Query Parameters Optional filters to narrow down which allowed URLs to delete:
- Search: Text search on fields like value and note.
- Type: Filter by URL type; valid options are url, pattern, domain, tld.
Additional Body Fields Optional body parameters to control deletion:
- Ids: JSON array of specific URL filter IDs to delete, overriding other filters.
- Exclude Ids: JSON array of URL filter IDs to exclude from deletion when using filters.

Output

The node outputs JSON data representing the result of the bulk delete operation. This typically includes confirmation of which allowed URLs were deleted or any relevant status messages returned by the API. There is no binary data output.

Dependencies

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

Troubleshooting

  • Missing or invalid Policy Id: The operation requires a valid policy ID. Ensure the policy ID is correct and exists in the system.
  • Invalid JSON in Ids or Exclude Ids: When specifying IDs as JSON arrays, ensure the JSON syntax is correct to avoid parsing errors.
  • API Authentication Errors: If the API key is missing, expired, or incorrect, the node will fail to authenticate. Verify the API credentials.
  • No URLs matched for deletion: If filters are too restrictive or IDs do not exist, no URLs may be deleted. Adjust filters or verify IDs.
  • Network or API downtime: Temporary connectivity issues can cause failures. Retry after some time or check network settings.

Links and References

Discussion