Actions144
- Activity Log Actions
- API Info Actions
- Article Actions
- Asset Actions
- Asset Layout Actions
- Asset Layout Field Actions
- Asset Password Actions
- Card Actions
- Company Actions
- Expiration Actions
- Export Actions
- Folder Actions
- Group Actions
- IP Address Actions
- List Actions
- List Options Actions
- Magic Dash Actions
- Matcher Actions
- Network Actions
- Password Folder Actions
- Photo Actions
- Procedure Actions
- Procedure Task Actions
- Public Photo Actions
- Rack Storage Actions
- Rack Storage Item Actions
- Relation Actions
- S3 Export Actions
- Upload Actions
- User Actions
- VLAN Actions
- VLAN Zone Actions
- Website Actions
Folder → Get Many
AI-generatedOverview
This node operation retrieves multiple folder records from the Hudu system. It supports filtering folders based on various criteria such as child folder status, company association, folder type, company specificity, folder name, and parent folder ID. Users can choose to return all matching folders or limit the number of results. Additionally, results can be wrapped into a single item containing an array of folders and a count, which helps prevent downstream nodes from executing once per folder and potentially hitting rate limits. This operation is useful for scenarios where bulk folder data retrieval is needed, such as syncing folder information, reporting, or batch processing.
Use Case Examples
- Retrieve all folders associated with a specific company.
- Get up to 25 photo-type folders that are not child folders.
- Fetch folders by name filter and wrap results to avoid rate limiting in subsequent nodes.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all results or only up to a given limit. |
| Limit | Maximum number of folder results to return when not returning all. |
| Wrap Results in Single Item | Whether to return all results as a single item with an 'items' array and 'count' field to prevent downstream nodes from executing once per result item. |
| Filters | Collection of filters to narrow down folder results based on child folder status, company, folder type, company specificity, name, and parent folder ID. |
Output
JSON
items- Array of folder objects when results are wrapped.count- Number of folder objects returned when results are wrapped.
- Individual folder properties returned when results are not wrapped.
Dependencies
- Hudu REST API
- API authentication token (credential required)
Troubleshooting
- Ensure the API credentials are correctly configured and have permissions to access folder data.
- If filtering by company, verify the company name or ID is valid and accessible.
- Be cautious with client-side filtering options like 'Child Folder' and 'Parent Folder ID' as they may impact performance.
- If the node throws an error about unknown resource, verify the resource parameter is set to 'folders'.
- Use the 'Wrap Results in Single Item' option to avoid rate limiting issues when processing many folders downstream.