AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter

Actions277

Overview

This node operation updates the policy settings for a specific application within an organization. It allows users to specify which policies should be allowed and which should be blocked on that application. This is useful in scenarios where administrators want to control access or restrictions applied to applications by managing their associated policies dynamically.

Practical examples include:

  • Enabling certain security or compliance policies for an application while disabling others.
  • Adjusting policy enforcement when onboarding new applications or changing organizational requirements.
  • Automating policy updates across multiple applications in an enterprise environment.

Properties

Name Meaning
Allow Policies List of Policy IDs to be explicitly allowed on the specified application.
Application Id Numeric identifier of the application whose policies are being updated.
Block Policies List of Policy IDs to be explicitly blocked on the specified application.
Organization Id Numeric identifier of the organization to which the application belongs.

Output

The node outputs JSON data representing the result of the policy update operation. This typically includes confirmation of the updated policies, status messages, or any relevant metadata returned from the API after applying the changes.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating with the AvantGuard DNSFilter service.
  • The node communicates with the DNSFilter API endpoint at https://api.dnsfilter.com.
  • Proper configuration of the API authentication credentials in n8n is necessary for successful execution.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Providing incorrect or non-existent Policy IDs or Application/Organization IDs may result in errors or no changes applied.
    • Improperly formatted JSON arrays for allow/block policies can cause request failures.
  • Error messages and resolutions:

    • Authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
    • Validation errors: Ensure all required fields (application_id, organization_id, allow_policies, block_policies) are provided and correctly formatted.
    • API response errors: Check network connectivity and API service status; review the API documentation for limits or constraints.

Links and References

Discussion