AvantGuard - CIPP icon

AvantGuard - CIPP

AvantGuard - CIPP

Actions136

Overview

This node interacts with the AvantGuard CIPP API to retrieve detailed information about a specific security incident from a list resource. It is designed to query and fetch exec set security incident data based on multiple filtering criteria such as assignment, classification, determination, status, and others.

Typical use cases include:

  • Automating the retrieval of security incident details for further processing or alerting.
  • Integrating security incident data into workflows for compliance reporting or incident management.
  • Filtering incidents dynamically by various attributes to focus on relevant cases.

For example, a security operations team could use this node to automatically pull incidents assigned to a particular user with a certain classification and status, enabling targeted follow-up actions.

Properties

Name Meaning
Assigned Filter incidents by the assigned person or entity.
Classification Filter incidents by their classification type.
Determination Filter incidents by the determination status or outcome.
Guid Unique identifier (GUID) of the specific security incident to retrieve.
Redirected Filter incidents based on whether they have been redirected.
Status Filter incidents by their current status.
Tenantfilter Filter incidents by tenant or organizational scope.

All these properties are required string inputs that are sent as query parameters in the API request to filter the results accordingly.

Output

The node outputs JSON data representing the retrieved security incident(s) matching the specified filters. The structure corresponds directly to the API response, typically including fields such as incident details, metadata, status, classification, and related attributes.

If the API supports binary data (e.g., attachments), it would be included in the output's binary field; however, based on the provided code and properties, the primary output is JSON-formatted incident data.

Dependencies

  • Requires an API key credential for authenticating with the AvantGuard CIPP API.
  • Needs the base URL of the AvantGuard resource API configured in the node credentials.
  • Depends on the @avantguardllc/n8n-openapi-node package for building request properties and handling API communication.
  • The node uses OpenAPI specifications defined in openapi.json to construct requests.

Troubleshooting

  • Missing or invalid API credentials: Ensure the API key and base URL are correctly configured in the node credentials.
  • Required properties not set: All listed properties are mandatory; missing any will cause the request to fail.
  • Incorrect property values: Providing invalid or mismatched filter values may result in empty responses or errors.
  • Network or API errors: Check connectivity and API availability if requests time out or return server errors.
  • Unexpected response format: If the API changes, the node might not parse the response correctly; verify API version compatibility.

Links and References

Discussion