clickup-integration

Automate ClickUp workspace setup via MCP reads, API v2 writes, and Playwright CLI.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/NEXUZ-SYS/nxz-tutorial-agents --skill clickup-integration-nexuz-sys
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clickup-integration
Source: https://github.com/NEXUZ-SYS/nxz-tutorial-agents/tree/main/skills/clickup-integration
Command: npx skills add https://github.com/NEXUZ-SYS/nxz-tutorial-agents --skill clickup-integration-nexuz-sys

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @playwright/test, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Automate the end-to-end setup and configuration of ClickUp workspaces by orchestrating reads via MCP, writes via API v2, and UI automation via Playwright CLI.

Core Features & Use Cases

  • Hybrid orchestration that uses MCP for reads, API v2 for structural writes, and Playwright CLI for UI-owned operations like Custom Statuses, Custom Fields, and Automations.
  • Provides templates and scripts to create Spaces, Folders, Lists, Statuses, Fields, Views, and Automations, plus recovery patterns for API gaps.
  • Use cases include onboarding a new team workspace, templating CRM pipelines, and bulk-updating automation patterns across multiple Lists.

Quick Start

Configure a new ClickUp workspace by following the orchestration plan: fetch reads via MCP, write structure via API, then run Playwright CLI templates to finish UI-only steps.

Frequently Asked Questions about clickup-integration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate ClickUp workspace setup including custom statuses and fields?

Automate ClickUp workspace setup by coordinating MCP for reads, API v2 for structural writes, and Playwright CLI for UI-owned operations like custom statuses, fields, and automations. This hybrid orchestration ensures deterministic end-to-end configuration of your workspace.

Why does ClickUp API v2 fail to create custom statuses and automations?

ClickUp API v2 lacks direct support for certain UI-owned operations like custom statuses and automations. This limitation requires using Playwright CLI UI automation to bridge the API gaps and successfully complete the workspace configuration.

What's the best way to template CRM pipelines across multiple ClickUp workspaces?

Template CRM pipelines across ClickUp workspaces by utilizing orchestration scripts and templates that bulk-write Spaces, Folders, Lists, and Views via API v2, applying standardized processes and recovery patterns for consistent team onboarding.

Can I use Playwright to bulk-update ClickUp lists when the API is limited?

Yes, you can use Playwright CLI to bulk-update ClickUp lists when API capabilities are limited. The Skill orchestrates Playwright to handle UI-only operations and automation patterns that API v2 cannot directly access, recovering from API gaps.

Do I need a ClickUp API token to automate workspace configuration?

Yes, automating ClickUp workspace configuration requires a ClickUp API token and workspace ID. These credentials allow the orchestration scripts to authenticate MCP reads, execute API v2 writes, and run Playwright CLI UI templates.

How does MCP coordinate with API v2 and Playwright for ClickUp automation?

MCP handles data reads, API v2 executes structural writes for Spaces and Lists, and Playwright CLI performs UI automation for custom fields and statuses. This coordinated approach delivers deterministic outcomes for end-to-end ClickUp workspace automation.