Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the "Compliance" resource of the Connect Secure API to retrieve compliance records based on specified criteria. It is useful for scenarios where users need to query and fetch filtered compliance data related to assets and companies, such as auditing, reporting, or monitoring compliance statuses.

For example, a user might want to retrieve all compliance records for a specific asset within a company, applying conditions like date ranges or status filters, and control pagination through skip and limit parameters.

Properties

Name Meaning
Asset Id The unique identifier of the asset for which compliance records are being retrieved.
Company Id The unique identifier of the company associated with the compliance records.
X USER ID The user identifier sent as a header to authenticate or identify the requestor.
Condition A query condition string to filter the compliance records (e.g., filtering by status).
Skip Number of records to skip, used for pagination.
Limit Maximum number of records to return, used for pagination.
Order By Field(s) by which to order the returned records.

Output

The node outputs JSON data containing the retrieved compliance records matching the query parameters. Each item in the output corresponds to a compliance record with its associated fields as returned by the API.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating requests to the Connect Secure API.
  • The node depends on the Connect Secure API endpoint that supports querying compliance records.
  • Proper configuration of authentication credentials in n8n is necessary.

Troubleshooting

  • Missing or invalid API credentials: Ensure the API key or authentication token is correctly configured in n8n credentials.
  • Required parameters not provided: Asset Id, Company Id, and X USER ID are mandatory; missing these will cause errors.
  • Invalid query conditions: Malformed or unsupported query strings in the Condition property may result in API errors.
  • Pagination issues: Setting Skip or Limit incorrectly (e.g., negative numbers) may lead to unexpected results or errors.
  • API rate limits or connectivity problems: Network issues or hitting API rate limits can cause failures; check connectivity and API usage policies.

Links and References

Discussion