AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter

Actions277

Overview

This node operation, User Agent Cleanups Create, is designed to initiate a cleanup process for user agents associated with specified organizations. It targets user agents that have been inactive for a certain number of days and triggers their removal or cleanup based on the provided criteria. This can be particularly useful in scenarios where an organization wants to maintain up-to-date records by removing stale or unused user agent data, improving system performance and data relevance.

Practical examples:

  • Automatically cleaning up user agents that have not been active for over 90 days across multiple organizations.
  • Managing user agent data hygiene by periodically removing entries linked to deprecated or inactive organizations.

Properties

Name Meaning
Organization Ids A JSON array containing the list of Organization IDs for which the cleanup should apply.
Inactive For The number of days a user agent has been inactive; user agents inactive longer than this will be cleaned up.
Additional Body Fields Optional additional fields to include in the request body. Currently supports a deprecated single Organization ID field.

Output

The node outputs JSON data representing the result of the cleanup creation request. This typically includes confirmation details such as status, identifiers of affected entities, or error messages if the operation fails. There is no indication that binary data is output by this node.

Dependencies

  • Requires an API key credential for authentication with the external service managing user agent cleanups.
  • The node sends HTTP requests with JSON bodies to the relevant API endpoint.
  • No other external dependencies are indicated in the provided source code.

Troubleshooting

  • Common issues:

    • Providing invalid or empty Organization IDs may cause the API to reject the request.
    • Setting Inactive For to zero or a negative number might lead to unexpected behavior or errors.
    • Using the deprecated single Organization ID field instead of the new list format could cause warnings or failures depending on API version.
  • Error messages:

    • Errors related to authentication failure indicate missing or incorrect API credentials.
    • Validation errors from the API may occur if required properties are missing or malformed.
  • Resolutions:

    • Ensure the Organization Ids property contains a valid JSON array of numeric IDs.
    • Verify the Inactive For value is a positive integer.
    • Use the updated Organization Ids property rather than the deprecated single ID field.
    • Confirm that the API key credential is correctly configured in n8n.

Links and References

  • No direct links were found in the provided source code or properties. For more information, consult the API documentation of the service managing user agent cleanups or the n8n community forums for usage examples.

Discussion