--- name: clickup-automation-3aa9ef7527ff description: "Automate ClickUp project management including tasks, spaces, folders, lists, comments, and team operations via Rube MCP (Composio). Always search tools first for current schemas." risk: critical source: community date_added: "2026-02-27" --- # ClickUp Automation via Rube MCP Automate ClickUp project management workflows including task creation and updates, workspace hierarchy navigation, comments, and team member management through Composio's ClickUp toolkit. ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) - Active ClickUp connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `clickup` - Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas ## Setup **Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. 1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds 2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `clickup` 3. If connection is not ACTIVE, follow the returned auth link to complete ClickUp OAuth 4. Confirm connection status shows ACTIVE before running any workflows ## Core Workflows ### 1. Create and Manage Tasks **When to use**: User wants to create tasks, subtasks, update task properties, or list tasks in a ClickUp list. **Tool sequence**: 1. `CLICKUP_GET_AUTHORIZED_TEAMS_WORKSPACES` - Get workspace/team IDs [Prerequisite] 2. `CLICKUP_GET_SPACES` - List spaces in the workspace [Prerequisite] 3. `CLICKUP_GET_FOLDERS` - List folders in a space [Prerequisite] 4. `CLICKUP_GET_FOLDERLESS_LISTS` - Get lists not inside folders [Optional] 5. `CLICKUP_GET_LIST` - Validate list and check available statuses [Prerequisite] 6. `CLICKUP_CREATE_TASK` - Create a task in the target list [Required] 7. `CLICKUP_CREATE_TASK` (with `parent`) - Create subtask under a parent task [Optional] 8. `CLICKUP_UPDATE_TASK` - Modify task status, assignees, dates, priority [Optional] 9. `CLICKUP_GET_TASK` - Retrieve full task details [Optional] 10. `CLICKUP_GET_TASKS` - List all tasks in a list with filters [Optional] 11. `CLICKUP_DELETE_TASK` - Permanently remove a task [Optional] **Key parameters for CLICKUP_CREATE_TASK**: - `list_id`: Target list ID (integer, required) - `name`: Task name (string, required) - `description`: Detailed task description - `status`: Must exactly match (case-sensitive) a status name configured in the target list - `priority`: 1 (Urgent), 2 (High), 3 (Normal), 4 (Low) - `assignees`: Array of user IDs (integers) - `due_date`: Unix timestamp in milliseconds - `parent`: Parent task ID string for creating subtasks - `tags`: Array of tag name strings - `time_estimate`: Estimated time in milliseconds **Pitfalls**: - `status` is case-sensitive and must match an existing status in the list; use `CLICKUP_GET_LIST` to check available statuses - `due_date` and `start_date` are Unix timestamps in **milliseconds**, not seconds - Subtask `parent` must be a task (not another subtask) in the same list - `notify_all` triggers watcher notifications; set to false for bulk operations - Retries can create duplicates; track created task IDs to avoid re-creation - `custom_item_id` for milestones (ID 1) is subject to workspace plan quotas ### 2. Navigate Workspace Hierarchy **When to use**: User wants to browse or manage the ClickUp workspace structure (Workspaces > Spaces > Folders > Lists). **Tool sequence**: 1. `CLICKUP_GET_AUTHORIZED_TEAMS_WORKSPACES` - List all accessible workspaces [Required] 2. `CLICKUP_GET_SPACES` - List spaces within a workspace [Required] 3. `CLICKUP_GET_SPACE` - Get details for a specific space [Optional] 4. `CLICKUP_GET_FOLDERS` - List folders in a space [Required] 5. `CLICKUP_GET_FOLDER` - Get details for a specific folder [Optional] 6. `CLICKUP_CREATE_FOLDER` - Create a new folder in a space [Optional] 7. `CLICKUP_GET_FOLDERLESS_LISTS` - List lists not inside any folder [Required] 8. `CLICKUP_GET_LIST` - Get list details including statuses and custom fields [Optional] **Key parameters**: - `team_id`: Workspace ID from GET_AUTHORIZED_TEAMS_WORKSPACES (required for spaces) - `space_id`: Space ID (required for folders and folderless lists) - `folder_id`: Folder ID (required for GET_FOLDER) - `list_id`: List ID (required for GET_LIST) - `archived`: Boolean filter for archived/active items **Pitfalls**: - ClickUp hierarchy is: Workspace (Team) > Space > Folder > List > Task - Lists can exist directly under Spaces (folderless) or inside Folders - Must use `CLICKUP_GET_FOLDERLESS_LISTS` to find lists not inside folders; `CLICKUP_GET_FOLDERS` only returns folders - `team_id` in ClickUp API refers to the Workspace ID, not a user group ### 3. Add Comments to Tasks **When to use**: User wants to add comments, review existing comments, or manage comment threads on tasks. **Tool sequence**: 1. `CLICKUP_GET_TASK` - Verify task exists and get task_id [Prerequisite] 2. `CLICKUP_CREATE_TASK_COMMENT` - Add a new comment to the task [Required] 3. `CLICKUP_GET_TASK_COMMENTS` - List existing comments on the task [Optional] 4. `CLICKUP_UPDATE_COMMENT` - Edit comment text, assignee, or resolution status [Optional] **Key parameters for CLICKUP_CREATE_TASK_COMMENT**: - `task_id`: Task ID string (required) - `comment_text`: Comment content with ClickUp formatting support (required) - `assignee`: User ID to assign the comment to (required) - `notify_all`: true/false for watcher notifications (required) **Key parameters for CLICKUP_GET_TASK_COMMENTS**: - `task_id`: Task ID string (required) - `start` / `start_id`: Pagination for older comments (max 25 per page) **Pitfalls**: - `CLICKUP_CREATE_TASK_COMMENT` requires all four fields: `task_id`, `comment_text`, `assignee`, and `notify_all` - `assignee` on a comment assigns the comment (not the task) to that user - Comments are paginated at 25 per page; use `start` (Unix ms) and `start_id` for older pages - `CLICKUP_UPDATE_COMMENT` requires all four fields: `comment_id`, `comment_text`, `assignee`, `resolved` ### 4. Manage Team Members and Assignments **When to use**: User wants to view workspace members, check seat utilization, or look up user details. **Tool sequence**: 1. `CLICKUP_GET_AUTHORIZED_TEAMS_WORKSPACES` - List workspaces and get team_id [Required] 2. `CLICKUP_GET_WORKSPACE_SEATS` - Check seat utilization (members vs guests) [Required] 3. `CLICKUP_GET_TEAMS` - List user groups within the workspace [Optional] 4. `CLICKUP_GET_USER` - Get details for a specific user (Enterprise only) [Optional] 5. `CLICKUP_GET_CUSTOM_ROLES` - List custom permission roles [Optional] **Key parameters**: - `team_id`: Workspace ID (required for all team operations) - `user_id`: Specific user ID for GET_USER - `group_ids`: Comma-separated group IDs to filter teams **Pitfalls**: - `CLICKUP_GET_WORKSPACE_SEATS` returns seat counts, not member details; distinguish members from guests - `CLICKUP_GET_TEAMS` returns user groups, not workspace members; empty groups does not mean no members - `CLICKUP_GET_USER` is only available on ClickUp Enterprise Plan - Must repeat workspace seat queries for each workspace in multi-workspace setups ### 5. Filter and Query Tasks **When to use**: User wants to find tasks with specific filters (status, assignee, dates, tags, custom fields). **Tool sequence**: 1. `CLICKUP_GET_TASKS` - Filter tasks in a list with multiple criteria [Required] 2. `CLICKUP_GET_TASK` - Get full details for individual tasks [Optional] **Key parameters for CLICKUP_GET_TASKS**: - `list_id`: List ID (integer, required) - `statuses`: Array of status strings to filter by - `assignees`: Array of user ID strings - `tags`: Array of tag name strings - `due_date_gt` / `due_date_lt`: Unix timestamp in ms for date range - `include_closed`: Boolean to include closed tasks - `subtasks`: Boolean to include subtasks - `order_by`: "id", "created", "updated", or "due_date" - `page`: Page number starting at 0 (max 100 tasks per page) **Pitfalls**: - Only tasks whose home list matches `list_id` are returned; tasks in sublists are not included - Date filters use Unix timestamps in milliseconds - Status strings must match exactly; use URL encoding for spaces (e.g., "to%20do") - Page numbering starts at 0; each page returns up to 100 tasks - `custom_fields` filter accepts an array of JSON strings, not objects ## Common Patterns ### ID Resolution Always resolve names to IDs through the hierarchy: - **Workspace name -> team_id**: `CLICKUP_GET_AUTHORIZED_TEAMS_WORKSPACES` and match by name - **Space name -> space_id**: `CLICKUP_GET_SPACES` with `team_id` - **Folder name -> folder_id**: `CLICKUP_GET_FOLDERS` with `space_id` - **List name -> list_id**: Navigate folders or use `CLICKUP_GET_FOLDERLESS_LISTS` - **Task name -> task_id**: `CLICKUP_GET_TASKS` with `list_id` and match by name ### Pagination - `CLICKUP_GET_TASKS`: Page-based with `page` starting at 0, max 100 tasks per page - `CLICKUP_GET_TASK_COMMENTS`: Uses `start` (Unix ms) and `start_id` for cursor-based paging, max 25 per page - Continue fetching until response returns fewer items than the page size ## Known Pitfalls ### ID Formats - Workspace/Team IDs are large integers - Space, folder, and list IDs are integers - Task IDs are alphanumeric strings (e.g., "9hz", "abc123") - User IDs are integers - Comment IDs are integers ### Rate Limits - ClickUp enforces rate limits; bulk task creation can trigger 429 responses - Honor `Retry-After` header when present - Set `notify_all=false` for bulk operations to reduce notification load ### Parameter Quirks - `team_id` in the API means Workspace ID, not a user group - `status` on tasks is case-sensitive and list-specific - Dates are Unix timestamps in **milliseconds** (multiply seconds by 1000) - `priority` is an integer 1-4 (1=Urgent, 4=Low), not a string - `CLICKUP_CREATE_TASK_COMMENT` marks `assignee` and `notify_all` as required - To clear a task description, pass a single space `" "` to `CLICKUP_UPDATE_TASK` ### Hierarchy Rules - Subtask parent must not itself be a subtask - Subtask parent must be in the same list - Lists can be folderless (directly in a Space) or inside a Folder - Subitem boards are not supported by CLICKUP_CREATE_TASK ## Quick Reference | Task | Tool Slug | Key Params | |------|-----------|------------| | List workspaces | `CLICKUP_GET_AUTHORIZED_TEAMS_WORKSPACES` | (none) | | List spaces | `CLICKUP_GET_SPACES` | `team_id` | | Get space details | `CLICKUP_GET_SPACE` | `space_id` | | List folders | `CLICKUP_GET_FOLDERS` | `space_id` | | Get folder details | `CLICKUP_GET_FOLDER` | `folder_id` | | Create folder | `CLICKUP_CREATE_FOLDER` | `space_id`, `name` | | Folderless lists | `CLICKUP_GET_FOLDERLESS_LISTS` | `space_id` | | Get list details | `CLICKUP_GET_LIST` | `list_id` | | Create task | `CLICKUP_CREATE_TASK` | `list_id`, `name`, `status`, `assignees` | | Update task | `CLICKUP_UPDATE_TASK` | `task_id`, `status`, `priority` | | Get task | `CLICKUP_GET_TASK` | `task_id`, `include_subtasks` | | List tasks | `CLICKUP_GET_TASKS` | `list_id`, `statuses`, `page` | | Delete task | `CLICKUP_DELETE_TASK` | `task_id` | | Add comment | `CLICKUP_CREATE_TASK_COMMENT` | `task_id`, `comment_text`, `assignee` | | List comments | `CLICKUP_GET_TASK_COMMENTS` | `task_id`, `start`, `start_id` | | Update comment | `CLICKUP_UPDATE_COMMENT` | `comment_id`, `comment_text`, `resolved` | | Workspace seats | `CLICKUP_GET_WORKSPACE_SEATS` | `team_id` | | List user groups | `CLICKUP_GET_TEAMS` | `team_id` | | Get user details | `CLICKUP_GET_USER` | `team_id`, `user_id` | | Custom roles | `CLICKUP_GET_CUSTOM_ROLES` | `team_id` | ## When to Use This skill is applicable to execute the workflow or actions described in the overview. --- ## AGI Framework Integration > **Adapted for [@techwavedev/agi-agent-kit](https://www.npmjs.com/package/@techwavedev/agi-agent-kit)** > Original source: [antigravity-awesome-skills](https://github.com/sickn33/antigravity-awesome-skills) ### Memory-First Protocol Cache workflow configurations and automation patterns. Retrieve prior pipeline designs to avoid re-building similar flows from scratch. ```bash # Check for prior workflow/automation context before starting python3 execution/memory_manager.py auto --query "automation patterns and workflow configurations for Clickup Automation" ``` ### Storing Results After completing work, store workflow/automation decisions for future sessions: ```bash python3 execution/memory_manager.py store \ --content "Workflow: automated data pipeline with retry logic, dead-letter queue, and Slack alerts on failure" \ --type technical --project \ --tags clickup-automation workflow ``` ### Multi-Agent Collaboration Share workflow state with other agents so they can trigger, monitor, or extend the automation. ```bash python3 execution/cross_agent_context.py store \ --agent "" \ --action "Workflow automation deployed — pipeline processing 1000+ events/day with 99.9% success rate" \ --project ``` ### Playbook Engine Combine this skill with others using the Playbook Engine (`execution/workflow_engine.py`) for guided multi-step automation with progress tracking. --- Source attribution: techwavedev Original project: https://github.com/techwavedev/agi-agent-kit/blob/58f5d95434a1adc8b41a4f391d32d95311e54936/templates/skills/extended/workflow/clickup-automation/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Dave AI. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to the Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright 2024-2026 Elton Machado (TechWaveDev) Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. # Dave AI resource metadata Creator / publisher: techwavedev Original project: https://github.com/techwavedev/agi-agent-kit/blob/58f5d95434a1adc8b41a4f391d32d95311e54936/templates/skills/extended/workflow/clickup-automation/SKILL.md Attribution basis: Source repository record Fields of work: Operations, Project & Program Management Roles: Business Process Analyst, Operations Manager, Project Manager Specialties: API, Backend, Design, DevOps, Frontend, Git Tools: ClickUp, Rube Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: 26e00c58a39e5ae77eef4d38d7d1e617d4cf3f9469eee7d020f8c2ed87d44f0f