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 integrates with the Hudu REST API to perform various operations on different resources within Hudu. Specifically, for the Asset Layout resource with the Get operation, it retrieves detailed information about a specific asset layout by its name or ID. This is useful when you want to fetch the configuration or structure of an asset layout in Hudu to use in automation workflows, reporting, or further processing.
Practical examples include:
- Automatically retrieving asset layout details to dynamically generate forms or UI elements.
- Using asset layout data to validate or enrich asset records in other systems.
- Integrating asset layout metadata into documentation or inventory management processes.
Properties
| Name | Meaning |
|---|---|
| Asset Layout Name or ID | Select an existing asset layout from a dropdown list or specify its ID via expression to identify which asset layout to retrieve. |
Output
The node outputs JSON data representing the requested asset layout's details. The structure typically includes all fields and configurations that define the asset layout in Hudu, such as field definitions, layout properties, and possibly customizations.
If the node supports binary data output (not indicated here), it would represent associated files or attachments related to the asset layout, but this is not applicable for the Get operation on asset layouts.
Dependencies
- Requires a valid connection to the Hudu REST API.
- Needs an API key credential configured in n8n to authenticate requests.
- The base URL for the Hudu instance must be set in the credentials.
- No additional external dependencies are required beyond the API access.
Troubleshooting
Common issues:
- Invalid or missing API key credential will cause authentication failures.
- Specifying an incorrect or non-existent asset layout ID or name will result in errors or empty responses.
- Network connectivity problems can prevent successful API calls.
Error messages:
"The resource "asset_layouts" is not known!"— indicates a misconfiguration or unsupported resource; ensure the resource parameter is correctly set.- API errors returned from Hudu (e.g., 404 Not Found) usually mean the specified asset layout does not exist.
Resolutions:
- Verify API credentials and permissions.
- Confirm the asset layout exists in Hudu and the correct identifier is used.
- Check network connectivity and endpoint URL correctness.
Links and References
- Hudu API Documentation (general reference for API endpoints)
- n8n Expressions Documentation (for using expressions in property values)