Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the Connect Secure API to retrieve Endpoint Detection and Response (EDR) data. It is designed to query EDR records based on user-defined conditions, pagination controls, and sorting preferences. This node is useful in cybersecurity workflows where automated retrieval of security event logs or endpoint activity data is required for analysis, alerting, or further processing.

Practical examples include:

  • Fetching recent EDR events matching specific threat indicators.
  • Paginating through large sets of EDR records for batch processing.
  • Sorting EDR data by timestamp or severity to prioritize incident response.

Properties

Name Meaning
X USER ID User identifier header required for authentication or scoping the request.
Condition Query condition string to filter EDR records (e.g., specific attributes or criteria).
Skip Number of records to skip for pagination purposes.
Limit Maximum number of records to return in the response.
Order By Field(s) to order the returned EDR records by (e.g., timestamp, severity).

Output

The node outputs JSON data representing the retrieved EDR records from the Connect Secure API. Each item in the output corresponds to an individual EDR record matching the query parameters. The structure typically includes fields relevant to endpoint detection events such as timestamps, event types, user IDs, and other metadata.

No binary data output is indicated by the source code or properties.

Dependencies

  • Requires a valid API key credential for authenticating with the Connect Secure API.
  • Depends on the external Connect Secure service being accessible.
  • Uses the @devlikeapro/n8n-openapi-node package for OpenAPI-based operation parsing and request handling.
  • Requires proper configuration of the API credentials within n8n.

Troubleshooting

  • Common issues:

    • Missing or invalid "X USER ID" header may cause authentication or authorization failures.
    • Incorrect query conditions can result in empty responses or errors from the API.
    • Pagination parameters (skip, limit) set improperly might lead to unexpected subsets of data.
    • Network connectivity problems or incorrect API credentials will prevent successful data retrieval.

  • Error messages:

    • Authentication errors typically indicate missing or invalid API keys or user IDs.
    • Validation errors may arise if query parameters are malformed or unsupported by the API.
    • Timeout or connection errors suggest network issues or API service unavailability.

To resolve these, verify that all required input properties are correctly set, ensure API credentials are valid, and confirm network access to the Connect Secure API endpoint.

Links and References

Discussion