Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the Connect Secure API to retrieve event set data. Specifically, the "Retrieve Event Set" operation fetches a list of event sets based on optional filtering, pagination, and sorting parameters. This is useful in scenarios where you need to programmatically access event-related information from Connect Secure, such as monitoring security events, auditing activities, or integrating event data into workflows for further processing or alerting.

Practical examples include:

  • Fetching recent security events filtered by specific conditions.
  • Paginating through large sets of event data.
  • Sorting event sets by date or severity to prioritize handling.

Properties

Name Meaning
X USER ID User identifier required for authentication; passed as a header in the API request.
Condition Query condition string to filter the event sets returned (e.g., filter expressions).
Skip Number of records to skip for pagination purposes.
Limit Maximum number of records to return.
Order By Field(s) to order the results by (e.g., timestamp, severity).

Output

The node outputs JSON data representing the retrieved event sets from the Connect Secure API. The structure typically includes an array of event set objects matching the query parameters provided. Each event set object contains details relevant to the event, such as identifiers, timestamps, descriptions, and other metadata defined by the API.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating with the Connect Secure API.
  • The node depends on the external Connect Secure service being accessible.
  • Proper configuration of the API endpoint and credentials within n8n is necessary.

Troubleshooting

  • Missing or invalid X USER ID: The API requires a valid user ID header; ensure it is provided and correct.
  • Invalid query conditions: Malformed or unsupported filter expressions may cause errors; verify syntax according to the API documentation.
  • Pagination issues: Setting skip or limit incorrectly might result in empty responses or incomplete data.
  • API connectivity problems: Network issues or incorrect credentials can lead to authentication failures or timeouts.
  • Error messages typically reflect HTTP status codes from the API; check the message for hints (e.g., 401 Unauthorized, 400 Bad Request).

Resolving these usually involves verifying input parameters, ensuring valid credentials, and confirming network connectivity.

Links and References

  • Connect Secure API Documentation (refer to official docs for detailed query syntax and response formats)
  • n8n Documentation on creating and using API nodes
  • General REST API best practices for filtering, pagination, and ordering

Discussion