Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the Connect Secure API to retrieve information about user shares of assets. Specifically, for the "Asset Data" resource and the "Retrieve Asset User Shares" operation, it fetches a list of asset shares associated with a particular user. This is useful in scenarios where you need to audit or analyze which assets are shared with or by a specific user, such as managing permissions, tracking asset distribution, or generating reports on asset access.

Practical examples include:

  • Retrieving all assets shared with a given user to verify access rights.
  • Filtering asset shares based on conditions like date ranges or asset types.
  • Paginating through large sets of asset shares using skip and limit parameters.
  • Sorting the results according to specified fields.

Properties

Name Meaning
X USER ID The unique identifier of the user whose asset shares you want to retrieve.
Condition A query condition string to filter the asset shares (e.g., filtering by status or type).
Skip Number of records to skip, used for pagination.
Limit Maximum number of records to return.
Order By Field(s) by which to order the returned asset shares.

Output

The node outputs JSON data representing the retrieved asset user shares. Each item in the output typically corresponds to an individual asset share record containing details such as asset identifiers, sharing metadata, and user-related information.

If the API supports binary data for this operation (not indicated here), the node would also provide binary output accordingly, but based on the provided code and properties, the output is purely JSON.

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 or external services are explicitly required beyond the API authentication.

Troubleshooting

  • Missing or invalid X USER ID: Since the user ID is required, omitting it or providing an incorrect value will likely cause errors or empty results. Ensure the user ID is correct and properly formatted.
  • API authentication errors: If the API key credential is missing or invalid, the node will fail to authenticate. Verify that the API key is correctly set up in n8n credentials.
  • Invalid query conditions: Malformed or unsupported query strings in the Condition property may result in API errors or no data returned. Validate the query syntax according to the Connect Secure API documentation.
  • Pagination issues: Setting Skip or Limit incorrectly (e.g., negative numbers) might cause unexpected behavior or errors.
  • Order By field errors: Specifying invalid fields for ordering can lead to API errors; ensure the field names match those supported by the API.

Links and References

Discussion