Actions100
- Activity Log Actions
- Article Actions
- Asset Actions
- Asset Layout Actions
- Asset Layout Field Actions
- Asset Password Actions
- Card Actions
- Company Actions
- Expiration Actions
- Folder Actions
- IP Address Actions
- List Actions
- Magic Dash Actions
- Matcher Actions
- Network Actions
- Password Folder Actions
- Procedure Actions
- Procedure Task Actions
- Public Photo Actions
- Rack Storage Actions
- Rack Storage Item Actions
Overview
This node interacts with the Hudu REST API to manage asset layout fields, specifically supporting operations such as deleting a field from an asset layout. The "Delete" operation for the "Asset Layout Field" resource allows users to remove a specific field from a chosen asset layout.
Common scenarios where this node is beneficial include:
- Automating cleanup of outdated or unused fields in asset layouts.
- Managing asset metadata structures dynamically based on changing requirements.
- Integrating asset layout management into broader IT asset workflows.
For example, if an organization restructures its asset information and needs to remove deprecated fields from asset layouts programmatically, this node can be used within an n8n workflow to delete those fields efficiently.
Properties
| Name | Meaning |
|---|---|
| Asset Layout Name or ID | Select or specify the asset layout from which the field will be deleted. Options are loaded dynamically from existing asset layouts. |
| Field Name or ID | Select or specify the specific field within the chosen asset layout to delete. Options depend on the selected asset layout and are loaded dynamically. |
Output
The node outputs a JSON array containing the result of the delete operation for each input item processed. Each output item corresponds to one deletion attempt and includes relevant response data from the Hudu API.
If the operation fails for an item and "Continue On Fail" is enabled, the output for that item will contain an error message describing the failure.
The node does not output binary data.
Dependencies
- Requires an active connection to the Hudu REST API.
- Needs an API key credential configured in n8n for authentication.
- Relies on dynamic option loaders to fetch available asset layouts and their fields for user selection.
Troubleshooting
Common Issues:
- Selecting an invalid or non-existent asset layout or field ID may cause errors.
- Insufficient permissions or incorrect API key configuration can lead to authentication failures.
- Network connectivity issues may prevent communication with the Hudu API.
Error Messages:
"The resource \"asset_layout_fields\" is not known!"— This indicates an internal misconfiguration; ensure the resource and operation are correctly set.- API errors returned by Hudu (e.g., 404 Not Found when the field does not exist) will be passed through; verify the IDs used are correct.
Resolutions:
- Verify that the asset layout and field IDs are valid and exist in your Hudu instance.
- Check that the API key credential is correctly set up and has necessary permissions.
- Enable "Continue On Fail" in the node settings to handle individual item errors gracefully in batch operations.
Links and References
- Hudu API Documentation (for detailed API endpoints and authentication)
- n8n Expressions Documentation (for using expressions in property values)