Actions109
- 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
- Websites Actions
- Procedures Actions
- Public Photos Actions
- Rack Storage Items Actions
- Rack Storages Actions
- Relations Actions
- Uploads Actions
- Users Actions
- Activity Logs Actions
- Articles Actions
Overview
This node retrieves a specific Asset from a given Company using the "Get Companies Company Id Assets Id" operation. It is designed for scenarios where you need to fetch detailed information about a particular asset belonging to a company, such as in IT asset management, inventory tracking, or compliance audits.
Practical Example:
Suppose your organization manages multiple companies and their assets (like computers, servers, or software licenses) in Hudu. You can use this node to automatically pull details of a specific asset by providing its ID and the parent company's ID, enabling workflows like automated reporting, asset validation, or integration with other systems.
Properties
| Name | Type | Meaning |
|---|---|---|
| Id | Number | The identifier of the requested Asset. |
| Company Id | Number | The identifier of the requested parent Company. |
Output
The node outputs a json object containing the details of the requested Asset. The structure typically includes fields representing the asset's properties as returned by the Hudu API, such as asset name, type, status, and any custom fields defined in your Hudu instance.
Note: The exact output fields depend on the Hudu API response for the asset resource.
Dependencies
- External Service: Requires access to the Hudu API.
- API Credentials: Needs an n8n credential named
avantguardHuduApi, which should include at least thebaseUrland likely an API key or token. - n8n Configuration: Ensure that the credentials are properly set up in your n8n instance.
Troubleshooting
Missing or Invalid Credentials:
Error Message: "401 Unauthorized" or similar.
Resolution: Check that theavantguardHuduApicredentials are correctly configured and have the necessary permissions.Invalid Asset or Company ID:
Error Message: "404 Not Found" or similar.
Resolution: Verify that both the Asset ID and Company ID exist in your Hudu system.Connection Issues:
Error Message: "Network Error" or timeouts.
Resolution: Ensure that the base URL is correct and that your n8n instance can reach the Hudu API endpoint.