← Integration Hub

ClickUp

Action requiredNot connectedMOCK

Tasks and deadlines behind the Tasks area.

How it connects
Paste a key or token
Health
healthy
Integration status
connected
Credential
Not configured
Last sync
never
Connected
not yet
Provider documentation

1 of 3 steps done

Setup

  1. Copy your personal API token

    You are hereNot done yet
    YouProvider console (one time)

    ClickUp → Settings → Apps → API Token. This is a personal token: it sees what your ClickUp account sees, and nothing more.

    Open the provider's console

  2. Encrypted credential storage initialized

    Done
    Administrator (once)In the Hub

    Credentials are sealed with AES-256-GCM before they reach the database, and PAXX refuses to store them at all without a key. Initialize it with one click in the Integration Hub, or set the key in the server environment if you would rather manage it yourself.

  3. Paste it into PAXX

    Not done yet
    YouIn the Hub

    Press Connect. The token is checked against ClickUp before it is stored.

Paste a key or token

Connect

Copy your ClickUp personal API token and paste it into the Connect form.

Live check

Connection test

GET https://api.clickup.com/api/v2/user — confirms the token is live and reports the ClickUp user.

1 declared

Permissions

What PAXX asks the provider for. The provider's own consent screen is the authoritative grant — this list is what will be requested, and after connecting, what was actually returned.

  • readRead tasksnot requested yetWorkspaces, tasks and due dates.

Capabilities

What you get

  • Tasks and due dates

    readNot available

    Open tasks grouped into today, this week, overdue and needs-attention.

    Available once this provider is connected.

    /tasksDashboard → Attention

  • Workspaces

    readNot available

    Which workspace and list a task belongs to.

    Available once this provider is connected.

    /tasks

Requirements

Diagnostics

Administrator requirements

One-time work for whoever administers this PAXX instance.

  • Encrypted credential storage initialized

    Satisfied
    Administrator (once)In the Hub

    Credentials are sealed with AES-256-GCM before they reach the database, and PAXX refuses to store them at all without a key. Initialize it with one click in the Integration Hub, or set the key in the server environment if you would rather manage it yourself.

Your requirements

Per-person steps — the authorization is yours, not the deployment's.

  • Copy your personal API token

    Not satisfied
    YouProvider console (one time)

    ClickUp → Settings → Apps → API Token. This is a personal token: it sees what your ClickUp account sees, and nothing more.

    Open

  • Paste it into PAXX

    Not satisfied
    YouIn the Hub

    Press Connect. The token is checked against ClickUp before it is stored.