ClickUp

!ClickUp

Access ClickUp via the ClickUp API with managed API key authentication. Manage tasks, lists, spaces, folders, comments, goals, and workspace data from chat.

This skill uses ClawLink for hosted connection flows and credentials so you do not need to configure ClickUp API access yourself.

Setup in 3 Steps

How It Works

┌─────────────────┐     ┌──────────────┐     ┌──────────────────┐
│   OpenClaw      │────▶│   ClawLink   │────▶│    ClickUp API    │
│   (User Chat)   │     │   (API Key)  │     │   (Tasks)         │
└─────────────────┘     └──────────────┘     └──────────────────┘
          │                       │                       │
          │  1. Install Plugin    │                       │
          │  2. Pair Device       │                       │
          │3. Connect ClickUp   │                       │
          │                       │  4. Secure Proxy │
          │                       │  5. API Requests        │
          │                       │                       │
          ▼                       ▼                       ▼
    ┌──────────┐           ┌──────────┐           ┌──────────┐
    │  SKILL   │           │ Dashboard│           │ ClickUp │
    │  File    │           │ Auth     │           │ Workspace│
    └──────────┘           └──────────┘           └──────────┘

Install

Install the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.

openclaw plugins install clawhub:clawlink-plugin
openclaw config set tools.alsoAllow '["clawlink-plugin"]' --strict-json
openclaw gateway restart

Then tell the user: "OpenClaw has been restarted. Send /new as a standalone message to start a fresh chat, then ask for ClickUp again."

Quick Start

# List integrations
clawlink_list_integrations

# List ClickUp tools
clawlink_list_tools --integration clickup

# Search for a specific tool
clawlink_search_tools --query "task" --integration clickup

Authentication

All ClickUp tool calls are authenticated automatically by ClawLink using the user's connected ClickUp API credentials.

No API key is required in chat. ClawLink stores the API key securely and injects it into every ClickUp API request on the user's behalf.

Getting Connected

1. Install the ClawLink plugin (see Install above).
2. Pair the plugin with clawlink_begin_pairing if it is not configured yet.
3. Open https://claw-link.dev/dashboard?add=clickup and connect ClickUp.
4. Call clawlink_list_integrations to verify the connection is active.

Connection Management

List Connections

clawlink_list_integrations

Response: Returns all connected integrations. Look for clickup in the list.

Verify Connection

clawlink_list_tools --integration clickup

Response: Returns the live tool catalog for ClickUp.

Reconnect

If ClickUp tools are missing or the connection shows an error:

1. Direct the user to https://claw-link.dev/dashboard?add=clickup
2. After they confirm, call clawlink_list_integrations to verify
3. Then call clawlink_list_tools --integration clickup

Discovery Workflow

1. Call clawlink_list_integrations to confirm ClickUp is connected.
2. Call clawlink_list_tools --integration clickup to see the live catalog.
3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.
4. If the user describes a capability but the exact tool is unclear, call clawlink_search_tools with a short query and integration clickup.
5. If no ClickUp tools appear, direct the user to https://claw-link.dev/dashboard?add=clickup.

Execution Workflow

┌─────────────────────────────────────────────────────────────┐
│  READ OPERATIONS (Safe)                                     │
│  list → get → search → describe → call                      │
│                                                             │
│  Example: List tasks → Get details → Show results            │
└─────────────────────────────────────────────────────────────┘
                               │
                               ▼
┌─────────────────────────────────────────────────────────────┐
│  WRITE OPERATIONS (Require Confirmation)                    │
│  list → get → describe → preview → confirm → call           │
│                                                             │
│  Example: Describe tool → Preview changes → User approves   │
│           → Execute update                                  │
└─────────────────────────────────────────────────────────────┘

1. For unfamiliar tools, ambiguous requests, or any write action, call clawlink_describe_tool first.
2. Use the returned guidance, schema, whenToUse, askBefore, safeDefaults, examples, and followups to shape the call.
3. Prefer read, list, search, and get operations before writes when that reduces ambiguity.
4. For writes or anything marked as requiring confirmation, call clawlink_preview_tool first.
5. Execute with clawlink_call_tool. Pass confirmation only after the preview matches the user's intent.
6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.

Tool Reference

Spaces, Folders& Lists

Tasks

Comments& Collaboration

Goals& Key Results

Views& Templates

Tags, Dependencies& Custom Fields

Chat (Messages)

Code Examples

List tasks in a list

clawlink_call_tool --tool "clickup_get_tasks" \
  --params '{
    "list_id": "123456"
  }'

Create a task

clawlink_call_tool --tool "clickup_create_task" \
  --params '{
    "name": "New Feature Implementation",
    "list_id": "123456",
    "priority": 3,
    "due_date": 1705310400000
  }'

Get task details

clawlink_call_tool --tool "clickup_get_task" \
  --params '{
    "task_id": "ABC123"
  }'

Add a comment

clawlink_call_tool --tool "clickup_create_task_comment" \
  --params '{
    "task_id": "ABC123",
    "comment_text": "This is blocked by the upstream dependency"
  }'

Security & Permissions

• Access is scoped to the connected ClickUp account's workspace permissions.
• All write operations require explicit user confirmation. Before executing any create, update, or delete call, confirm the target resource and intended effect with the user.
• Destructive actions (deleting tasks, spaces, folders, lists) are marked as high-impact and must be confirmed.
• Guest access is only available on ClickUp Enterprise plans.
• Bulk operations affect multiple records; confirm before executing.

Notes

• ClickUp task IDs may be standard or custom; use custom_task_ids=true and provide team_id when using custom IDs.
• Some operations require specific ClickApps to be enabled (e.g., "Tasks in Multiple Lists").
• Time tracking data is available when the Time Tracking ClickApp is enabled.
• Nested subtasks have limitations on which list they can belong to.

Error Handling

Troubleshooting: Tools Not Visible

1. Check that the ClawLink plugin is installed:

```bash

openclaw plugins list

```

1. If the plugin is installed but tools are missing, tell the user to send /new as a standalone message to reload the catalog.
2. If a fresh chat does not help, run:

```bash

openclaw config set tools.alsoAllow '["clawlink-plugin"]' --strict-json

openclaw gateway restart

```

1. After restart, tell the user to send /new again and retry.

Troubleshooting: Invalid Tool Call

1. Ensure the integration slug is exactly clickup.
2. Use clawlink_describe_tool to verify parameter names and types before calling.
3. For write operations, always call clawlink_preview_tool first.

Resources

• ClickUp API Documentation
• ClickUp API Reference
• ClawLink: https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=clickup-tasks
• ClawLink Docs: https://docs.claw-link.dev/openclaw
• ClawLink Verification: https://claw-link.dev/verify

Powered by ClawLink — an integration hub for OpenClaw

!ClawLink Logo