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 retrieve information about asset layout fields. Specifically, the "Get" operation under the "Asset Layout Field" resource fetches details of a particular field within an asset layout by specifying either its name or ID.
Common scenarios for this node include:
- Automating retrieval of metadata about specific fields in asset layouts for documentation or auditing.
- Integrating asset layout field data into workflows that require dynamic access to asset structure definitions.
- Using the field details to drive conditional logic or populate other systems with asset schema information.
For example, you might use this node to get the configuration of a custom field in an asset layout before updating records or generating reports based on that field's properties.
Properties
| Name | Meaning |
|---|---|
| Asset Layout Name or ID | Select or specify the asset layout from which to get the field. Options are loaded dynamically from available asset layouts. |
| Field Name or ID | Select or specify the specific field within the chosen asset layout to retrieve. Options depend on the selected asset layout. |
Output
The node outputs JSON data representing the details of the requested asset layout field. This typically includes all relevant metadata about the field such as its identifier, name, type, and any configuration settings defined in Hudu.
The output is structured as an array of JSON objects, each corresponding to one retrieved field (in this case, usually a single item). Each object contains key-value pairs describing the field's attributes.
No binary data output is involved in this operation.
Dependencies
- Requires a valid connection to the Hudu REST API, authenticated via an API key credential.
- The base URL and API key must be configured in the node credentials.
- Dynamic option loading depends on API calls to fetch available asset layouts and their fields.
Troubleshooting
Common issues:
- Selecting an invalid or non-existent asset layout or field ID will result in errors or empty responses.
- Network connectivity or authentication failures with the Hudu API can cause request errors.
- If the dynamic options fail to load, it may indicate permission issues or API changes.
Error messages:
"The resource \"asset_layout_fields\" is not known!"— indicates a misconfiguration or unsupported resource selection.- API errors returned from Hudu (e.g., 404 Not Found) when the specified field or layout does not exist.
Resolutions:
- Verify that the asset layout and field IDs/names are correct and accessible.
- Check API credentials and network connectivity.
- Use expressions carefully to ensure they resolve to valid IDs.
Links and References
- Hudu API Documentation (for detailed API endpoints and field definitions)
- n8n Expressions Documentation (for using expressions in property values)