Integrations
ClickUp
betaConnect ClickUp to map your workspace, then choose which lists to watch for task updates. Connect, watch, Brain, and writeback are separate steps.
ClickUp is a keep-your-board plug-in beside the Linear beachhead: connect, then confirm which lists to watch before monitoring or Docs Brain seed. Connecting grants OAuth access and maps workspaces you authorized — it does not by itself start list watching, Brain indexing, or two-way writeback.
Treat these as separate gates:
| Stage | What it means |
|---|---|
| Connect | OAuth succeeds; HiveBase can see authorized workspaces/teams. |
| Watch | You confirm (stamp) specific lists via Update; HiveBase monitors only those lists for task activity. |
| Brain | Docs Brain seed runs after list confirmation, scoped to stamped list IDs — not “connect and we ingest everything.” |
| Writeback | Creating or updating ClickUp tasks from HiveBase follows certification and your approval model. Do not assume two-way sync from connect alone. |
How monitoring works
After you connect and stamp lists, HiveBase can receive task and space / list / folder webhook events for watched containers, deduplicating repeated notifications.
What each stage does
| Stage | What moves | How |
|---|---|---|
| Connect | Workspace/team mapping | OAuth — no full crawl claim |
| Watch | Task + structure events for stamped lists | Webhooks (deduplicated) |
| Brain | ClickUp Docs attached to stamped lists (when seed runs after Stamp) | Separate job — scoped to stamped list IDs, not implied by connect |
| Writeback | Sparse task fields, only after live certification | Fail-closed until certified; then propose-first / approval-gated |
Writeback (not live by default)
Governed ClickUp writeback stays fail-closed until a path is
live_certified. Do not treat connect, Stamp, or Brain as enabling two-way
sync. When a certified path is enabled, outbound changes still follow your
approval model (propose-first; earn auto per
action class — never assume default full auto).
Supported field surface (when a certified write path is live) may include title, description, status, priority, due date, assignees, and project (create-or-update where supported). Treat that list as the ceiling, not a claim that every field is live today.
Connecting ClickUp
Connect ClickUp from your HiveBase workspace settings. OAuth alone finishes connect — you still choose lists to watch.
Open Settings → Integrations
In HiveBase, go to Settings → Integrations.
Open Data Sources
Select Data Sources, the home for context integrations like ClickUp.
Connect ClickUp
Click Connect ClickUp to start the OAuth flow.
Approve in ClickUp
You'll be redirected to ClickUp's OAuth consent screen. Review the access HiveBase is requesting and approve.
Confirm lists to watch
You're returned with ClickUp connected. Use Update to select the lists HiveBase should watch. Connect does not mean full sync or automatic Brain indexing — Docs Brain seed runs only after this confirmation, scoped to those lists.
Use cases
Watch the lists that matter
Stamp specific ClickUp lists so HiveBase monitors task activity there — without implying a whole-workspace crawl.
Separate Brain indexing
Docs indexing is not the same step as connect. Watching lists and seeding Brain are gated separately.
Fail-closed writes
Writeback stays dark until certified. When enabled, changes still pass through HiveBase's approval model before reaching ClickUp.
Honest connection state
Connected means authorized access. Watching, Brain, and writeback each need their own confirmation.
Disconnecting and data
To stop watching, return to Settings → Integrations → Data Sources, find the connected ClickUp integration, and disconnect it. Disconnecting revokes HiveBase's access and stops further ingestion of ClickUp events.
Reconnect anytime
You can reconnect ClickUp at any time from Settings → Integrations → Data Sources → Connect ClickUp.
FAQ
Does connecting ClickUp start two-way sync?
No. Connect maps authorized access. You still stamp lists to watch. Writeback is a separate, approval-gated capability and is not implied by OAuth alone.
Does connect seed the Brain?
No. Connect does not fire Brain Docs seed by itself. Confirming lists via Update (stamp) is a separate step; Brain indexing runs after that — and when it does, it is scoped to the lists you confirmed (not a silent whole-workspace crawl). Space/folder-level Docs outside those lists are not auto-indexed.
Will HiveBase change my ClickUp tasks without asking?
No. Writeback is fail-closed until certified, then follows HiveBase's approval model when enabled. See Trust & safety.
Which fields can HiveBase write to a ClickUp task?
Only on a live-certified write path: title, description, status, priority, due date, assignees, and project (create-or-update where supported). That is the ceiling — not a claim every field is live today.
Why don't I see duplicate updates from repeated events?
Inbound webhooks for task and structure changes are deduplicated, so repeated notifications for the same change don't produce noise.