AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node operation, "Get Retrieve Asset Shares," is designed to fetch shared asset data from an external service. It allows users to retrieve information about asset shares associated with a particular user by specifying the user ID and optional query parameters to filter, sort, or paginate the results.

Common scenarios where this node would be beneficial include:

  • Retrieving all asset shares for a specific user to display or process in workflows.
  • Filtering asset shares based on conditions such as date ranges or status.
  • Paginating through large sets of asset share records by skipping and limiting the number of returned entries.
  • Ordering the retrieved asset shares by specified fields.

Practical example: A workflow that monitors asset sharing activity could use this node to pull the latest shares for a user, filter them by certain criteria, and then trigger notifications or further processing based on the retrieved data.

Properties

Name Meaning
X USER ID The User ID for whom the asset shares are being retrieved. This is required and sent as a header named X-USER-ID.
Additional Query Parameters Optional parameters to refine the query:
- Condition: A string to specify query conditions (e.g., filters).
- Skip: Number of records to skip (for pagination).
- Limit: Maximum number of records to return.
- Order By: Field(s) to order the results by.

Output

The node outputs JSON data representing the retrieved asset shares. Each item in the output corresponds to an asset share record fetched from the external service. The structure typically includes details about the asset share such as identifiers, metadata, and any relevant attributes provided by the API.

If the external service supports binary data related to asset shares (e.g., documents or images), the node would handle it accordingly, but based on the provided code and properties, the primary output is JSON data.

Dependencies

  • Requires an API key credential for authenticating requests to the external service.
  • The base URL for the API is configured via credentials.
  • Uses HTTP headers and query parameters to communicate with the API endpoint.
  • Depends on the @avantguardllc/n8n-openapi-node package and an OpenAPI specification (openapi.json) bundled with the node for request building.

Troubleshooting

  • Missing or invalid X USER ID header: Since the user ID is required, omitting it or providing an incorrect value will likely cause authentication or authorization errors. Ensure the user ID is correctly set.
  • Invalid query parameters: Providing malformed or unsupported values in additional query parameters (e.g., non-numeric skip/limit) may result in API errors. Validate inputs before execution.
  • API connectivity issues: Network problems or incorrect base URL configuration can prevent successful API calls. Verify credentials and network access.
  • Empty or unexpected responses: If no asset shares match the query, the output may be empty. Adjust query parameters or verify data availability.

Links and References

Discussion