AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter

Actions277

Overview

The node provides an operation to delete (destroy) a scheduled policy by its unique identifier. This is useful in scenarios where automated or scheduled policies need to be programmatically removed from the system, such as cleaning up outdated rules or managing policy lifecycle dynamically.

For example, if you have scheduled policies that enforce certain network or security rules at specific times, and you want to remove one of these policies based on some condition or event, this node operation allows you to do so by specifying the policy's ID.

Properties

Name Meaning
Id The unique identifier of the Scheduled Policy to be deleted. This is a required numeric value representing the ScheduledPolicy ID.

Output

The output JSON structure is not explicitly detailed in the provided code snippet. However, typically for a destroy/delete operation, the output would include confirmation of deletion, such as a success status or the ID of the deleted policy.

If the node supports binary data output, it is not indicated here, so it can be assumed the output is purely JSON-based with information about the deletion result.

Dependencies

  • Requires an API key credential for authentication with the external service.
  • The node uses a base URL https://api.dnsfilter.com indicating it interacts with the AvantGuard DNSFilter API.
  • The node depends on the @avantguardllc/n8n-openapi-node package for building properties and handling OpenAPI specifications.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent ScheduledPolicy ID will likely result in an error from the API indicating the resource was not found.
    • Missing or incorrect API credentials will cause authentication failures.
    • Network connectivity issues may prevent the node from reaching the API endpoint.
  • Error messages:

    • "ScheduledPolicy not found" or similar indicates the specified ID does not exist.
    • Authentication errors suggest checking the API key or credential configuration.
    • Timeout or connection errors require verifying network access and API availability.

Links and References

Discussion