Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the Connect Secure API to retrieve information about asset user shares. Specifically, the "Retrieve Asset User Share" operation fetches details related to a particular user's share of an asset by using the user's ID and the asset's ID. This can be useful in scenarios where you need to audit or display which users have access to specific assets within a system that uses Connect Secure.

Practical examples include:

  • Fetching user-specific permissions or shares on digital assets for reporting.
  • Validating if a user has access to a given asset before performing further operations.
  • Integrating asset sharing data into workflows for notifications or compliance checks.

Properties

Name Meaning
X USER ID The unique identifier of the user whose asset share information is being retrieved.
Id The numeric identifier of the asset for which the user share information is requested.

Output

The node outputs JSON data containing the details of the asset user share corresponding to the provided user ID and asset ID. The exact structure depends on the Connect Secure API response but typically includes fields describing the share attributes, permissions, and metadata related to the asset-user relationship.

If the API supports binary data (e.g., files or attachments related to the asset share), the node would handle it accordingly, but based on the provided code and properties, the output focuses on JSON data representing the asset user share details.

Dependencies

  • Requires an active connection to the Connect Secure API.
  • Needs an API authentication token or key configured in n8n credentials to authorize requests.
  • The node depends on the bundled OpenAPI client library (@devlikeapro/n8n-openapi-node) and the OpenAPI specification (openapi.json) for request construction and execution.

Troubleshooting

  • Missing or invalid X USER ID: Ensure the "X USER ID" property is correctly set; otherwise, the API may reject the request or return no data.
  • Invalid asset Id: Providing an incorrect or non-existent asset ID will result in errors or empty responses.
  • Authentication errors: Verify that the API credentials are properly configured and valid.
  • Network issues: Connectivity problems with the Connect Secure API endpoint can cause timeouts or failures.
  • API changes: If the Connect Secure API updates its schema or endpoints, the node might require updates to remain compatible.

Common error messages might include unauthorized access, resource not found, or bad request due to missing parameters. Resolving these involves checking input values, credentials, and network connectivity.

Links and References

Discussion