Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the Connect Secure API to retrieve compliance-related information. Specifically, for the "Compliance" resource and the "Retrieve Compliance Types" operation, it fetches the different types of compliance categories or classifications available in the system. This can be useful in scenarios where you need to dynamically obtain compliance type options for validation, reporting, or integration purposes.

For example, a user might want to pull all compliance types to populate a dropdown menu in another workflow or to audit which compliance categories are currently defined in their environment.

Properties

Name Meaning
X USER ID User Id (string) - required header value sent as X-USER-ID in the request

Output

The node outputs JSON data containing the retrieved compliance types from the Connect Secure API. The exact structure depends on the API response but typically includes an array or list of compliance type objects, each describing a compliance category.

No binary data output is indicated by the source code.

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.
  • Uses the @devlikeapro/n8n-openapi-node package to build properties and handle OpenAPI-based operations.
  • Requires the user to provide the X-USER-ID header value for the request.

Troubleshooting

  • Missing or invalid X-USER-ID header: The API may reject requests without this header or with incorrect values. Ensure the property is set correctly.
  • Authentication errors: If the API key credential is missing or invalid, the node will fail to authenticate.
  • Network or API availability issues: Connectivity problems or API downtime will cause execution failures.
  • Unexpected API response structure: If the API changes its response format, the node's output parsing might break.

To resolve these:

  • Verify the X USER ID input is provided and correct.
  • Confirm that the API key credential is configured properly.
  • Check network connectivity and API status.
  • Review any error messages returned by the API for clues.

Links and References

Discussion