Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the Connect Secure API to retrieve system event data related to assets. Specifically, the "Retrieve System Events View" operation fetches a filtered and paginated list of system events based on user-defined query parameters. This is useful for monitoring asset-related activities, auditing changes, or integrating event logs into workflows for alerting or reporting.

Practical examples include:

  • Fetching recent system events for an asset to display in a dashboard.
  • Automating alerts when certain conditions in system events are met.
  • Exporting event logs for compliance or analysis.

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 system events (e.g., by event type, date range).
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 descending).

Output

The node outputs JSON data representing the retrieved system events matching the query parameters. The structure typically includes an array of event objects, each containing details such as event type, timestamp, associated asset information, and other metadata relevant to the system events view.

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 Connect Secure API being accessible and properly configured.
  • No additional environment variables are explicitly required beyond the API credential.

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 query strings may cause errors; verify syntax and supported fields.
  • Pagination issues: Setting skip or limit incorrectly might result in empty responses or incomplete data.
  • API connectivity problems: Network issues or incorrect credentials will prevent successful data retrieval.
  • Common error messages will relate to authentication failures, invalid parameters, or server errors from the API. Resolving these involves checking credentials, input values, and network access.

Links and References

  • Connect Secure API documentation (refer to your organization's API docs for detailed query syntax and event schema).
  • n8n documentation on creating and using HTTP Request nodes for similar API integrations.

Discussion