How to Connect ClickUp to OpenClaw

ClickUp personal API tokens authenticate requests as your user account. Unlike OAuth tokens, personal tokens do not expire and grant access to all workspaces your account belongs to. Log in to ClickUp and go to your profile avatar in the bottom-left corner > Settings > Apps > API Token. If you do not see a token, click 'Generate' to create one. Copy the token — it is a long alphanumeric string. ClickUp also supports OAuth apps for multi-user integrations, but for OpenClaw automation on your own workspaces, a personal API token is the correct approach. Store it in OpenClaw as CLICKUP_API_KEY.

1# Set your ClickUp API token in OpenClaw config
2clawhub config set CLICKUP_API_KEY pk_XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
3
4# Verify it is set
5clawhub config get CLICKUP_API_KEY
6
7# Test the connection — should return your ClickUp user info
8curl -H "Authorization: pk_XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX" \
9  "https://api.clickup.com/api/v2/user"

ClickUp's API hierarchy uses numeric IDs to identify workspaces (also called teams), spaces, folders, and lists. You need these IDs to make targeted API calls. **Team/Workspace ID:** Call the `/team` endpoint to list all workspaces your account belongs to. Each workspace has a numeric ID. **Space ID:** Call `/team/{team_id}/space` to list spaces in a workspace. **List ID:** You can find list IDs in the ClickUp URL when viewing a list: `https://app.clickup.com/{team_id}/v/li/{LIST_ID}`. Or call `/space/{space_id}/list` to list all lists in a space. Note the IDs for the workspaces and lists you want to access — store them in your OpenClaw config for easy reference.

1# Get workspace/team IDs
2curl -H "Authorization: pk_YOUR_TOKEN" \
3  "https://api.clickup.com/api/v2/team"
4
5# Get spaces in a workspace
6curl -H "Authorization: pk_YOUR_TOKEN" \
7  "https://api.clickup.com/api/v2/team/YOUR_TEAM_ID/space"
8
9# Get lists in a space
10curl -H "Authorization: pk_YOUR_TOKEN" \
11  "https://api.clickup.com/api/v2/space/YOUR_SPACE_ID/list"
12
13# Find list ID from URL:
14# https://app.clickup.com/TEAM_ID/v/li/LIST_ID

Add the ClickUp integration configuration to your OpenClaw config file. This stores your team ID and frequently-used list IDs under descriptive names so workflows reference them by name rather than numeric ID. CLICKUP_API_KEY is read automatically from your environment config — do not repeat it in the YAML file. The config sets default values that workflows use when specific IDs are not provided explicitly.

1# ~/.openclaw/config.yaml
2integrations:
3  clickup:
4    team_id: "YOUR_TEAM_ID"         # Your ClickUp workspace/team ID
5    default_assignee: "YOUR_USER_ID"  # Your ClickUp user ID (from /user response)
6    # Named list references
7    lists:
8      bug_reports: "LIST_ID_1"
9      feature_requests: "LIST_ID_2"
10      content_pipeline: "LIST_ID_3"
11      task_inbox: "LIST_ID_4"
12    # Default task settings
13    defaults:
14      priority: 3           # 1=Urgent, 2=High, 3=Normal, 4=Low
15      status: "Open"        # Default status for new tasks

Test task creation and reading. ClickUp's task creation endpoint is POST `/list/{list_id}/task` with a JSON body containing the task fields. Required fields: `name`. Optional fields include `description`, `assignees` (array of user IDs), `status`, `priority`, `due_date` (Unix timestamp in milliseconds), `time_estimate`, `tags`, and `custom_fields`. For reading tasks, GET `/list/{list_id}/task` returns all tasks in a list with extensive filtering options: by assignee, status, due date range, priority, tags, and custom field values. The response is paginated — check the `last_page` field to determine if more pages exist. ClickUp's search API at `/team/{team_id}/task` allows cross-list and cross-space task searches, which is more powerful than list-specific queries for finding tasks by criteria across your entire workspace.

1# Create a task in a list
2curl -X POST \
3  -H "Authorization: pk_YOUR_TOKEN" \
4  -H "Content-Type: application/json" \
5  "https://api.clickup.com/api/v2/list/LIST_ID/task" \
6  -d '{
7    "name": "Review onboarding email sequence",
8    "description": "Check for outdated links and update copy for Q2",
9    "assignees": [USER_ID],
10    "priority": 2,
11    "due_date": 1745280000000,
12    "tags": ["content", "email"]
13  }'
14
15# Read tasks from a list (incomplete only)
16curl -H "Authorization: pk_YOUR_TOKEN" \
17  "https://api.clickup.com/api/v2/list/LIST_ID/task?include_closed=false"
18
19# Search tasks across workspace
20curl -H "Authorization: pk_YOUR_TOKEN" \
21  "https://api.clickup.com/api/v2/team/TEAM_ID/task?assignees[]=USER_ID&due_date_lt=1746489600000"

Task updates use PUT `/task/{task_id}` with a JSON body containing only the fields to change. Status updates are done the same way — set `status` to the name of the target status as defined in your ClickUp list's status configuration. Custom fields require their UUID (not their display name) in API calls. Get custom field UUIDs by calling GET `/list/{list_id}/field` — this returns all custom fields configured for that list with their IDs, types, and allowed values. Then include custom field values in task creation and update calls using the `custom_fields` array. RapidDev recommends caching the list of custom field IDs locally rather than fetching them on every API call — custom field configurations rarely change and fetching them repeatedly wastes API quota and adds latency to task creation workflows.

1# Update a task's status and priority
2curl -X PUT \
3  -H "Authorization: pk_YOUR_TOKEN" \
4  -H "Content-Type: application/json" \
5  "https://api.clickup.com/api/v2/task/TASK_ID" \
6  -d '{
7    "status": "In Progress",
8    "priority": 1,
9    "due_date": 1746057600000
10  }'
11
12# Get custom field definitions for a list
13curl -H "Authorization: pk_YOUR_TOKEN" \
14  "https://api.clickup.com/api/v2/list/LIST_ID/field"
15
16# Create a task with custom field values
17curl -X POST \
18  -H "Authorization: pk_YOUR_TOKEN" \
19  -H "Content-Type: application/json" \
20  "https://api.clickup.com/api/v2/list/LIST_ID/task" \
21  -d '{
22    "name": "Bug: Login timeout",
23    "priority": 1,
24    "custom_fields": [
25      {"id": "CUSTOM_FIELD_UUID", "value": "High"},
26      {"id": "ANOTHER_FIELD_UUID", "value": "Chrome"}
27    ]
28  }'