AvantGuard - SentinelOne icon

AvantGuard - SentinelOne

AvantGuard - SentinelOne

Actions682

Overview

This node operation retrieves the status of remote operation scripts from a web API. It allows users to query and filter remote script execution tasks based on various criteria such as creation date, update date, status, type, and other metadata. This is useful for monitoring and managing remote scripts executed on agents or computers in an IT environment, enabling automation workflows to track script execution results and statuses.

Properties

Name Meaning
Additional Query Parameters A collection of optional query parameters to filter and control the results returned by the API. These include filters like countOnly (to return only the count of items), limit (number of items to return), type, query string, date filters (createdAt, updatedAt), text filters (description, computer name, initiated by), pagination controls (skip, cursor), sorting options (sortBy, sortOrder), and various ID filters (groupIds, accountIds, siteIds, parentTaskId, etc.). These parameters allow fine-grained control over which remote script statuses are retrieved.

Output

JSON

  • items - An array of remote script status objects matching the query parameters.
  • count - Total number of matching items, if countOnly or skipCount is used.
  • cursor - Cursor string for pagination to fetch the next set of results.

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

  • If the node returns authentication errors, verify that the API key credential is correctly configured and has sufficient permissions.
  • If no results are returned, check the query parameters for correctness and ensure that the filters match existing remote script statuses.
  • Pagination issues may occur if the cursor parameter is not used properly; ensure to use the cursor returned from previous requests to paginate beyond 1000 items.
  • Large result sets may cause timeouts; use filters like limit, skip, or countOnly to reduce data volume.
  • Invalid date formats in createdAt or updatedAt filters can cause errors; use ISO 8601 format (e.g., '2018-02-27T04:49:26.257525Z').

Links

Discussion