AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node operation, Get Retrieve Asset Unquoted Services, is designed to fetch asset-related data specifically about unquoted services from an external API. It is useful in scenarios where users need to retrieve detailed information about assets that have not been quoted yet, potentially for analysis, reporting, or further processing within an automation workflow.

Practical examples include:

  • Fetching a list of unquoted service assets for a particular user to display in a dashboard.
  • Automating the retrieval of asset data filtered by specific conditions such as date ranges or status.
  • Integrating asset data into other systems by pulling it dynamically based on user ID and query parameters.

Properties

Name Meaning
X USER ID The User ID header value used to identify the user making the request.
Additional Query Parameters Optional parameters to refine the query:
- Condition: A filter condition 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 of this node operation is JSON data representing the retrieved unquoted asset services. The structure typically includes an array of asset service objects with their respective properties as returned by the API.

If the API supports binary data, it would be summarized here; however, based on the provided code and properties, the output is purely JSON.

Dependencies

  • Requires an API key credential for authentication to the external AvantGuard ConnectSecure service.
  • Needs the base URL of the API 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 supplied.
  • Invalid query parameters: Providing malformed or unsupported values in additional query parameters like condition, skip, limit, or order_by may result in API errors or empty responses. Validate these inputs before execution.
  • API connectivity issues: Network problems or incorrect base URL configuration can lead to failed requests. Verify network access and credential settings.
  • Empty or unexpected response: If no data matches the query conditions, the output might be empty. Adjust filters or check the data source.

Links and References

Discussion