AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter

Actions277

Overview

This node operation allows you to add an allowed application to a specific policy within the Policies resource. It is useful in scenarios where you want to whitelist or permit certain applications under a given policy, for example, to ensure that trusted applications are not blocked by security or filtering rules.

Practical examples include:

  • Adding a business-critical application to a network security policy to prevent it from being inadvertently blocked.
  • Whitelisting a new software tool in an organization's access control policy.

Properties

Name Meaning
Id The unique identifier of the policy to which the application will be added (Policy ID).
Name The name of the application to be allowed under the specified policy.
Additional Body Fields Optional additional fields to customize the request:
- Include Relationships Boolean flag indicating whether to include relationships in the response (true/false). Defaults to true.

Output

The node outputs JSON data representing the updated policy with the newly added allowed application. If the "Include Relationships" option is enabled, the output will also contain related entities linked to the policy.

No binary data output is expected from this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the external service managing policies.
  • The node sends HTTP requests to the service's API endpoint (base URL: https://api.dnsfilter.com).
  • Proper configuration of the API authentication credential in n8n is necessary.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent Policy ID may result in errors or no changes.
    • Omitting required properties like the application name or policy ID will cause the node to fail.
    • Network connectivity problems or incorrect API credentials can lead to authentication failures.
  • Error messages and resolutions:

    • "Policy not found" — Verify that the Policy ID is correct and exists.
    • "Unauthorized" or "Authentication failed" — Check that the API key credential is correctly configured and valid.
    • "Invalid input" — Ensure all required fields are provided and properly formatted.

Links and References

Discussion