Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the Connect Secure API to create an Endpoint Detection and Response (EDR) record. It is useful in security automation workflows where you want to programmatically submit EDR data for analysis or logging. For example, a security operations team could use this node to automatically send endpoint threat detection details into a centralized system whenever suspicious activity is detected.

Properties

Name Meaning
X USER ID The user identifier header value required by the API to authenticate or track the request.
Data JSON object containing EDR details. Supports fields such as regex (boolean), is_firewall (boolean), and is_antirandsome (boolean). This represents the payload sent to create the EDR record.

Output

The node outputs the response from the Connect Secure API after creating the EDR record. The output is structured as JSON data representing the created EDR resource or any relevant response information returned by the API. There is no indication of binary data output.

Dependencies

  • Requires an API key credential for authenticating with the Connect Secure API.
  • The node depends on the external Connect Secure service being available.
  • No additional environment variables are explicitly required beyond the API authentication setup.

Troubleshooting

  • Missing or invalid X USER ID header: The API requires the X USER ID header; ensure it is provided and correctly formatted.
  • Malformed JSON in Data property: The Data input must be valid JSON. Invalid JSON will cause request failures.
  • API authentication errors: Verify that the API key credential is configured properly and has sufficient permissions.
  • Network or connectivity issues: Ensure the Connect Secure API endpoint is reachable from the n8n instance.
  • Unexpected API responses: Check the API documentation for error codes and messages if the node returns errors.

Links and References

Discussion