AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter

Actions277

Overview

This node interacts with the Policies resource of an external service, specifically performing the "Policies Application" operation. It is designed to query policies related to a particular application within an organization. This can be useful in scenarios where you need to retrieve policy details by specifying an application ID, organization ID, and filtering by policy names or IDs.

Practical examples include:

  • Fetching all policies applied to a specific application for auditing or compliance checks.
  • Searching for policies by name or partial name within an organization's context.
  • Retrieving detailed information about selected policies by their IDs.

Properties

Name Meaning
Application Id The unique identifier of the application whose policies are being queried.
Name The full or partial name of a policy to filter the query results.
Organization Id The unique identifier of the organization that owns the application and policies.
Policy Ids A JSON array containing one or more policy IDs to specifically target certain policies.

Output

The node outputs JSON data representing the policies matching the query parameters. The structure typically includes details about each policy such as its ID, name, description, and any other metadata provided by the external service's API.

If binary data were involved (e.g., policy documents or attachments), it would be included in a separate binary output field, but based on the code and properties, this node primarily deals with JSON data.

Dependencies

  • Requires an API key credential for authenticating requests to the external Policies service.
  • The base URL for API requests is set to https://api.dnsfilter.com as per the bundled source code.
  • The node depends on an OpenAPI client library (@avantguardllc/n8n-openapi-node) to build and execute requests.
  • Proper configuration of credentials and network access to the external API endpoint is necessary.

Troubleshooting

  • Missing or invalid API credentials: Ensure that the API key credential is correctly configured and has sufficient permissions.
  • Invalid input parameters: Verify that Application Id, Organization Id, and Policy Ids are provided and correctly formatted. For example, Policy Ids must be a valid JSON array.
  • Network issues or API downtime: Check connectivity to https://api.dnsfilter.com and confirm the external service is operational.
  • Empty or no results returned: Confirm that the specified application, organization, and policy filters actually exist and match records in the external system.

Links and References

Discussion