AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter

Actions277

Overview

This node integrates with the AvantGuard DNSFilter API to create scheduled policies. Scheduled policies allow users to define time-based rules for DNS filtering, such as blocking or allowing certain domains during specific times. This is useful in scenarios like enforcing internet usage policies in organizations based on time zones and schedules.

For example, an organization might want to block social media sites during work hours but allow them after hours. Using this node, you can programmatically create such scheduled policies by specifying policy IDs, time zones, and other relevant details.

Properties

Name Meaning
Additional Body Fields Optional fields to customize the scheduled policy creation request. Includes:
- Name The name of the scheduled policy.
- Organization Id Numeric ID representing the organization that owns the block page or policy.
- Policy Ids JSON array of policy IDs representing 15-minute blocks starting Monday morning 12:01am.
- Timezone Timezone string (e.g., "America/New_York") used to localize the policy schedule.

Output

The node outputs JSON data corresponding to the response from the AvantGuard DNSFilter API when creating a scheduled policy. This typically includes details about the newly created scheduled policy such as its ID, name, associated organization, policy blocks, and timezone settings.

No binary data output is indicated.

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 uses standard HTTP headers including Accept: application/json and Content-Type: application/json.

Troubleshooting

  • Invalid or missing API key: Ensure the API key credential is correctly configured in n8n; otherwise, authentication will fail.
  • Malformed JSON in Policy Ids: The policy_ids field expects a valid JSON array. Invalid JSON will cause errors. Validate JSON formatting before input.
  • Incorrect Timezone String: Use valid IANA timezone strings (e.g., "America/New_York"). Invalid timezones may cause unexpected behavior or API errors.
  • Missing Required Fields: Although some fields are optional, omitting necessary identifiers like organization ID or policy IDs may result in API errors.
  • API Rate Limits or Network Issues: Handle possible rate limiting or connectivity problems by implementing retries or error handling in workflows.

Links and References

Discussion