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 integrates with the Hudu REST API to manage procedure tasks within the Hudu system. Specifically, the "Procedure Task - Create" operation allows users to create a new task associated with a particular procedure. This is useful in scenarios where you want to automate task creation as part of a workflow, such as setting up tasks for IT documentation, project management, or operational procedures.
Practical examples include:
- Automatically creating a checklist item when a new procedure is added.
- Assigning tasks to specific users based on certain triggers.
- Setting due dates and priorities for tasks created programmatically.
Properties
| Name | Meaning |
|---|---|
| Name | The name/title of the procedure task to be created. |
| Procedure ID | The numeric ID of the procedure this task belongs to. |
| Additional Fields | A collection of optional fields to further define the task: |
| - Assigned User Names or IDs | Multiple users assigned to the task; can select from a list or specify IDs via expressions. |
| - Description | A detailed textual description of the task. |
| - Due Date | The date and time by which the task should be completed. |
| - Position | Numeric position/order of the task within the procedure. |
| - Priority | Priority level of the task; options are High, Low, Normal, Unsure, Urgent. |
| - User Name or ID | Single user assigned to the task; selectable from a list or specified via expression. |
Output
The node outputs an array of JSON objects representing the created procedure tasks. Each output item corresponds to one input item processed and contains the details of the newly created task as returned by the Hudu API.
If the node supports binary data output (not indicated here), it would typically represent attachments or files related to the task, but this operation focuses on JSON data only.
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 credentials.
- Uses internal option loaders to fetch user lists for assignment fields.
Troubleshooting
Common Issues:
- Invalid or missing Procedure ID: Ensure the procedure ID exists and is correct.
- Missing required fields like "Name" or "Procedure ID" will cause errors.
- API authentication failures if the API key or base URL is incorrect.
- Assigning users that do not exist or are not accessible may cause errors.
Error Messages:
"The resource \"procedure_tasks\" is not known!"— indicates an invalid resource parameter; ensure "procedure_tasks" is selected.- API errors related to permissions or invalid data will be passed through; verify API credentials and input data validity.
Resolution Tips:
- Double-check all required parameters before execution.
- Verify API credentials and connectivity.
- Use expressions carefully to ensure valid user IDs or other dynamic values.
Links and References
- Hudu API Documentation (general reference for API endpoints)
- n8n Expressions Documentation (for using expressions in property fields)
- Hudu Official Website