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 operation retrieves multiple Asset Layout records from the Hudu system. It is useful when you want to list or filter asset layouts in bulk, for example, to synchronize asset layout data with another system, generate reports, or perform batch processing on asset layouts.
Typical use cases include:
- Fetching all asset layouts or a limited subset based on criteria.
- Filtering asset layouts by name or last update date.
- Paging through large sets of asset layouts efficiently.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all matching asset layouts or limit the number of results. If false, the number of results returned is capped by the "Limit" property. |
| Limit | The maximum number of asset layouts to return when "Return All" is false. Must be at least 1. |
| Filters | Collection of filters to narrow down the asset layouts returned: |
| Name | Filter asset layouts by their exact name. |
| Page | Specify which page of results to retrieve (for pagination). |
| Updated At | Filter asset layouts by their update timestamp. Supports three modes: exact date, date range, or preset ranges such as "Last 7 Days", "Today", "This Month", etc. |
Output
The output is an array of JSON objects representing asset layouts that match the specified filters and limits. Each object contains the fields of an asset layout as returned by the Hudu API.
- The
jsonfield holds the asset layout data. - The output items are paired with the input item index they correspond to.
- No binary data is output by this operation.
Dependencies
- Requires an active connection to the Hudu REST API.
- Needs an API key credential configured in n8n with appropriate permissions to read asset layouts.
- The base URL for the Hudu API must be set in the credentials.
Troubleshooting
- No results returned: Check if filters are too restrictive or if the pagination parameters are correct.
- API authentication errors: Verify that the API key credential is valid and has access rights.
- Invalid date filter usage: Ensure date filters are correctly formatted and the mode matches the provided values.
- Limit ignored when Return All is true: This is expected behavior; disable Return All to enforce limits.
- Unexpected errors: Enable debug logging in the node to get detailed error messages for troubleshooting.
Links and References
- Hudu API Documentation — For details on asset layout endpoints and filtering options.
- n8n Documentation - Creating Nodes — Guidance on how nodes interact with APIs and handle inputs/outputs.