Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the "Company" resource to retrieve audit data from an Adaudit system via a REST API. It is designed to fetch audit logs or records based on user-defined query conditions, pagination controls, and sorting preferences. This node is useful in scenarios where you need to monitor, analyze, or report on company-related audit events, such as tracking user activities, compliance checks, or security audits.

Practical examples include:

  • Retrieving audit logs filtered by specific criteria (e.g., date ranges, event types).
  • Paginating through large sets of audit records.
  • Sorting audit results by timestamp or other fields.

Properties

Name Meaning
X USER ID User Id header value required for authentication or identification in the API request.
Condition Query condition string to filter audit records (e.g., SQL-like or API-specific syntax).
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, user).

Output

The node outputs JSON data representing the retrieved Adaudit records matching the query parameters. The structure typically includes an array of audit entries, each containing details such as event type, timestamp, user information, and other relevant audit metadata.

If binary data were involved (not indicated here), it would represent files or attachments related to audit records, but this node focuses on JSON audit log data.

Dependencies

  • Requires an API key or token credential to authenticate requests to the Connect Secure API.
  • Depends on the external Connect Secure API service that exposes the Company Adaudit endpoint.
  • No additional environment variables are explicitly required beyond standard API credential configuration in n8n.

Troubleshooting

  • Missing or invalid X USER ID: The API requires the X USER ID header; ensure it is provided and correct to avoid authentication errors.
  • Invalid query condition syntax: If the Condition property is malformed, the API may return errors or empty results. Verify the query format matches the API specification.
  • Pagination issues: Setting Skip or Limit incorrectly might result in no data or repeated data. Adjust these values carefully.
  • Order By field not recognized: Using unsupported fields in Order By can cause API errors; confirm valid sortable fields with the API documentation.
  • API connectivity problems: Network issues or incorrect credentials will prevent data retrieval. Check API access and credential validity.

Links and References

Discussion