AvantGuard - SentinelOne icon

AvantGuard - SentinelOne

AvantGuard - SentinelOne

Actions682

Overview

This node operation allows users to create or update an Auto Upgrade Policy via a web API POST request. It is useful for managing upgrade policies programmatically, such as setting activation times, retry limits, scope, and other policy details. For example, an IT administrator can automate the deployment of upgrade policies across different operating systems and scopes by configuring this node in an automation workflow.

Properties

Name Meaning
Activated At Timestamp indicating when the upgrade policy becomes active.
All Endpoints Boolean flag to specify if the policy applies to all endpoints.
Created At Timestamp indicating when the policy was created.
Description Text description of the upgrade policy.
Id Unique identifier of the upgrade policy.
Is Active Boolean flag indicating if the policy is currently active.
Is Scheduled Boolean flag indicating if the policy is scheduled for execution.
Max Retries Maximum number of retry attempts for the upgrade.
Name Name of the upgrade policy.
Os Type Operating system type to which the policy applies.
Package JSON object defining the package details for the upgrade.
Priority Priority level of the upgrade policy.
Scope Id Identifier for the scope of the policy.
Scope Level Level of scope (e.g., global, local) for the policy.
Tags JSON array of tags associated with the policy.
Updated At Timestamp indicating when the policy was last updated.

Output

JSON

  • response - The JSON response from the API after creating or updating the upgrade policy, containing details of the policy.

Dependencies

  • Requires an API key credential for authentication to the AvantGuard SentinelOne API.
  • Depends on the '@avantguardllc/n8n-openapi-node' package for OpenAPI integration.

Troubleshooting

  • Ensure the API credentials are correctly configured and have sufficient permissions to create or update upgrade policies.
  • Verify that all required fields are provided and correctly formatted, especially JSON fields like 'package' and 'tags'.
  • If the API returns authentication errors, check the validity and scope of the API key.
  • Network connectivity issues may cause request failures; ensure the base URL is reachable.
  • Malformed JSON in 'package' or 'tags' fields can cause parsing errors; validate JSON syntax before sending.

Discussion