Actions100
- Activity Logs Actions
- Articles Actions
- Asset Layouts Actions
- Asset Passwords Actions
- Assets Actions
- Get Assets
- Get Companies Company Id Assets
- Post Companies Company Id Assets
- Get Companies Company Id Assets Id
- Put Companies Company Id Assets Id
- Delete Companies Company Id Assets Id
- Put Companies Company Id Assets Id Archive
- Put Companies Company Id Assets Id Unarchive
- Put Companies Company Id Assets Id Move Layout
- Cards Actions
- Companies Actions
- Expirations Actions
- Exports Actions
- Folders Actions
- IP Addresses Actions
- Lists Actions
- Magic Dash Actions
- Matchers Actions
- Networks Actions
- Password Folders Actions
- Procedure Tasks Actions
- Procedures Actions
- Public Photos Actions
- Rack Storage Items Actions
- Rack Storages Actions
- Relations Actions
- Uploads Actions
Overview
This node operation retrieves a specific Asset associated with a particular Company by their respective identifiers. It is useful in scenarios where you need to fetch detailed information about an individual asset belonging to a company, such as for inventory management, auditing, or reporting purposes.
For example, if you manage multiple companies and each has various assets tracked in your system, this operation allows you to query the details of one specific asset by providing the company ID and the asset ID.
Properties
| Name | Meaning |
|---|---|
| Id | The identifier of the requested Asset (a numeric value representing the specific asset). |
| Company Id | The identifier of the parent Company that owns the asset (a numeric value). |
Output
The output will contain a JSON object representing the details of the requested Asset. This typically includes all relevant fields describing the asset's properties, status, and metadata as defined by the external API schema.
If the node supports binary data output, it would represent any associated files or attachments related to the asset, but based on the provided code and context, only JSON data output is expected.
Dependencies
- Requires an API key credential for authentication to the external service.
- The base URL for the API must be configured in the node credentials.
- Depends on the
@avantguardllc/n8n-openapi-nodepackage for building request properties from the OpenAPI specification.
Troubleshooting
- Missing or invalid IDs: Ensure both the Company Id and Asset Id are provided and valid numbers; otherwise, the API call will fail.
- Authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
- Network or API errors: Check connectivity and API endpoint availability.
- Unexpected response structure: Confirm that the API version matches the OpenAPI spec used by the node.
Links and References
- AvantGuard API Documentation (hypothetical link)
- n8n OpenAPI Node Integration Guide