ClickUp Verified First Read

Overview

Verify authentication, JSON parsing, and Workspace scope before enabling any task or webhook mutation. Keep this first probe read-only and narrowly scoped.

Prerequisites

• A personal token for individual/testing use or an OAuth token for a user-facing app
• An expected authorized Workspace ID supplied through a safe channel
• A server-side runtime that will not expose the token

Tool Discipline

Use Read, Glob, and Grep to inspect the repository, adapters, configuration names, tests, and evidence. Use WebFetch only for current official ClickUp documentation. Use Write or Edit after confirming the target file, Workspace boundary, and requested mode.

Current Contract

• Send the token in the Authorization header; OAuth examples may use the Bearer form documented by ClickUp.
• Use GET /api/v2/user to confirm caller identity and GET /api/v2/team for authorized Workspaces.
• In v2, returned teams are Workspaces.
• The probe performs zero writes and logs no names, emails, or tokens.

Authentication

Use a personal token only for accountable individual/testing work or OAuth Authorization Code for a user-facing integration. Inject the token server-side through a governed secret reference, send it in Authorization, verify authorized Workspace IDs, and never print the token, OAuth client secret, or webhook secret.

Instructions

1. Confirm the auth mode, secret reference, expected Workspace, timeout, and zero-write boundary.
2. Inspect the local client and ensure the base URL is https://api.clickup.com/api/v2.
3. Request the authorized user and validate a JSON user object without logging personal fields.
4. Request authorized teams and compare IDs to the expected Workspace allow-list.
5. Record status, latency, response schema, and redacted Workspace match.
6. Keep mutation disabled until the caller explicitly selects a bounded workflow.

Approval Boundaries

Do not create a test task, regenerate a token, or broaden OAuth Workspace authorization as part of this read-only proof.

Output

Return auth mode, user-probe result, authorized Workspace count, expected-ID match, latency, and writes performed. A successful result must explicitly report zero writes.

Error Handling

Examples

The example below is a redacted operator receipt; it contains no task text, member data, credential, or webhook secret.

auth=oauth; user=verified; workspaces=2; expected-workspace=present; writes=0; secrets-exposed=0

Resources

• Skill-specific official documentation
• Authentication
• Authentication
• Rate limits