ClickUp
Task, status, and comment events from ClickUp
ClickUp positions itself as the everything-app, and the trigger model on Tiny Command reflects that breadth. Six triggers cover the core task surface: Task Created, Task Updated, Task Status Updated, Task Deleted, Comment Posted, and List Created. Task Status Updated is the distinctive one, it fires only when a task moves between statuses (not every field-edit), which is usually the moment a workflow actually wants to react. Nine actions handle the writes: Create Task, Update Task, Delete Task, Create Comment, plus the read endpoints for Spaces, Folders, Lists, and Tasks (Get Task, List Tasks). The integration authorizes via ClickUp's OAuth and respects ClickUp's Spaces/Folders/Lists hierarchy, workflows only see the parts of the workspace the connected user has access to. Common patterns: a ClickUp task moving to "Ready for QA" status fires a workflow that creates a paired QA ticket in Jira, posts to Slack, and assigns the QA engineer based on the project; or a Linear bug auto-creates a ClickUp task in the right list with the original bug's context.
Workflows start when ClickUp does.
6 real-time triggers, each backed by a webhook subscription. Events arrive within seconds and you don't have to set up polling.
Fires when a new comment is posted on a task in the selected ClickUp workspace. The webhook is registered automatically when the workflow is published. Use to mirror discussion to Slack or feed AI summaries.
Fires when a new list is created in the selected ClickUp space. The webhook is registered automatically when the workflow is published. Useful for templated list provisioning or governance audit logs.
Fires when a new task is created in the selected ClickUp workspace. The webhook is registered automatically when the workflow is published. The standard inbound hook for routing, enrichment, and notification flows.
Fires when a task is deleted in the selected ClickUp workspace. The webhook is registered automatically when the workflow is published. Useful for audit logs or for tearing down related records elsewhere.
Fires when a task's status changes in the selected ClickUp workspace. The webhook is registered automatically when the workflow is published. Use status filters to react only to Done, In Review, etc.
Fires whenever any field on a ClickUp task changes (name, description, assignees, due date, custom fields). The webhook is registered automatically when the workflow is published.
Do anything ClickUp can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| Add Comment | Adds a comment to a ClickUp task, optionally as a specific user with @mentions. Used for automation activity logs, AI summary notes, or status broadcasts. |
| Create Task | Creates a new task in a ClickUp list with name, description, assignees, status, priority, due date, tags, and custom fields. The standard write action for piping forms or external tickets into ClickUp. |
| Delete Task | Deletes a task from ClickUp by ID. Moves to trash for 30 days before permanent deletion, so this is recoverable in the short term. |
| Get Task | Retrieves a ClickUp task by ID with name, description, status, assignees, due date, parent, list, and custom fields. The standard read after a trigger fires with an ID. |
| List Folders | Lists all folders in a ClickUp space along with their IDs and names. Use to populate a folder picker before creating a list. |
| List Lists | Lists all lists in a ClickUp folder. Required step before creating a task, since tasks live inside lists. |
| List Spaces | Lists all spaces in a ClickUp workspace. Use as the first step before drilling into folders and lists. |
| List Tasks | Retrieves tasks from a ClickUp list with filters for status, assignee, tags, due date, and custom fields. Used for digests, sprint reviews, or warehouse exports. |
| Update Task | Updates an existing ClickUp task: name, description, status, assignees, due date, priority, or custom fields. Only the fields you pass are changed. |
Pre-built ClickUp workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect ClickUp once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every ClickUp field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the ClickUp integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect ClickUp to Tiny Command?
What ClickUp triggers does Tiny Command support?
What ClickUp actions can I run from a workflow?
Is the ClickUp integration real-time?
Do I need to write code to use ClickUp with Tiny Command?
How much does the ClickUp integration cost?
More project management apps people connect.
Same category as ClickUp, ordered by how often teams pair them. Hover the carousel to pause.
Do more with ClickUp.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
