AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter

Actions277

Overview

This node interacts with the "Agent Local User Bulk Deletes" resource, specifically performing the operation to retrieve counts related to bulk delete actions of local users on agents. It is useful in scenarios where you need to monitor or report on how many bulk delete operations have been performed or their status counts. For example, an administrator might use this node to track the number of bulk deletions processed for auditing or compliance purposes.

Properties

Name Meaning
Id The unique identifier of the agent local user bulk delete record for which you want to retrieve count information. This is a required numeric field.

Output

The node outputs JSON data containing the counts related to the specified bulk delete operation identified by the provided Id. The exact structure depends on the API response but typically includes fields representing various count metrics (e.g., total deletes, successful deletes, failed deletes). There is no indication that binary data is output by this node.

Dependencies

  • Requires an API key credential for authentication with the external service.
  • The node uses a base URL pointing to https://api.dnsfilter.com.
  • The node depends on an OpenAPI-based client library (@avantguardllc/n8n-openapi-node) and a local OpenAPI specification file (openapi.json).

Troubleshooting

  • Missing or invalid Id: Since the Id property is required, omitting it or providing an invalid value will likely cause errors. Ensure the Id is a valid number corresponding to an existing bulk delete record.
  • Authentication errors: If the API key credential is missing or invalid, the node will fail to authenticate with the external service. Verify that the correct API key is configured.
  • Network or API errors: Connectivity issues or API downtime can cause failures. Check network connectivity and the status of the external service.
  • Unexpected API responses: If the API changes or returns unexpected data, the node may not parse the output correctly. Review API documentation or update the node accordingly.

Links and References

Discussion