AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node is designed to retrieve asset interface data from the "Asset Data" resource using a "Get Retrieve Asset Interface" operation. It allows users to fetch detailed information about asset interfaces by specifying a user ID and optional query parameters to filter, limit, or order the results. This node is beneficial in scenarios where you need to programmatically access asset-related data for monitoring, reporting, or integration with other systems.

Practical examples include:

  • Fetching asset interface details for a specific user to display in a dashboard.
  • Retrieving a limited set of asset records ordered by a particular field for batch processing.
  • Applying conditions to query only assets that meet certain criteria.

Properties

Name Meaning
X USER ID The User ID required to identify the user context for which asset data is retrieved.
Additional Query Parameters Optional parameters to refine the query:
- Condition: Filter condition as a string.
- Skip: Number of records to skip.
- Limit: Maximum number of records to return.
- Order By: Field name(s) to order the results by.

Output

The node outputs JSON data representing the retrieved asset interface information. The structure typically includes asset interface details corresponding to the query parameters provided. If multiple records are returned, the output will be an array of objects each describing an asset interface.

No binary data output is indicated in the source code or properties.

Dependencies

  • Requires an API key credential for authentication (referred generically as an API key credential).
  • Depends on the base URL configuration provided in the node credentials.
  • Uses HTTP headers including X-USER-ID to specify the user context.
  • Supports additional query parameters sent as URL query strings.

Troubleshooting

  • Missing or invalid X USER ID: The node requires a valid user ID header; ensure this is provided and correctly formatted.
  • API authentication errors: Verify that the API key credential is correctly configured and has necessary permissions.
  • Query parameter issues: Invalid values for condition, skip, limit, or order_by may cause errors or unexpected results. Validate these inputs before execution.
  • Network or endpoint errors: Check connectivity and the correctness of the base URL in credentials.
  • Empty results: If no data is returned, verify the query conditions and user ID to ensure they match existing data.

Links and References

  • No direct external links were found in the source code.
  • For more information, consult the API documentation of the service providing the asset data interface.

Discussion