AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter

Actions277

Overview

This node operation, User Agent Bulk Updates Counts, is designed to retrieve counts of user agents based on various filtering criteria. It is useful in scenarios where you need aggregated statistics about user agents in bulk, such as monitoring the number of active or offline agents, filtering by policy, network, or tags, and analyzing agent states or traffic activity.

Practical examples include:

  • Getting a count of all online user agents filtered by a specific policy ID.
  • Counting user agents that have received traffic in the last 15 minutes.
  • Filtering user agents by their release channel or block page ID to understand distribution or compliance.

Properties

Name Meaning
Additional Query Parameters Optional filters to refine the user agent count query. These include:
- Agent State Filter by agent state. Options: Protected, Unprotected, Bypassed, Uninstalled.
- Block Page Id Filter user agents by block page ID (number).
- Name Search Search term for client name fields like hostname or friendly name (string).
- Network Ids JSON array of network IDs to filter by; defaults to all networks.
- Organization Id Organization ID to filter user agents (number).
- Policy Id Filter user agents by policy ID (number).
- Release Channels JSON object to filter by release channels. Valid values: stable, beta, preview.
- Scheduled Policy Id Filter user agents by scheduled policy ID (number).
- Search Keyword(s) to search user agents by hostname or friendly name (string).
- State Filter by user agent online/offline state. Options: Online, Offline.
- Status Filter by user agent status. Valid attributes: active, disabled, uninstalled (string).
- Tags JSON array of tags to filter user agents by.
- Traffic Received Last 15 Mins Boolean filter for agents that have received traffic in the last 15 minutes.
- Type User agent type filter. Options: Proxy, Agents. Defaults to proxy.

Output

The output of this operation is a JSON object containing counts of user agents matching the specified filters. The exact structure depends on the API response but typically includes numeric counts grouped by relevant categories such as agent state, status, or other queried parameters.

There is no indication that this node outputs binary data.

Dependencies

  • Requires an API key credential for authentication with the external service managing user agents.
  • The node uses HTTP requests to communicate with the external API endpoint.
  • Proper configuration of the API base URL and authentication headers is necessary.

Troubleshooting

  • Common Issues:

    • Incorrect or missing API credentials will cause authentication failures.
    • Invalid filter values (e.g., non-existent policy IDs or malformed JSON arrays) may result in errors or empty results.
    • Network connectivity issues can prevent successful API calls.
  • Error Messages:

    • Authentication errors typically indicate invalid or missing API keys; verify credentials.
    • Validation errors suggest incorrect parameter formats; check property types and allowed values.
    • Timeout or connection errors require checking network access and API availability.

Links and References

  • Refer to the external API documentation for detailed descriptions of each filter parameter and expected response format.
  • Consult n8n documentation on how to configure API credentials and use collection-type input properties effectively.

Discussion