AvantGuard - SentinelOne icon

AvantGuard - SentinelOne

AvantGuard - SentinelOne

Actions682

Overview

This node performs a POST request to the Datalake Inventory Account API endpoint to retrieve or manipulate asset account data based on complex filtering criteria. It is useful for users who need to query cloud asset inventories with detailed filters such as account IDs, group IDs, site IDs, asset status, coverage, tags, and other metadata. For example, security analysts can use this node to fetch active cloud assets with critical risk factors or to filter assets by specific organizational units or regions.

Properties

Name Meaning
Additional Query Parameters Optional query parameters to further filter the request, including lists of Account IDs, Group IDs, and Site IDs.
Filter A required JSON object defining detailed filtering criteria for the asset accounts, including fields like cloud provider organization, region exclusions, coverage status, asset status, tags, risk factors, device review status, and pagination controls such as limit and skip.
Additional Body Fields Optional additional JSON fields to include in the request body, allowing for extended customization of the POST payload.

Output

JSON

  • response - The JSON response from the API containing the filtered list of asset accounts or related data as per the POST request.

Dependencies

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

Troubleshooting

  • Ensure the 'Filter' JSON is correctly formatted and valid; invalid JSON will cause request failures.
  • Verify that the API credentials (baseURL and API key) are correctly configured and have sufficient permissions.
  • If the response is empty or incomplete, check that the filter criteria are not overly restrictive or conflicting.
  • Network connectivity issues or incorrect baseURL settings can cause request timeouts or connection errors.
  • Large result sets may require adjusting pagination parameters like 'limit' and 'skip' to avoid timeouts.

Discussion