AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure
Join our community

Actions223

Overview

This node allows you to create an Endpoint Detection and Response (EDR) record by sending a POST request with specified user identification and optional additional data fields. It is useful in security automation workflows where you want to programmatically report or log EDR events into a system that supports such API interactions.

Typical use cases include:

  • Automatically creating EDR entries when suspicious activity is detected.
  • Integrating with security platforms to enrich incident data.
  • Logging firewall or ransomware-related events with custom metadata.

Properties

Name Meaning
X USER ID The User ID header value sent with the request, identifying the user associated with the EDR event. This is required.
Additional Body Fields Optional JSON fields to add to the request body. Includes: data object with boolean flags like regex, is_firewall, and is_antirandsome.

The Additional Body Fields property lets you customize the payload with extra details about the EDR event, for example:

{
  "data": {
    "regex": false,
    "is_firewall": false,
    "is_antirandsome": false
  }
}

Output

The node outputs the response from the API call as JSON in the json output field. This typically contains confirmation of the created EDR record or any error messages returned by the server.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authentication to the AvantGuard ConnectSecure API.
  • Needs the base URL of the API endpoint configured in the credentials.
  • Uses HTTP headers including X-USER-ID to identify the user making the request.
  • The node depends on the @avantguardllc/n8n-openapi-node package and an OpenAPI specification (openapi.json) bundled internally for request building.

Troubleshooting

  • Missing or invalid X USER ID header: The API requires this header; ensure it is provided and correctly formatted.
  • Invalid JSON in Additional Body Fields: If the JSON is malformed, the request will fail. Use valid JSON syntax.
  • Authentication errors: Verify that the API key credential is set up correctly and has necessary permissions.
  • Network or base URL issues: Confirm the base URL is correct and reachable from your n8n instance.
  • API response errors: Check the response message for specific error codes or messages to adjust input parameters accordingly.

Links and References

Discussion