AvantGuard - SentinelOne

Actions682

Overview

This node operation fetches device control rules from the AvantGuard SentinelOne API using various optional query parameters to filter and paginate the results. It is useful for retrieving detailed device control policies, such as rules based on device IDs, names, classes, statuses, creation dates, and other attributes. Practical applications include auditing device control configurations, integrating device rule data into workflows, or monitoring device access policies.

Properties

Name	Meaning
Additional Query Parameters	A collection of optional filters and pagination controls to customize the device control rules retrieval. These include parameters like countOnly, limit, uids, deviceNames, ruleName, actions, createdAt timestamps, skip, cursor for pagination, sortBy, sortOrder, and many others to precisely filter the device rules returned by the API.

Output

JSON

data - Array of device control rule objects returned by the API, each containing detailed attributes of the device control rules matching the query parameters.
totalCount - Total number of device control rules matching the query, present if countOnly is used or pagination is enabled.
cursor - Cursor string for pagination to fetch the next set of results if more data is available.

Dependencies

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

Troubleshooting

If authentication fails, verify that the API key credential is correctly configured and has necessary permissions.
If no data is returned, check the filter parameters for correctness and ensure that matching device rules exist.
Pagination parameters like 'cursor' and 'skip' must be used correctly to iterate over large result sets.
Using 'countOnly' with other filters may return only the count without data; ensure this is intended.
Invalid date formats in 'createdAt' filters can cause errors; use ISO 8601 timestamps.
If the API returns rate limit errors, consider adding delays or reducing request frequency.