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 updates an existing Asset associated with a specific Company by its unique identifiers. It sends a PUT request to modify the Asset's details such as name, serial number, model, manufacturer, and other metadata fields. This is useful in scenarios where asset information needs to be kept current, for example, updating equipment details in an inventory system or modifying asset attributes after maintenance.
Practical examples:
- Updating the serial number or model of a company’s machinery asset.
- Changing the archived status of an asset when it is decommissioned.
- Modifying custom fields or adding additional metadata to an asset record.
Properties
Name | Meaning |
---|---|
Id | The identifier of the requested Asset (number) |
Company Id | The identifier of the parent Company to which the Asset belongs (number) |
Additional Body Fields | Optional fields to update on the Asset. These include: |
- Id | Unique identifier of the asset (number) |
- Company Id | Identifier of the company owning the asset (number) |
- Asset Layout Id | Identifier of the asset layout associated with the asset (number) |
- Slug | URL slug used to identify the asset (string) |
- Name | Name of the asset (string) |
- Primary Serial | Primary serial number of the asset (string) |
- Primary Mail | Primary email associated with the asset (string) |
- Primary Model | Primary model of the asset (string) |
- Primary Manufacturer | Primary manufacturer of the asset (string) |
- Company Name | Name of the company owning the asset (string) |
- Object Type | Type of object the asset represents (string) |
- Asset Type | Category/type of the asset (string) |
- Archived | Whether the asset is archived (boolean) |
- Url | URL of the asset page (string) |
- Created At | Date/time when the asset was created (string) |
- Updated At | Date/time when the asset was last updated (string) |
- Fields | JSON array of fields associated with the asset |
- Assets | JSON object containing custom fields related to the asset |
- Cards | JSON array of cards associated with the asset (if available) |
Output
The node outputs the updated Asset data in the json
field of the output item. This typically includes all the properties of the Asset after the update has been applied, reflecting the new state of the Asset resource.
If binary data were involved (not indicated here), it would represent files or attachments related to the Asset, but this operation focuses on JSON data updates only.
Dependencies
- Requires an API key or authentication token configured in n8n credentials to authorize requests to the external service managing Assets and Companies.
- The base URL for the API must be set in the node credentials or environment configuration.
- The node depends on the external API supporting PUT operations on the endpoint for updating Assets under a given Company.
Troubleshooting
- Missing Required IDs: If either the Asset Id or Company Id is not provided or invalid, the API will likely return an error indicating missing or invalid identifiers. Ensure these are correctly set.
- Invalid Field Formats: Providing incorrectly formatted JSON in fields like
fields
,assets
, orcards
may cause parsing errors. Validate JSON syntax before sending. - Authentication Errors: If the API key or token is missing or expired, the node will fail with authorization errors. Verify credential validity.
- API Endpoint Issues: If the base URL or endpoint path is incorrect, the request will fail. Confirm the API endpoint configuration matches the service documentation.
- Archived Status Confusion: Setting the
archived
boolean incorrectly might lead to assets being hidden or inactive unexpectedly. Double-check the intended value.
Links and References
- Refer to the external API documentation for detailed schema and validation rules of Asset and Company resources.
- JSON formatting tools can help validate complex JSON input fields.
- n8n documentation on setting up API credentials and HTTP request nodes for further customization.