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 n8n node allows you to create a new asset for a specific company in Hudu via the "Post Companies Company Id Assets" operation. It is useful for automating asset management workflows, such as registering new hardware, software, or other resources under a company's profile in Hudu. For example, you could use this node to automatically add newly purchased devices to your asset inventory when a purchase order is completed.
Properties
| Name | Type | Meaning |
|---|---|---|
| Company Id | Number | The identifier of the parent company for the new asset. Required to specify the target company. |
| Additional Body Fields | Collection | Optional fields to further describe the asset being created. Includes: |
| - Name | String | The name of the new asset. |
| - Asset Layout Id | Number | The identifier of the asset layout associated with the new asset. |
| - Primary Serial | String | The primary serial number of the new asset. |
| - Primary Mail | String | The primary email associated with the new asset. |
| - Primary Model | String | The primary model of the new asset. |
| - Primary Manufacturer | String | The primary manufacturer of the new asset. |
| - Custom Fields | JSON | An array of JSON objects representing custom fields, with labels underscored and downcased. |
Output
The node returns the response from the Hudu API after creating the asset. The structure of the json output field will typically include details about the newly created asset, such as its ID, name, and any additional properties provided. The exact structure depends on the Hudu API's response, but you can expect fields like:
{
"id": 123,
"name": "Asset Name",
"company_id": 456,
"asset_layout_id": 789,
"primary_serial": "SN12345",
"primary_mail": "user@example.com",
"primary_model": "Model X",
"primary_manufacturer": "Manufacturer Y",
"custom_fields": [
{
"field_label": "value"
}
],
...
}
Binary data is not expected from this operation.
Dependencies
- External Service: Requires access to a Hudu instance with API enabled.
- API Key/Credentials: Needs valid credentials (
avantguardHuduApi) configured in n8n, including the base URL and authentication token. - n8n Configuration: Ensure the credentials are set up in n8n under the appropriate credential type.
Troubleshooting
Missing or Invalid Credentials:
Error: "401 Unauthorized" or similar.
Resolution: Check that your Hudu API credentials are correctly configured in n8n.Invalid Company Id:
Error: "404 Not Found" or "Company not found."
Resolution: Verify that the Company Id exists in your Hudu instance.Required Field Missing:
Error: "400 Bad Request" or "company_id is required."
Resolution: Ensure all required fields, especially Company Id, are provided.Malformed Custom Fields:
Error: "Invalid JSON" or "custom_fields format error."
Resolution: Make sure the Custom Fields property is a valid JSON array of objects.