Hudu icon

Hudu

Interact with Hudu REST API

Overview

This node interacts with the "Procedure Task" resource of the Hudu REST API, specifically supporting the deletion of procedure tasks by their ID. It is useful in automation workflows where you need to programmatically remove specific tasks from procedures managed in Hudu, such as cleaning up completed or obsolete tasks.

A practical example: If you have a workflow that monitors task completion status and wants to automatically delete tasks that are no longer needed, this node can be configured to delete those tasks by specifying their Task ID.

Properties

Name Meaning
Task ID The numeric identifier of the procedure task to delete. This is required to specify which task should be removed.

Output

The node outputs JSON data representing the result of the delete operation for each input item. Typically, this will include confirmation details or status information returned by the Hudu API after deleting the specified procedure task.

If an error occurs during deletion, and the node is set to continue on failure, the output JSON will contain an error field with the error message.

No binary data output is involved.

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 other external dependencies are required.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent Task ID will cause the API to return an error.
    • Network connectivity problems or incorrect API credentials will prevent successful deletion.
    • Attempting to delete a task without proper permissions may result in authorization errors.
  • Error messages:

    • "The resource \"procedure_tasks\" is not known!" — indicates the resource parameter was incorrectly set; ensure it is exactly "procedure_tasks".
    • API errors returned from Hudu (e.g., 404 Not Found if Task ID does not exist) will be surfaced in the node's error output.
  • Resolutions:

    • Verify the Task ID exists and is correct.
    • Check API key validity and permissions.
    • Ensure network access to the Hudu API endpoint.
    • Use the node’s “Continue On Fail” option to handle errors gracefully in workflows.

Links and References

Discussion