clickup

1# ClickUp
2 
3## Purpose
4Work the user's ClickUp: list workspaces ("teams") (`teams`), list tasks in a list (`tasks`), and create tasks (`create`). ClickUp's API calls workspaces "teams": `teams` returns workspaces.
5 
6## Tooling
7All commands go through `bin/clickup.py`:
8 
9```bash
10bin/clickup.py teams                    # workspaces (id, name)
11bin/clickup.py tasks --list 123456789   # tasks in a list (name, status, due date)
12bin/clickup.py create --list 123456789 --name "Ship the thing"   # create a task
13```
14 
15List ids come from ClickUp (open a list → the URL contains its numeric id). Use `teams` → space → folder → list navigation in ClickUp's UI to find the right list.
16 
17## Auth
18- Provider id: `clickup` (credential is collected as `custom.clickup`)
19- Collection: personal API token via the secure credential flow (`credentials.request_api_access`): create one in ClickUp → avatar → Settings → Apps → API Token (tokens start with `pk_`)
20- Connect placement: `custom_header:Authorization` (ClickUp takes the **raw** token in the `Authorization` header: no `Bearer` prefix)
21- Allowed hosts: `api.clickup.com`
22- Status check: `bin/clickup.py teams` (a successful list proves the token works)
23 
24## Operating Rules
251. `create` is a write: confirm the task name and destination list with the user before running, unless standing permission exists.
262. Reading (`teams`, `tasks`) needs no confirmation.
27…