AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter

Actions277

Overview

This node updates a Scheduled Policy in the AvantGuard DNSFilter system. It allows users to modify properties of an existing scheduled policy by specifying its ID and optionally updating fields such as the policy's name, associated organization, policy IDs representing time blocks, and timezone localization.

Common scenarios for this node include automating changes to network filtering schedules, adjusting policies based on organizational needs, or synchronizing scheduled policies with external systems.

For example, a user might update the name and timezone of a scheduled policy to reflect a new business location's working hours or adjust the policy IDs to change which time blocks are active.

Properties

Name Meaning
Id The unique identifier (ID) of the Scheduled Policy to update.
Additional Body Fields Optional fields to update on the Scheduled Policy:
- Name New name for the Scheduled Policy.
- Organization Id Numeric ID of the organization that owns the block page.
- Policy Ids JSON array of numeric IDs representing 15-minute blocks starting Monday 12:01 AM (e.g., schedule).
- Timezone Timezone string (e.g., "America/New_York") used to localize the policy times.

Output

The node outputs JSON data representing the updated Scheduled Policy object returned from the API after the update operation. This typically includes all current properties of the Scheduled Policy reflecting the applied changes.

No binary data output is involved.

Dependencies

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

Troubleshooting

  • Invalid ID error: If the provided Scheduled Policy ID does not exist or is incorrect, the API will return an error. Verify the ID before running the node.
  • Malformed JSON in Policy Ids: The policy_ids field expects a valid JSON array. Ensure the input is correctly formatted JSON; otherwise, parsing errors may occur.
  • Authentication failures: Ensure the API key credential is valid and has sufficient permissions to update scheduled policies.
  • Timezone format issues: Use valid timezone strings recognized by the API (e.g., "America/New_York"). Invalid values may cause errors or unexpected behavior.

Links and References

Discussion