AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter

Actions277

Overview

This node operation performs bulk deletion of user agents based on various filter criteria or explicit IDs. It is useful in scenarios where an administrator needs to clean up or remove multiple user agents from a system efficiently, such as removing inactive, uninstalled, or otherwise unwanted agents in one request.

Practical examples include:

  • Deleting all user agents that are offline or uninstalled.
  • Removing user agents filtered by specific policies, tags, or network IDs.
  • Bulk uninstalling agents matching certain version or state criteria.

Properties

Name Meaning
Additional Query Parameters Optional filters to narrow down which user agents to delete. Includes options like Agent State (protected, unprotected, bypassed, uninstalled), Agent Version, Block Page Id, Name Search, Network Ids, Organization Id(s), Policy Id, Policy Schedule, Queue Uninstall (boolean), Release Channels (stable, beta, preview), Scheduled Policy Id, Search keywords, State (online/offline), Status (active, disabled, uninstalled), Tags, Traffic Received Last 15 Mins (boolean), and Type (proxy or agents). These parameters are sent as query parameters in the API request.
Additional Body Fields Optional body fields for the delete request. Includes:
- Ids: JSON array of specific user agent IDs to delete, which overrides any filters.
- Exclude Ids: JSON array of user agent IDs to exclude from deletion when using filters. These are sent in the request body.

Output

The node outputs JSON data representing the response from the bulk delete API call. This typically includes information about the success or failure of the deletion operation, such as counts of deleted user agents or error messages if applicable.

No binary data output is involved.

Dependencies

  • Requires an API key credential for authentication with the external service managing user agents.
  • The base URL for API requests is https://api.dnsfilter.com.
  • The node uses standard HTTP headers including Accept: application/json and Content-Type: application/json.

Troubleshooting

  • Common issues:
    • Providing invalid or malformed JSON arrays in the "Ids" or "Exclude Ids" fields may cause request failures.
    • Using conflicting filters or specifying both IDs and filters might lead to unexpected results since IDs override filters.
    • Missing or incorrect API credentials will result in authentication errors.
  • Error messages:
    • Authentication errors indicate missing or invalid API keys; verify credentials configuration.
    • Validation errors may occur if query parameters or body fields have invalid values; ensure correct types and formats.
    • Network or timeout errors suggest connectivity issues; check network access and API availability.

Links and References

Discussion