Short answer: Drop the "ClickUp → Create Task" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
List ID list_id | string | Required | The ClickUp list ID to create the task in |
Task Name name | string | Required | Task Name. Example: Design new landing page |
Description description | string | Optional | Task description (supports Markdown) |
Priority priority | options | Optional | Priority. Options: Urgent, High, Normal, Low |
Status status | string | Optional | Status name (must match a status in the list) |
Due Date due_date | string | Optional | Due date as Unix timestamp in milliseconds |
Assignee User IDs assignees | string | Optional | Comma-separated ClickUp user IDs |
Tags tags | string | Optional | Comma-separated tag names |
{"list_id": "e.g. 123456789","name": "e.g. Design new landing page","description": "{{trigger.description}}","priority": "{{trigger.priority}}","status": "e.g. to do"}
{"id": "abc123","url": "https://app.clickup.com/t/abc123","name": "Design new landing page","status": {"status": "to do"}}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.