Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the Connect Secure API to retrieve audit log entries. It is designed to fetch records of user activities or system events for auditing and monitoring purposes. Typical use cases include compliance tracking, security analysis, and operational troubleshooting by reviewing who did what and when within a system.

For example, an organization might use this node to pull audit logs filtered by specific users or conditions, limit the number of records retrieved, or order the results by timestamp to analyze recent activities.

Properties

Name Meaning
X USER ID The User ID header value to identify the user making the request.
Condition A query string to filter audit log entries based on specific criteria (e.g., event type).
Skip Number of records to skip from the start of the result set (for pagination).
Limit Maximum number of audit log records to retrieve.
Order By Field name(s) to order the returned audit log entries (e.g., timestamp ascending/descending).

Output

The node outputs JSON data containing the retrieved audit log entries matching the specified query parameters. Each entry typically includes details such as the event type, timestamp, user involved, and other relevant metadata.

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

Dependencies

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

Troubleshooting

  • Missing or invalid User ID header: Since the X USER ID property is required and sent as a header, omitting it or providing an incorrect value may cause authorization errors or empty responses.
  • Invalid query condition syntax: If the Condition parameter contains malformed queries, the API may return errors or no results.
  • Pagination issues: Incorrect values for Skip and Limit could lead to unexpected subsets of data or empty results.
  • Ordering errors: Specifying invalid fields in Order By may cause the API to reject the request or ignore the ordering.
  • API connectivity problems: Network issues or invalid API credentials will prevent successful retrieval of audit logs.

To resolve these:

  • Ensure all required fields are correctly filled.
  • Validate query syntax according to the API documentation.
  • Check API credentials and network connectivity.
  • Adjust pagination and ordering parameters carefully.

Links and References

Discussion