Feature Requests

Please search first before posting to help others find and vote for your idea!
Extend ClickUp Brain to generate context-aware mini‑apps (dynamic artifacts bound to ClickUp data)
Summary Enable ClickUp Brain to generate executable “mini‑apps” from natural language prompts and workspace context. These apps should read and write ClickUp data (Lists, Tasks, Docs, Dashboards, Custom Fields, Tags, Comments, Attachments) with permission‑aware access and run as dynamic, interactive tools embedded in ClickUp. Support both internal workflows (inside ClickUp) and external use (lightweight client portals, prototypes, single‑task utilities). Problem Brain is strong at reasoning and content generation, but many high‑value workflows still require stitching views together, manual data transforms, or repetitive actions across Lists/Docs/Tasks. Teams need small, purpose‑built interactive tools that bind to live ClickUp data, execute multi‑step actions, and share outputs without leaving ClickUp or building separate integrations. Proposed Solution Introduce Brain‑generated mini‑apps that: Bind to data: Connect to Lists, Tasks, Docs, Dashboards, Saved Filters; expose fields and relations; support query, aggregate, and live updates. Extend to external data: Connect to Google Drive, GMail, Google Calendar, and other data sources. Provide interactive UI: Forms, tables, charts, buttons, wizards; adapt based on context (assignees, statuses, tags, custom fields). Execute actions: Create/update tasks and docs, set statuses, add comments, trigger automations, post to Chat, write to custom fields. Are permission‑aware: Enforce roles/custom roles/sharing for all reads and writes. Are deployable: Launch from Chat, Task, Doc, Dashboard, or standalone panel; share internally or externally with controlled access. Are composable: Save as templates, version apps, branch/test changes, reuse across Spaces. Example Mini‑Apps NDA Generator: Pick a template, fill variables (party names, dates, jurisdiction, term), render a final NDA, attach to the Task/Doc, post a Chat message, and open a “Sign & Track” task with due dates. Marketing Spend Planner: A calculator bound to campaign Lists and budget fields; model scenarios, generate a summary Doc with charts, and create tasks to adjust budgets and assign owners. Contract Clause Analyzer: Paste text or select a Doc; the app highlights risky clauses, suggests redlines, and opens subtasks for each recommended change, citing sections. KPI Narrative Builder: Read Dashboard widgets; explain trends, anomalies, and risks; propose follow‑up tasks with owners and dates; post a summary to the channel. Spec‑to‑Plan Converter: Pull a Doc, extract milestones, produce a dependency graph and sequenced subtasks, each citing source sections; dry‑run changes, then commit. Bug Triage Console: Intake reports (attachments, text), group by component/severity using workspace fields, mass‑create/update tasks, and publish a triage summary back to Chat. Governance & Safety Admin controls: Enable/disable Brain mini‑apps; define scopes (space/folder/list); approve data bindings and actions; set external sharing rules. Audit & observability: Log prompts, context accessed, data mutations, and app versions; exportable for compliance. Data boundaries: No cross‑workspace leakage; retention and deletion aligned with ClickUp policies; strict permission inheritance. Cost/performance: Rate limits, quotas, resource controls; “dry run” previews for bulk changes. Success Metrics Reduced time‑to‑action from prompt to committed changes. Lower app‑switching; faster decisions in Chat/Tasks/Docs. Improved data quality via structured inputs and governed bulk updates. Adoption of mini‑apps across teams; increased external collaboration.
4
·
ClickUp AI
·
building now
MCP : add time entries / time_spent in clickup_filter_tasks
We use the ClickUp MCP server with Claude to answer project questions, for example checking tracked time against client quotes. Tracked time is currently hard to retrieve through the MCP server, and the workarounds put unnecessary load on your API. What we observed clickup_get_time_entries only filters by task_id, dates, assignee and billable status. There is no list_id, folder_id or space_id filter, although the REST endpoint GET /api/v2/team/{team_id}/time_entries supports location filters such as list_id. Without a task_id, results are capped at 50 entries per call, and the tool exposes no pagination parameter, so totals are silently truncated. time_spent is not returned by clickup_filter_tasks, and it comes back null from the bulk task fetch (task.get_many) even for tasks that have tracked time. Impact To check one quarter of tracked time for three client folders (over 100 tasks), we had to query tasks one by one 🐌 : more than 60 separate requests for a single report, where one request per list would have been enough :) Request Add list_id / folder_id / space_id filters to the time entries tool, with pagination (cursor or page) so results are never silently truncated. Return time_spent (and time_estimate) in task list results and in the bulk task operator. Optionally, offer an aggregated mode (total per task, list or user) so individual entries do not need to be transferred. This would significantly reduce the number of calls hitting your API and make time-tracking reports reliable for MCP users.
0
·
ClickUp AI
Load More
→