AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter

Actions277

Overview

This node operation performs a bulk update of allowed URLs associated with a specific policy in the AvantGuard DNSFilter system. It is useful for administrators who need to efficiently modify multiple URL filters at once, such as updating notes, changing types, or enabling/disabling certain URLs within a security policy.

Practical examples include:

  • Updating a batch of allowed URLs to change their filtering type (e.g., from "url" to "domain").
  • Adding or modifying notes on multiple URL filters simultaneously.
  • Excluding certain URLs from updates while applying changes to others based on search criteria.

Properties

Name Meaning
Policy Id The identifier of the policy to which the allowed URLs belong.
Additional Query Parameters Optional filters for the bulk update request:
- Search: Search string applied to fields like value and note.
- Type: Filter by URL filter type; valid options are url, pattern, domain, tld.
Additional Body Fields Optional body parameters for the bulk update:
- Ids: JSON array of specific URL filter IDs to update, overriding any filters.
- Exclude Ids: JSON array of URL filter IDs to exclude from the update when using filters.
- Changeset: JSON object describing the changes to apply to the selected URL filters.

Output

The node outputs JSON data representing the response from the bulk update API call. This typically includes details about the updated URL filters, confirmation of changes applied, or error information if the update failed.

No binary data output is indicated.

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 in n8n is necessary.

Troubleshooting

  • Common issues:
    • Invalid or missing Policy Id will cause the API request to fail.
    • Malformed JSON in the Ids, Exclude Ids, or Changeset fields can lead to parsing errors.
    • Using unsupported types in the Type query parameter may result in no matching URL filters being updated.
  • Error messages:
    • Authentication errors indicate problems with the API key credential setup.
    • Validation errors from the API may specify which fields are incorrect or missing.
  • Resolutions:
    • Ensure the Policy Id is correct and exists.
    • Validate JSON syntax before inputting it into the node.
    • Confirm that the API key credential is correctly configured and has sufficient permissions.

Links and References

Discussion