Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the Connect Secure API to retrieve compliance assessment data. It is designed to fetch records related to compliance assessments based on user-defined query parameters such as filtering conditions, pagination controls, and sorting preferences.

Typical use cases include:

  • Fetching a list of compliance assessments for auditing or reporting purposes.
  • Retrieving specific compliance assessment records filtered by certain criteria.
  • Integrating compliance data into workflows for automated monitoring or alerting.

For example, a user might want to retrieve all compliance assessments where the status is "pending" and limit the results to 10 entries sorted by date.

Properties

Name Meaning
X USER ID User Id header required for authentication or identification in the API request.
Condition Query condition string to filter compliance assessments (e.g., status="pending").
Skip Number of records to skip for pagination purposes.
Limit Maximum number of records to return.
Order By Field name(s) to order the results by (e.g., "date", "status").

Output

The node outputs JSON data representing the retrieved compliance assessments. The structure typically includes an array of compliance assessment objects matching the query parameters. Each object contains fields relevant to a compliance assessment record as defined by the Connect Secure API.

No binary data output is indicated.

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 may reject requests without a valid user ID header. Ensure this property is set correctly.
  • Invalid query conditions: Malformed or unsupported query strings in the Condition property can cause errors or empty results.
  • Pagination issues: Setting Skip or Limit incorrectly (e.g., negative numbers) may lead to unexpected results or errors.
  • API connectivity problems: Network issues or incorrect API credentials will prevent successful data retrieval.
  • Order By field errors: Specifying non-existent fields in Order By may cause the API to return errors or ignore the parameter.

To resolve these, verify all input properties, ensure valid API credentials, and confirm network connectivity.

Links and References

  • Connect Secure API documentation (refer to your organization's API docs)
  • n8n documentation on HTTP Request nodes and custom API integrations

Discussion