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 REST API, specifically supporting the "Get" operation to retrieve details about a specific procedure task by its ID. It is useful in scenarios where you need to fetch detailed information about a particular task within a procedure, such as tracking progress, auditing, or integrating task data into workflows.
Practical examples include:
- Automatically retrieving task details when a procedure is triggered.
- Using task information to update other systems or notify users.
- Auditing or reporting on specific tasks within procedures.
Properties
| Name | Meaning |
|---|---|
| Task ID | The ID number of the procedure task to retrieve. This is a required numeric identifier specifying which task's details to fetch. |
Output
The node outputs JSON data representing the details of the requested procedure task. The structure typically includes all relevant fields returned by the Hudu API for a procedure task, such as task name, description, status, assigned user, due dates, and any custom fields associated with the task.
If the node supports binary data output (not indicated here), it would represent attachments or files related to the task, but this is not evident from the provided code.
Dependencies
- Requires an active connection to the Hudu REST API.
- Needs an API key credential configured in n8n to authenticate requests.
- The base URL for the Hudu API must be set in the node credentials.
- No additional external dependencies are indicated.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Task ID will likely result in an error or empty response.
- Network connectivity problems or incorrect API credentials can cause authentication failures.
- If the resource or operation parameters are misconfigured, the node will throw an error indicating unknown resource or operation.
Error messages:
"The resource \"procedure_tasks\" is not known!"— indicates the resource parameter is incorrect or unsupported.- API errors returned from Hudu (e.g., 404 Not Found if Task ID does not exist) will propagate as node errors.
Resolutions:
- Verify that the Task ID is correct and exists in Hudu.
- Ensure API credentials and base URL are correctly configured.
- Confirm that the resource is set to "procedure_tasks" and operation to "get".
Links and References
- Hudu API Documentation (general reference for API endpoints and data structures)
- n8n documentation on creating and using API credentials