AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter
Join our community

Actions277

Overview

This node performs bulk updates on user agents within a system, allowing users to filter and select multiple user agents based on various criteria and then apply changes to them collectively. It is particularly useful in scenarios where administrators need to update configurations, tags, release channels, or other attributes for many user agents at once without manually editing each one.

Practical examples include:

  • Updating the tags of all user agents that are currently online and running a specific agent version.
  • Changing the release channel for a group of user agents filtered by organization or policy.
  • Excluding certain user agents by ID while applying updates to the rest matching given filters.

Properties

Name Meaning
Additional Query Parameters Optional filters to narrow down which user agents to target. Includes:
- Agent State (protected, unprotected, bypassed, uninstalled)
- Agent Version (string)
- Block Page Id (number)
- Name Search (hostname or friendly name)
- Network Ids (array)
- Organization Id / Ids (number or array)
- Policy Id (number)
- Policy Schedule (string)
- Release Channels (JSON array; e.g., stable, beta, preview)
- Scheduled Policy Id (number)
- Search (keyword(s) for hostname/friendly name)
- State (online/offline)
- Status (active, disabled, uninstalled)
- Tags (array)
- Traffic Received Last 15 Mins (boolean)
- Type (proxy or agents)
Additional Body Fields Optional fields to specify details of the bulk update:
- Ids (array): Specific user agent IDs to update, overrides filters
- Exclude Ids (array): User agent IDs to exclude from update when using filters
- Changeset (JSON): The actual changes to apply, such as updated tags or release channels

Output

The node outputs JSON data representing the result of the bulk update operation. This typically includes information about which user agents were updated and the status of the update request. The exact structure depends on the API response but generally confirms success or failure and may list affected user agent IDs.

If binary data is returned (not indicated here), it would represent downloadable content related to the update, but this node primarily deals with JSON responses.

Dependencies

  • Requires an API key credential for authenticating requests to the external service managing user agents.
  • The node sends HTTP requests to a predefined base URL endpoint (not explicitly shown in the snippet but implied by routing).
  • No additional external libraries beyond standard n8n dependencies and the bundled OpenAPI client are required.

Troubleshooting

  • Common Issues:

    • Incorrect or missing API authentication token will cause authorization errors.
    • Providing invalid filter values (e.g., malformed JSON arrays or unsupported option values) can lead to request failures.
    • Specifying conflicting parameters, such as both ids and filters, might cause unexpected behavior since ids override filters.

  • Error Messages:

    • Authorization errors: Check that the API key credential is correctly configured and has necessary permissions.
    • Validation errors: Ensure all JSON inputs (like ids, exclude_ids, changeset) are properly formatted.
    • Empty results or no updates: Verify that filters match existing user agents and that the changeset contains valid update instructions.

Links and References

  • Refer to the official API documentation of the user agent management service for detailed descriptions of query parameters and body fields.
  • n8n documentation on creating and using custom nodes with collections and JSON input types.
  • General best practices for bulk update operations in API-driven environments.

Discussion