ClickUp

In ClickUp, click your avatar in the bottom-left corner to open your account menu. Click 'Settings'. In the left sidebar of Settings, click 'Apps'. Scroll down to find the 'API Token' section. Click 'Generate' if you don't have a token yet, or 'Regenerate' to create a new one (note: regenerating invalidates the old token). Click the copy icon next to the token to copy it to your clipboard. The personal API token starts with pk_ followed by a long alphanumeric string. This token has the same permissions as your ClickUp account — it can read and modify any workspace, space, list, or task your account has access to. Keep it private. If you need the integration to work on behalf of multiple users (not just your account), consider ClickUp's OAuth 2.0 flow instead — but for a single-user or agency integration, the personal token is the simplest path.

In Bubble, go to Plugins → API Connector → click 'Add another API'. Name the group 'ClickUp API'. In the API base URL field, enter: https://api.clickup.com/api/v2. Now add a shared header. This is where most developers make the first mistake: the key is Authorization, and the value is JUST the token — no 'Bearer' prefix, no 'Basic' prefix. For example: pk_1234567890abcdef. Using 'Bearer pk_1234...' or 'Basic pk_1234...' causes HTTP 401 on every call. Check the Private checkbox on the Authorization header. This keeps the token off the client side. You do not need a Content-Type header at the group level for GET requests — add it per-call for POST requests that send a body. The base URL https://api.clickup.com/api/v2 applies to all calls in this group, so individual calls only need the path suffix (e.g., /team for the team list).

1API Connector Group: ClickUp API
2  Base URL: https://api.clickup.com/api/v2
3
4  Shared header:
5  - Authorization: pk_your_actual_token_here  [Private: YES]
6    (NO 'Bearer' prefix — just the raw token value)

ClickUp's data is organized hierarchically: Workspace (Team) → Spaces → Folders → Lists → Tasks. To query tasks, you need to work down this hierarchy, and the IDs are not visible in the ClickUp UI by default. Start with the team (workspace) level: add a call named 'Get Teams' with Method GET and URL /team. Set 'Use as' to 'Data'. Click 'Initialize call'. The response includes an array of teams, each with an id and name. Your team ID is a numeric ID in the response. Note it down — you will use it in the next call. Next, add a call 'Get Spaces' with Method GET and URL /team/<team_id>/space — set team_id as a parameter. Initialize with your actual team ID. The response lists your spaces (equivalent to departments or clients in ClickUp) each with an id and name. Copy the space ID for the space containing the lists you want to access from Bubble.

1Call 1: GET /team
2Returns: { "teams": [{ "id": "9012345678", "name": "My Workspace" }] }
3
4Call 2: GET /team/9012345678/space
5Returns: {
6  "spaces": [
7    { "id": "90120000001", "name": "Client Projects" },
8    { "id": "90120000002", "name": "Internal Operations" }
9  ]
10}

Add a new call named 'Get Tasks'. Set Method to GET and URL to /list/<list_id>/task — set list_id as a dynamic parameter. Set 'Use as' to 'Data'. ClickUp supports optional query parameters for filtering tasks: add parameters for status (filter by status name), page (for pagination — ClickUp returns max 100 tasks per page), order_by (e.g., 'due_date'), and reverse (true to sort descending). These are query string parameters, not body parameters — add them in the 'Parameters' section of the call, not in a body. Initialize with a real list ID that has tasks. After initialization, Bubble detects the 'tasks' array with fields like: tasks[0].id, tasks[0].name, tasks[0].status.status, tasks[0].assignees[0].username, tasks[0].due_date, tasks[0].priority.priority. Note that due_date comes back as a 13-digit millisecond epoch string like '1714003200000' — to display it as a date in Bubble, divide by 1000 and use Bubble's 'formatted as date' operator on the resulting number treated as a Unix timestamp. Use the 'page' parameter to implement pagination if you have more than 100 tasks.

1GET /list/<list_id>/task
2
3Query parameters:
4  - list_id: <dynamic: your list ID>  (path parameter)
5  - status: <dynamic: status_filter>   (optional, e.g., 'in progress')
6  - page: 0                            (0-indexed, increment for pagination)
7  - order_by: due_date                 (sort field)
8  - reverse: true                      (newest/latest first)
9  - include_closed: false              (exclude completed tasks)

Add a new call named 'Create Task'. Set Method to POST and URL to /list/<list_id>/task. Set 'Use as' to 'Action'. Add a Content-Type header at the call level (not the shared headers): key = Content-Type, value = application/json. Check 'Send arbitrary data' in the Body section. The task creation body requires: name (text), and optionally description (plain text string — unlike Jira, ClickUp does NOT require ADF format), due_date (millisecond epoch as a number), and priority (integer: 1=urgent, 2=high, 3=normal, 4=low). The critical issue for due dates: Bubble stores dates in seconds internally but ClickUp expects milliseconds. In the workflow where you call this API, you need to multiply the Bubble date's Unix timestamp by 1000 before passing it as the due_date parameter. In Bubble's formula: Input Due Date's value:unix timestamp * 1000. Initialize the call with a real list ID and example values including a valid millisecond timestamp to confirm Bubble detects the response (the created task with its id).

1POST /list/<list_id>/task
2
3Additional call-level header:
4  Content-Type: application/json
5
6Body:
7{
8  "name": "<dynamic: task_name>",
9  "description": "<dynamic: task_description>",
10  "due_date": <dynamic: due_date_milliseconds>,
11  "due_date_time": false,
12  "priority": <dynamic: priority_integer>,
13  "assignees": [],
14  "status": "to do"
15}

Now connect the ClickUp task query to your Bubble UI. Add a Repeating Group to your page. Set Type of content to the response type from the Get Tasks call. Set Data source to 'Get data from an external API' → select 'ClickUp API - Get Tasks'. In the parameter prompt, enter the list ID you want to display (this can be dynamic based on the current user's stored list ID in Bubble's database). Inside the Repeating Group, add elements for each task field: a text element bound to 'Current cell's tasks's name' for the task name, another for 'Current cell's tasks's status's status' for the status value. For the due date, the ClickUp due_date field is a string of milliseconds — in Bubble, to convert it to a readable date, use a calculation: extract the due_date value, treat it as a number, divide by 1000, and use Bubble's :formatted as date. The easiest way: add a Text element and set its value to 'Current cell's tasks's due_date / 1000 :formatted as MM/DD/YYYY'. Note: be careful not to make per-row API calls inside the Repeating Group — this pattern quickly exhausts the 100 requests/minute rate limit. Load all tasks once for the list, not one call per task. RapidDev has built dozens of ClickUp-powered Bubble client portals — if your data model or hierarchy is complex, book a free scoping call at rapidevelopers.com/contact.

1Repeating Group:
2  Type of content: ClickUp API - Get Tasks's tasks
3  Data source: Get data from external API → ClickUp API - Get Tasks
4    → list_id: [your list ID or dynamic value]
5
6Inside Repeating Group cells:
7  Text element 1: Current cell's tasks's name
8  Text element 2: Current cell's tasks's status's status
9  Text element 3 (due date display):
10    → Current cell's tasks's due_date (as number) / 1000
11       :formatted as MM/DD/YYYY