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 "Procedure Task" resource of the Hudu API, specifically supporting the "Get Many" operation. It retrieves multiple procedure tasks based on optional filtering criteria and pagination controls.
Typical use cases include:
- Fetching all or a limited number of procedure tasks for reporting or auditing.
- Filtering procedure tasks by associated procedure ID, task name, or company to narrow down results.
- Integrating procedure task data into workflows for further processing or notifications.
For example, a user might want to retrieve all procedure tasks related to a specific procedure or company to monitor progress or generate summaries.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all matching procedure tasks or limit the number of results returned. |
| Limit | Maximum number of procedure tasks to return when "Return All" is false. Minimum value is 1. |
| Filters | Collection of filters to narrow down the procedure tasks: |
| Procedure ID | Filter tasks by the numeric ID of the associated procedure. |
| Name | Filter tasks by their name (string match). |
| Company Name or ID | Filter tasks by selecting a company from a list or specifying its ID via expression. |
Output
The node outputs an array of JSON objects representing procedure tasks. Each object contains the fields as returned by the Hudu API for procedure tasks, enriched with metadata linking each output item to its input item index.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Hudu REST API.
- The base URL and API key must be configured in the node credentials.
- Uses internal option loaders to populate dynamic dropdowns such as companies.
Troubleshooting
Common issues:
- Incorrect or missing API key credential will cause authentication failures.
- Providing invalid filter values (e.g., non-numeric Procedure ID) may result in API errors.
- Requesting too many items without enabling "Return All" can lead to truncated results.
Error messages:
"The resource \"procedure_tasks\" is not known!"indicates a misconfiguration of the resource parameter.- API errors returned from Hudu are propagated; check the error message for details like invalid filters or permission issues.
Resolutions:
- Verify API credentials and permissions.
- Use valid filter values and types.
- Enable "Return All" if you need to fetch more than the default limit.
Links and References
- Hudu API Documentation (for detailed API endpoints and parameters)
- n8n Expressions Documentation (for using expressions in filter inputs)