Source connector
ClickUp connector
ClickUp integration for databases, warehouses and BI tools
Work management platform for tasks, docs, and operations. Datrise captures ClickUp entities such as tasks, custom fields, statuses, docs, and workspace execution data, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.
The ClickUp API v2 authenticates with OAuth 2.0, personal access token, incremental runs key on date_updated_gt, and ClickUp caps calls at 100 requests/minute per token on Free/Unlimited/Business plans, 1,000/minute on Business Plus, 10,000/minute on Enterprise.
Of the 5 objects, 5 sync as upserts keyed on the primary key and 0 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `clickup_tasks`) with a schema derived from the ClickUp API rather than a flattened CSV, in any of the 43 supported destinations.
Datrise is in early access: pick a destination below to open the ClickUp pipeline page, and join the waitlist to get the ClickUp connector (Work management) with guided onboarding.
What ClickUp data Datrise extracts
Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.
| Object | Landing table | Sync mode |
|---|---|---|
| tasks | clickup_tasks | Upsert by primary key, incremental on updated-at |
| custom fields | clickup_custom_fields | Upsert by primary key, incremental on updated-at |
| statuses | clickup_statuses | Upsert by primary key, incremental on updated-at |
| docs | clickup_docs | Upsert by primary key, incremental on updated-at |
| workspace execution data | clickup_workspace_execution_data | Upsert by primary key, incremental on updated-at |
ClickUp API: setup facts for the connector
Verified against the vendor documentation on 2026-09-02. Unknown values are left blank rather than guessed.
| API | ClickUp API v2 |
|---|---|
| Authentication | OAuth 2.0, personal access token — A personal API token (prefixed `pk_`, sent as a raw `Authorization` header) suits single-user scripts, while multi-user apps use OAuth2 authorization-code with a `Bearer` access token. |
| Pagination | page — `GET /task` and similar list endpoints take a zero-indexed `page` parameter, return up to 100 items per page, and include a `last_page` boolean in the response to signal when to stop. |
| Rate limit | 100 requests/minute per token on Free/Unlimited/Business plans, 1,000/minute on Business Plus, 10,000/minute on Enterprise |
| Incremental cursor | date_updated_gt — `GET /task` accepts `date_updated_gt`/`date_updated_lt` (and `date_created_gt`/`date_created_lt`) as Unix-millisecond filters for delta pulls. |
| Webhooks | Yes — Webhooks |
| Bulk export | No |
| Deletes detectable | Yes — The `taskDeleted` webhook event reports task deletions; without an active webhook, `GET /task` simply omits deleted tasks with no separate deleted-records endpoint to diff against. |
What bites when replicating ClickUp
- `date_updated_gt`/`date_updated_lt` expect Unix time in milliseconds, not seconds; passing a seconds-based epoch silently produces a window that's off by a factor of 1,000 rather than an error.
- The rate limit is per token, not per app: 100 requests/minute on the Free/Unlimited/Business tiers is shared by every integration authenticating with that same personal token or OAuth connection.
- Deletions only surface through the `taskDeleted` webhook event; a connector relying solely on `GET /task` polling has no deleted-records feed and must diff the full set of task IDs between runs to notice removals.
- List pagination signals the end of results via the `last_page` boolean in the response rather than an empty `tasks` array, so code that stops on an empty page instead of checking `last_page` can loop forever or exit one page early.
Popular destinations for ClickUp
Choose a destination below to open the ready pipeline page.
- AAirtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline - AAmazon Athena
Serverless SQL over S3 data lake tables.
View pipeline - AAmazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline - AAmazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline - AAmazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline - AAmazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline - AApache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline - AAzure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline - AAzure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline
ClickUp connector FAQ
- What ClickUp data does the connector extract?
- 5 objects: tasks, custom fields, statuses, docs and workspace execution data. Each lands in its own table with types preserved; history-style objects (0) load as append-only streams.
- Is the ClickUp integration incremental?
- Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
- Where can I load ClickUp data?
- Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each ClickUp → destination pair has its own page with the object-to-table mapping.
Related Work management sources
Other sources in the same category, each with its own connector page.
Early access
Launch your ClickUp pipeline with guided onboarding
Join the waitlist to get priority access for ClickUp integrations with guided setup, schema-aware mapping, and production-grade incremental sync.