AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node operation retrieves the user shares associated with a specific asset in an asset management system. It is useful when you need to query which users have access or sharing permissions for a particular asset, enabling audit, reporting, or access control workflows.

Practical examples include:

  • Fetching all users who have shared access to a digital asset before performing further processing.
  • Auditing user permissions on assets to ensure compliance.
  • Integrating asset sharing data into dashboards or notifications.

Properties

Name Meaning
X USER ID The User Id header value identifying the user making the request (required).
Additional Query Parameters Optional parameters to refine the query:
- Condition: Query condition/filter string.
- Skip: Number of records to skip (pagination).
- Limit: Maximum number of records to return.
- Order By: Field(s) to order the results by.

Output

The output JSON contains the retrieved list of user shares related to the specified asset. Each item typically represents a user share record with details such as user identifiers and sharing metadata.

If the node supports binary data output, it would represent any file or media content related to the asset shares, but based on the provided code and properties, this node primarily outputs JSON data about user shares.

Dependencies

  • Requires an API key credential for authentication to the AvantGuard ConnectSecure service.
  • Needs the base URL of the AvantGuard ConnectSecure API configured in credentials.
  • Depends on the @avantguardllc/n8n-openapi-node package and the OpenAPI specification (openapi.json) bundled with the node.

Troubleshooting

  • Missing or invalid X USER ID: The node requires the "X USER ID" header; ensure it is provided and correctly formatted.
  • API authentication errors: Verify that the API key credential is valid and has sufficient permissions.
  • Query parameter issues: Incorrectly formatted query conditions or unsupported fields in "Additional Query Parameters" may cause errors; validate these inputs.
  • Network or connectivity problems: Ensure the base URL is reachable from the n8n instance.

Links and References

Discussion