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 perform various operations on different resources, including folders. Specifically, the "Get Path" operation for the Folder resource retrieves the full path of a folder given its ID. This is useful in scenarios where you need to understand or display the hierarchical location of a folder within the system, such as organizing documents, assets, or other entities stored in nested folders.
Practical examples:
- Fetching the full folder path to display it in a user interface.
- Using the folder path to generate breadcrumbs for navigation.
- Automating workflows that depend on folder hierarchy information.
Properties
| Name | Meaning |
|---|---|
| Folder ID | The numeric ID of the folder to get the path for. This identifies which folder's path will be retrieved. |
Output
The node outputs an array of JSON objects representing the result of the requested operation. For the "Get Path" operation on folders, the output JSON typically contains the folder path details, such as the names and IDs of folders from the root down to the specified folder.
Each output item includes a pairedItem property linking it back to the input item index.
No binary data output is indicated by the source code.
Dependencies
- Requires an API key credential for authenticating with the Hudu REST API.
- The base URL for the API must be configured in the node credentials.
- No additional external dependencies are required beyond the Hudu API access.
Troubleshooting
- Unknown Resource Error: If the resource parameter is incorrect or misspelled, the node throws an error stating the resource is not known. Ensure the resource name is exactly "folders" for this operation.
- Invalid Folder ID: Providing a non-existent or invalid folder ID may cause the API to return an error or empty results. Verify the folder ID exists in your Hudu instance.
- Authentication Issues: Missing or incorrect API key credentials will prevent successful API calls. Confirm the API key and base URL are correctly set in the node credentials.
- Continue On Fail Behavior: If enabled, the node will continue processing subsequent items even if one fails, returning error messages in the output JSON.
Links and References
- Hudu API Documentation (general reference for API endpoints)
- n8n documentation on creating custom nodes