ClickUp

ClickUp API integration with managed OAuth. Access tasks, lists, folders, spaces, workspaces, users, and manage webhooks. Use this skill when users want to manage work items, track projects, or integrate with ClickUp workflows. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a ClickUp connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a ClickUp action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with ClickUp examples; they add no ClickUp capability - ClickUp is not an event source, a trigger cannot read ClickUp data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).

Install this only if you intend to connect ClickUp through Maton. Review the Maton CLI install, authorize the minimum ClickUp scopes needed, confirm the exact account/connection before any write, and be especially careful with webhooks, triggers, destinations, and raw MATON_API_KEY use because those can create ongoing data flows.