AvantGuard - SentinelOne

Actions682

Overview

This node operation retrieves location data from the AvantGuard SentinelOne API using a web API GET request. It supports extensive filtering and pagination options, allowing users to query locations based on various criteria such as name, description, IP address, group IDs, and more. This is useful for workflows that need to integrate or analyze location information from SentinelOne, for example, to monitor network locations, audit firewall rules, or generate reports on site configurations.

Properties

Name	Meaning
Additional Query Parameters	A collection of optional query parameters to filter and control the retrieval of location data. These include filters like 'Count Only' to get only the total count, 'Limit' to restrict the number of returned items, text filters for description, name, hostname, IP address, and others, as well as pagination controls like 'Skip' and 'Cursor'. Sorting options and flags like 'Has Firewall Rules' are also supported.

Name

Meaning

Additional Query Parameters

A collection of optional query parameters to filter and control the retrieval of location data. These include filters like 'Count Only' to get only the total count, 'Limit' to restrict the number of returned items, text filters for description, name, hostname, IP address, and others, as well as pagination controls like 'Skip' and 'Cursor'. Sorting options and flags like 'Has Firewall Rules' are also supported.

Output

JSON

locations - An array of location objects matching the query parameters.
totalCount - The total number of matching locations, if requested.
cursor - Cursor token for pagination to retrieve the next set of results.

Dependencies

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

Troubleshooting

If the API returns authentication errors, verify that the API key credential is correctly configured and has necessary permissions.
When using pagination parameters like 'cursor' or 'skip', ensure values are valid to avoid empty or repeated results.
Using 'countOnly' with other filters may return only the count without data; ensure this matches the intended use.
Invalid filter values (e.g., malformed JSON arrays) can cause API errors; validate input formats before execution.
If the node returns no results, check that the filter criteria are not too restrictive or conflicting.