AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node interacts with the AvantGuard ConnectSecure API to retrieve shared asset data. Specifically, the "Get Retrieve Asset Share" operation fetches details about a shared asset by its unique identifier. This is useful in scenarios where users need to access or verify information about assets that have been shared within the AvantGuard system, such as checking permissions, status, or metadata of an asset share.

Practical examples include:

  • Retrieving details of a specific asset share to display in a dashboard.
  • Validating asset share information before performing further operations.
  • Auditing shared assets for compliance or security reviews.

Properties

Name Meaning
X USER ID The user identifier required for authentication or authorization in the API request.
Id The unique numeric identifier of the asset share to retrieve.

Output

The node outputs JSON data representing the retrieved asset share details. This typically includes all relevant fields returned by the AvantGuard ConnectSecure API for the specified asset share, such as share metadata, permissions, timestamps, and related asset information.

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 operation, the output is primarily JSON structured data.

Dependencies

  • Requires an API key credential for AvantGuard ConnectSecure to authenticate requests.
  • Needs the base URL of the AvantGuard ConnectSecure API configured in the node credentials.
  • Depends on the @avantguardllc/n8n-openapi-node package for building properties and handling OpenAPI specifications.

Troubleshooting

  • Missing or invalid X USER ID: The API requires a valid user ID header; ensure this property is correctly set.
  • Invalid asset share Id: Providing a non-existent or incorrect Id will result in errors or empty responses.
  • Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
  • Network issues: Ensure connectivity to the configured base URL and that no firewall or proxy blocks the request.
  • Unexpected response format: If the API changes, the node might fail to parse the response; updating the OpenAPI spec or node version may be necessary.

Links and References

Discussion