Currently, to detect when a task is ready for work because its dependencies have been completed, developers must rely on the taskUnblocked trigger. While functional, this trigger is broad and does not explicitly distinguish between a dependency being manually removed versus a "waiting on" task being completed (resolved).

We request a specific webhook event that fires only when a task's "Waiting On" dependency status changes to "Resolved" due to the completion of the blocking task.

Use Case:

External Automation: Automatically triggering a CI/CD pipeline or external notification only when all prerequisite tasks are fully completed in ClickUp.

Precision Tooling: Reducing "noise" in middleware (like Zapier or Make) by filtering out instances where a dependency was simply deleted or unlinked without the work actually being finished.

Proposed API Change:

New Webhook Event: taskDependencyResolved

Payload Enhancement: Include the task_id of the specific blocking task that was completed to trigger the resolution.

Impact:

This will provide cleaner, more reliable event-driven architectures for teams using ClickUp as a source of truth for complex, multi-stage project lifecycles.