ClickUp | Operate As Docs

Connect your client's ClickUp with a key they paste, and call its API through Operate As.

Website: clickup.com
Connects by: Pasting a Personal API token
Category: Projects and tasks
Services: 1
Tools: 137

Service	Key	Base URL
ClickUp	`clickup`	`https://api.clickup.com/api/v2`

Connecting

Your client makes a Personal API token in their ClickUp settings and pastes it on their link. Operate As tries it with ClickUp before saving it, and stores it encrypted. See Services connected with an API key.

Check they're connected

curl https://api.operate.as/v1/me/clients \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

curl https://api.operate.as/v1/me/clients \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

Response

[
  {
    "id": "6f1c2a7e-...",
    "name": "Miller Dental",
    "services": [
      "clickup"
    ]
  }
]

[  {    "id": "6f1c2a7e-...",    "name": "Miller Dental",    "services": [      "clickup"    ]  }]

Permissions

What the client reads	Permission it asks for
Use the ClickUp key you paste, with only the access you gave that key	Chosen on the provider's screen

Tools

Install ClickUp's typed package for your language:

pip install operate-as-clickup

pip install operate-as-clickup

Run clickup.add_dependency

curl -X POST https://api.operate.as/v1/actions/clickup.add_dependency \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "clientId": "6f1c2a7e-...",
    "input": {
      "task_id": "<task_id>"
    }
  }'

curl -X POST https://api.operate.as/v1/actions/clickup.add_dependency \  -H "Authorization: Bearer $OPERATE_AS_API_KEY" \  -H "Content-Type: application/json" \  -d '{    "clientId": "6f1c2a7e-...",    "input": {      "task_id": "<task_id>"    }  }'

Shows the required inputs. Every input, with its JSON Schema: GET /v1/actions/clickup.add_dependency

Response

{
  "status": 200,
  "data": {
    "…": "the service's own response"
  },
  "encoding": "json"
}

{  "status": 200,  "data": {    "…": "the service's own response"  },  "encoding": "json"}

Pass-through

Paths continue from https://api.clickup.com/api/v2. Your Operate As key goes in Authorization; the client's access is added for you.

See Pass-through requests for the full request and response format.

Call any endpoint

curl "https://api.operate.as/v1/clients/6f1c2a7e-.../clickup/user" \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

curl "https://api.operate.as/v1/clients/6f1c2a7e-.../clickup/user" \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

Response

{
  "status": 200,
  "data": {
    "…": "the service's own response"
  },
  "encoding": "json"
}

{  "status": 200,  "data": {    "…": "the service's own response"  },  "encoding": "json"}

When access ends

A key works until your client deletes it in ClickUp. They can paste a new one on the same link at any time, and your workflows carry on without changes.

See Keeping access alive and Removing access.

Calls answer, once the key is deleted

{
  "status": 401,
  "data": {
    "…": "the service's own error"
  },
  "encoding": "json"
}

{  "status": 401,  "data": {    "…": "the service's own error"  },  "encoding": "json"}