AvantGuard - SentinelOne icon

AvantGuard - SentinelOne

AvantGuard - SentinelOne

Actions682

Overview

This node performs governance actions on assets within a datalake inventory system via a web API POST request. It allows users to execute various predefined actions such as exporting resource details, updating asset criticality levels, managing asset contacts, applying reviews, and manipulating tags on selected assets. The node is useful for automating asset governance workflows, filtering assets based on complex query parameters, and managing asset metadata in bulk.

Properties

Name Meaning
Additional Query Parameters Optional filters to refine the selection of assets for the governance action. These include filters on cloud provider details, regions, coverage status, tags, risk factors, asset status, and many other asset attributes. Each filter corresponds to a query parameter sent with the API request.
Action Name Specifies the governance action to perform on the selected assets. Actions include exporting details, marking asset criticality levels, updating or clearing asset contacts, applying reviews, adding notes, and managing tags (add, remove, replace, clear).
Additional Body Fields Optional additional fields to include in the request body, such as lists of inventory IDs to include or exclude from the action.

Output

JSON

  • response - The JSON response from the API after performing the governance action, containing details about the result of the action.

Dependencies

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

Troubleshooting

  • Ensure the API credentials are correctly configured and have sufficient permissions to perform governance actions.
  • Verify that the 'Action Name' selected is supported and correctly spelled.
  • Check that any JSON input fields (e.g., filters) are valid JSON arrays or objects as expected.
  • If the API returns errors about invalid filters, review the query parameters for unsupported or malformed values.
  • Network connectivity issues may prevent the node from reaching the API endpoint; verify network access and base URL configuration.
  • Large payloads or complex filters may cause timeouts; consider simplifying filters or batching requests.

Discussion