Tadeo Gómez Coll
When a Doc (or Doc page) is linked to a task — either by adding the task as a Location on the Doc, or via the "Linked Docs" section on the task — that relationship isn't readable anywhere outside the UI. It doesn't appear in the Get Task API response, it can't be referenced as a dynamic value in Automations, and there's no endpoint to attach an
existing
Doc to a task programmatically (I see this has been requested before: "attach existing ClickUp doc to a task," still not on the roadmap).
This makes it impossible to build any automation that depends on "which Doc is linked to this task" — for example, automatically creating a follow-up task in another list and carrying over the same linked Doc. Right now the only way to move that link anywhere is to manually copy the Doc's URL into a text field.
Requested:
  1. Include linked Docs (with their page-level URLs) in the Get Task API response.
  2. Allow attaching an existing Doc/page to a task as a Location via the API.
  3. Let Automations reference "this task's linked Doc(s)" as a dynamic value, and support linking a Doc to a task as an Automation action (not just creating a brand-new Doc).
Use case: we have a task that tracks a script (with the script itself linked as a Doc), and when that task reaches a certain status, we want to auto-create a task in another list with the same Doc linked. Today this can't be automated at all because the relationship isn't exposed anywhere.
---
Want me to also send this to your ClickUp feedback board directly if you give me a link, or is copy-paste what you need?