AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure
Join our community

Actions223

Overview

This node interacts with the "Asset Data" resource to retrieve information about asset storages. Specifically, the "Get Retrieve Asset Storages" operation fetches a list of asset storage records from an external service. This is useful in scenarios where you need to programmatically access and manage asset storage data, such as inventory management, asset tracking, or integration with asset databases.

Practical examples include:

  • Fetching all asset storages for a given user to display in a dashboard.
  • Querying asset storages with specific conditions or filters.
  • Paginating through large sets of asset storage records by skipping and limiting results.
  • Ordering the retrieved asset storages based on certain fields.

Properties

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

Output

The node outputs JSON data representing the retrieved asset storages. Each item in the output corresponds to an asset storage record fetched from the external service. The exact structure depends on the API response but typically includes details like storage identifiers, names, locations, capacities, or other metadata related to asset storages.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authentication with the external AvantGuard ConnectSecure service.
  • The base URL for the API must be configured in the node credentials.
  • The node uses HTTP headers and query parameters to communicate with the API endpoint.

Troubleshooting

  • Missing or invalid X USER ID: Since the X USER ID header is required, omitting it or providing an incorrect value will likely cause authentication or authorization errors. Ensure the correct user ID is provided.
  • Invalid query parameters: Providing malformed or unsupported query conditions may result in API errors or empty responses. Validate query syntax and parameter values.
  • API connectivity issues: Network problems or incorrect base URL configuration can prevent successful requests. Verify network access and credential settings.
  • Rate limits or permission errors: If the API enforces rate limits or user permissions, exceeding these may cause errors. Check API documentation and user privileges.

Links and References

Discussion