Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the Connect Secure API to retrieve shared asset data. Specifically, the "Retrieve Asset Share" operation fetches information about a particular asset share by its unique identifier. This is useful in scenarios where users need to programmatically access or verify details of shared assets within the Connect Secure platform, such as for auditing, reporting, or integration with other systems.

Practical examples include:

  • Automatically retrieving asset share details when processing incoming requests.
  • Integrating asset share data into dashboards or monitoring tools.
  • Validating user access or permissions based on asset share information.

Properties

Name Meaning
X USER ID User Id header value required for authentication or identification in the API request.
Id Numeric identifier of the asset share to retrieve.

Output

The node outputs JSON data representing the retrieved asset share details from the Connect Secure API. The exact structure depends on the API response but typically includes fields describing the asset share's properties, status, and metadata.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating with the Connect Secure API.
  • Depends on the Connect Secure API being accessible and the provided user ID and asset share ID being valid.
  • The node uses the bundled OpenAPI specification to build its properties and operations.

Troubleshooting

  • Invalid or missing X USER ID: Ensure the "X USER ID" property is correctly set; otherwise, the API may reject the request.
  • Invalid asset share Id: Providing a non-existent or incorrect asset share ID will result in errors or empty responses.
  • Authentication errors: Verify that the API key credential is configured properly and has sufficient permissions.
  • Network issues: Confirm network connectivity to the Connect Secure API endpoint.
  • Unexpected API responses: Check if the API schema or endpoint has changed, which might require updating the node or credentials.

Links and References

  • Connect Secure API documentation (refer to official vendor resources)
  • n8n documentation on creating and using API credentials
  • OpenAPI Specification used internally by the node (bundled in source)

Discussion