AvantGuard - WebhookSite icon

AvantGuard - WebhookSite

AvantGuard - WebhookSite

Actions100

Overview

The "Get Assets" operation of the Assets resource retrieves a list of assets from an external system, allowing users to filter and paginate the results based on various criteria. This node is useful in scenarios where you need to fetch asset information for inventory management, reporting, or integration with other systems.

For example, you might use this node to:

  • Retrieve all assets belonging to a specific company.
  • Search for assets by name or serial number.
  • Paginate through large sets of assets to process them in batches.
  • Filter assets updated within a certain date range.

Properties

Name Meaning
Additional Query Parameters Optional filters and pagination options to refine the asset search. Includes:
- Company Id Filter assets by the parent company's ID (number).
- Id Filter assets by their unique asset ID (number).
- Name Filter assets by their name (string).
- Primary Serial Filter assets by their primary serial number (string).
- Asset Layout Id Filter assets by the associated asset layout's ID (number).
- Page Specify which page of results to return (number).
- Archived Set to true to retrieve only archived assets (boolean).
- Page Size Limit the number of assets returned per page (number).
- Slug Filter assets by their URL slug (string).
- Search Filter assets using a general search query (string).
- Updated At Filter assets updated at an exact time or within a range. Format: 'start_datetime,end_datetime' or 'exact_datetime' (string).

Output

The node outputs JSON data containing the retrieved assets matching the specified filters. The structure typically includes an array of asset objects, each representing an individual asset with its properties as provided by the external API.

If the external API supports binary data related to assets (e.g., images or documents), the node would handle it accordingly, but based on the provided code and properties, the output focuses on JSON asset data.

Dependencies

  • Requires connection to an external API service that manages assets.
  • Needs an API authentication token or key configured in the node credentials to authorize requests.
  • The base URL for the API is set via credentials.
  • No additional external libraries beyond the bundled OpenAPI client are required.

Troubleshooting

  • Common Issues:

    • Incorrect or missing API credentials will cause authentication failures.
    • Providing invalid filter values (e.g., non-numeric IDs) may result in API errors.
    • Pagination parameters out of range could lead to empty responses.
    • Date format errors in the "Updated At" filter can cause request failures.
  • Error Messages:

    • Authentication errors: Verify that the API key or token is correctly configured.
    • Validation errors: Check that all filter parameters conform to expected types and formats.
    • Network errors: Ensure the API base URL is reachable and correct.

Links and References

  • Refer to the external API documentation for detailed descriptions of asset fields and supported query parameters.
  • Consult n8n documentation on how to configure API credentials and use collection-type input properties.

Discussion