AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter

Actions277

Overview

This node integrates with the AvantGuard DNSFilter API to create allowed URLs under a specified policy. It is useful for managing web filtering policies by programmatically adding URLs that should be permitted through the DNS filter. Typical use cases include automating whitelist management in security or network administration workflows, where administrators want to allow specific URLs dynamically based on changing requirements.

For example, an organization might use this node to add new trusted domains to their DNS filtering policy whenever a new vendor or partner site needs to be accessible to employees.

Properties

Name Meaning
Additional Body Fields Optional fields to include in the request body when creating allowed URLs. Includes:
- Policy Id The numeric ID of the policy under which the allowed URLs will be created.
- Allowed Urls A JSON array representing the list of URLs to be added as allowed URLs in the policy.

The "Additional Body Fields" property allows users to specify the policy_id and a list of allowed_urls in JSON format. This flexibility lets users customize the request payload sent to the API.

Output

The node outputs JSON data representing the response from the AvantGuard DNSFilter API after creating the allowed URLs. This typically includes confirmation details such as the created URLs, their IDs, and any metadata returned by the API.

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 Policy Id: If the provided policy ID does not exist or is incorrect, the API may return an error. Verify the policy ID before running the node.
  • Malformed Allowed URLs JSON: The allowed_urls field expects valid JSON. Errors in JSON formatting will cause the request to fail. Use proper JSON syntax.
  • Authentication Errors: Ensure the API key credential is correctly configured and has sufficient permissions.
  • API Rate Limits: Frequent calls may hit rate limits imposed by the API. Implement retries or backoff strategies if needed.

Links and References

Discussion