AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter

Actions277

Overview

The node integrates with the AvantGuard DNSFilter API to perform bulk updates on blocked URLs associated with a specific policy. This operation is useful for administrators managing web filtering policies who need to update multiple URL filters at once, such as changing notes, types, or other attributes of blocked URLs in bulk.

Practical examples include:

  • Updating the status or notes of multiple blocked URLs under a given policy.
  • Filtering which URLs to update based on search criteria or type before applying changes.
  • Excluding certain URLs from the bulk update by specifying their IDs.

Properties

Name Meaning
Policy Id The numeric ID of the policy to which the blocked URLs belong.
Additional Query Parameters Optional filters to narrow down which blocked URLs to update:
- Search: Search string applied to fields like value and note.
- Type: Filter by type; valid options are url, pattern, domain, tld.
Additional Body Fields Optional JSON fields to customize the bulk update request body:
- Ids: JSON array of URL filter IDs to update directly (overrides filters).
- Exclude Ids: JSON array of URL filter IDs to exclude 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 AvantGuard DNSFilter API after performing the bulk update. This typically includes details about the updated URL filters, confirmation of changes applied, or any errors encountered.

No binary data output is involved.

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 key credential within n8n is necessary for successful authentication.

Troubleshooting

  • Common issues:

    • Invalid or missing Policy Id will cause the API call to fail.
    • Malformed JSON in the "Ids", "Exclude Ids", or "Changeset" fields can lead to parsing errors.
    • Using invalid filter types in the query parameters may result in no matches or API errors.
    • Network or authentication failures if the API key is incorrect or expired.
  • Error messages:

    • Authentication errors usually indicate problems with the API key credential setup.
    • Validation errors from the API may point to incorrect JSON structure or invalid field values.
  • Resolutions:

    • Verify that the Policy Id is correct and exists.
    • Ensure JSON inputs are properly formatted.
    • Confirm the API key credential is correctly configured and active.
    • Use valid filter types (url, pattern, domain, tld) when applying filters.

Links and References

Discussion