Problem
A lot of the "what am I working on and why" context lives in a task/project manager. For ClickUp users, tasks, subtasks, comments, and docs capture goals, status, decisions, and history — but OpenWiki has no way to bring that in, so the agent has no view of the work itself.
Proposal
Add an optional ClickUp connector (ClickUp API v2) that can import and incrementally sync workspace content into OpenWiki.
It could support:
- Selecting one or more workspaces/spaces/folders/lists to import
- Importing tasks and subtasks with title, description, status, assignees, tags, priority, due dates, custom fields, timestamps, and links back to the source task
- Importing task comments and ClickUp Docs
- Incremental sync with configurable scope (space/list allowlists), time windows, and filtering/redaction controls
- Structuring imported content so projects, tasks, decisions, and recurring themes are discoverable in OpenWiki
Auth / scope notes
ClickUp supports both a personal API token and an OAuth2 app flow; OAuth2 would be the better fit for a shared connector. The API is organized as workspace (team) → space → folder → list → task, so a scope selector along that hierarchy would keep imports focused.
Example use case
My tasks and their comment history are where the real status and rationale live. Connecting ClickUp to OpenWiki would let me ask "what's the state of this project and what changed?" and get an answer grounded in the actual tasks and discussion, with links back.
Happy to help test or clarify the most useful task/comment/doc fields and sync behavior.
Problem
A lot of the "what am I working on and why" context lives in a task/project manager. For ClickUp users, tasks, subtasks, comments, and docs capture goals, status, decisions, and history — but OpenWiki has no way to bring that in, so the agent has no view of the work itself.
Proposal
Add an optional ClickUp connector (ClickUp API v2) that can import and incrementally sync workspace content into OpenWiki.
It could support:
Auth / scope notes
ClickUp supports both a personal API token and an OAuth2 app flow; OAuth2 would be the better fit for a shared connector. The API is organized as workspace (team) → space → folder → list → task, so a scope selector along that hierarchy would keep imports focused.
Example use case
My tasks and their comment history are where the real status and rationale live. Connecting ClickUp to OpenWiki would let me ask "what's the state of this project and what changed?" and get an answer grounded in the actual tasks and discussion, with links back.
Happy to help test or clarify the most useful task/comment/doc fields and sync behavior.