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 updates an existing Procedure Task in the Hudu system. It allows users to modify various attributes of a specific task within a procedure, such as its name, description, assigned users, due date, priority, and completion status.
Common scenarios where this node is beneficial include:
- Automating task management workflows by programmatically updating task details based on external triggers or conditions.
- Synchronizing task information from other systems into Hudu.
- Adjusting task priorities or assignments dynamically as project requirements evolve.
Practical example:
- Automatically mark a procedure task as completed when a related external process finishes.
- Change the assigned user of a task based on workload balancing logic implemented in n8n.
Properties
| Name | Meaning |
|---|---|
| Task ID | The unique identifier of the procedure task to update (required). |
| Update Fields | A collection of fields to update on the task. Each field is optional and can be set as needed: |
| - Assigned User Names or IDs | Multiple users assigned to the task. Users can be selected from a list or specified by IDs via expressions. |
| - Completed | Boolean flag indicating whether the task is marked as completed. |
| - Description | Detailed textual description of the task. |
| - Due Date | The due date and time for the task. |
| - Name | The name/title of the task. |
| - Position | Numeric position of the task within the procedure sequence. |
| - Priority | Priority level of the task. Options: High, Low, Normal, Unsure, Urgent. |
| - Procedure ID | Identifier of the procedure to which this task belongs. |
| - User Name or ID | Single user assigned to the task. Can be selected from a list or specified by ID via expression. |
Output
The node outputs JSON data representing the updated procedure task(s). Each output item corresponds to one input item processed and includes the updated task details as returned by the Hudu API.
If multiple items are processed, each output item is paired with its corresponding input item index.
No binary data output is produced by this node.
Dependencies
- Requires an active connection to the Hudu REST API.
- Needs an API key credential configured in n8n for authentication.
- The base URL for the Hudu API must be set in the node credentials.
- Uses internal option loaders to fetch user lists for assignment fields.
Troubleshooting
Common issues:
- Invalid or missing Task ID will cause the update to fail.
- Providing invalid user IDs or names in assignment fields may result in errors.
- Attempting to update a task that does not exist or belongs to another procedure may cause API errors.
- Incorrect date formats for the due date field can lead to request rejection.
Error messages:
"The resource "procedure_tasks" is not known!"— indicates the resource parameter was incorrect or missing.- API errors related to authentication failures suggest checking the API key credential.
- Validation errors from the API typically indicate malformed or incomplete update fields.
Resolution tips:
- Ensure the Task ID is correct and the task exists.
- Use the provided user selection dropdowns or valid user IDs.
- Validate date/time inputs conform to ISO 8601 format.
- Confirm API credentials and base URL are correctly configured.
Links and References
- Hudu API Documentation (for detailed API endpoints and data models)
- n8n Expressions Documentation (for using expressions in property values)