AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node interacts with the AvantGuard ConnectSecure API to retrieve Endpoint Detection and Response (EDR) data. Specifically, the "Get Retrieve Edr" operation fetches EDR records based on user-supplied criteria. This is useful in cybersecurity workflows where automated retrieval of endpoint security events or alerts is needed for monitoring, analysis, or incident response.

Practical examples include:

  • Automatically fetching recent EDR alerts for a specific user to trigger further investigation.
  • Querying EDR logs with filters such as conditions, pagination (skip/limit), and sorting order.
  • Integrating EDR data into dashboards or SIEM systems via n8n workflows.

Properties

Name Meaning
X USER ID The User Id header value identifying the user context for which to retrieve EDR data.
Additional Query Parameters Optional query parameters to refine the request:
- Condition: Query filter condition string.
- Skip: Number of records to skip (pagination).
- Limit: Maximum number of records to return.
- Order By: Field(s) to sort the results by.

Output

The node outputs JSON data representing the retrieved EDR records matching the query parameters. The structure corresponds to the API's response schema for EDR data, typically including details about detected threats, timestamps, affected endpoints, and other relevant metadata.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for AvantGuard ConnectSecure service authentication.
  • Needs the base URL of the AvantGuard ConnectSecure API configured in credentials.
  • Depends on the @avantguardllc/n8n-openapi-node package for OpenAPI-based request building.

Troubleshooting

  • Missing or invalid X USER ID: The API requires a valid user identifier in the header; ensure this is provided and correct.
  • Incorrect query parameters: Invalid values for condition, skip, limit, or order_by may cause API errors or empty responses.
  • Authentication failures: Verify that the API key credential is correctly set up and has necessary permissions.
  • Network issues: Ensure connectivity to the configured base URL and that no firewall blocks the requests.
  • API rate limits: Excessive requests might be throttled; implement retry logic or reduce request frequency.

Links and References

Discussion