Pipedream ClickUp steps in n8n

ClickUp workflows on Pipedream create tasks from outside events (forms, emails, Slack messages) and push task changes to other tools. n8n has a native ClickUp node with wide coverage and a ClickUp Trigger, so most steps map to one node each.

The n8n side

ClickUp node (n8n-nodes-base.clickUp), resources: Checklist, Checklist Item, Comment, Folder, Goal, Goal Key Result, List, Space Tag, Task, Task List, Task Tag, Task Dependency, Time Entry, Time Entry Tag.

• Task: Create, Delete, Get, Get All, Get Members, Set Custom Field, Update
• Time Entry: Create, Delete, Get, Get All, Start, Stop, Update
• Comment: Create, Delete, Get All, Update

ClickUp Trigger: events for tasks (Created, Updated, Deleted, Moved, Status / Assignee / Due date / Tag / Time estimate / Time tracked updated), task comments, lists, folders, spaces, goals and key results.

What maps where

Pipedream (app clickup)	In n8n	Status
Create Task	ClickUp → Task → Create	manual
Update Task, Update Task Custom Field	Task → Update / Set Custom Field	manual
Create Checklist, Create Checklist Item	Checklist → Create, Checklist Item → Create	manual
Create Folder, Create List	Folder → Create, List → Create	manual
Create Task Comment, Create List Comment	Comment → Create (on task or list)	manual
Create Chat View Comment	HTTP Request with the ClickUp credential	manual
New Task (Instant), New Task Advanced (Instant)	ClickUp Trigger, Task Created (+ If node for filters)	manual
New Task Comment (Instant), New Task Comment Updated	ClickUp Trigger, task comment events	manual
New Folder, New List (Instant)	ClickUp Trigger, Folder / List Created	manual
Code step with this.clickup.$auth.oauth_access_token	Code node; token becomes CLICKUP_OAUTH_ACCESS_TOKEN	automatic, review

ClickUp actions are not in the converter's automatic list; the free report shows each with its list ID, name, assignees and custom field values.

Credentials

n8n's ClickUp credential has two methods:

• API access token – a personal token from ClickUp settings (Apps). Fastest for one workspace.
• OAuth2 – on n8n Cloud, "Connect my account"; self-hosted needs a ClickUp OAuth app with n8n's redirect URL.

The same credential works for the ClickUp node and the ClickUp Trigger.

Typical migration: form to task with assignee

Pipedream: HTTP trigger (form) → ClickUp Create Task (list, assignee, due date, priority) → Slack. n8n: Webhook → Code (trigger) → ClickUp → Task → Create (same list ID and fields) → HTTP Request (Slack, converted automatically).

Pitfalls

• Rate limits per token. 100 requests per minute on Free, Unlimited and Business plans; 1,000 on Business Plus; 10,000 on Enterprise. Over the limit returns 429 with X-RateLimit-Reset. A loop creating 300 subtasks on a Business plan needs a Wait node.
• IDs. ClickUp uses numeric IDs for lists and folders and string IDs for tasks; custom task IDs need the custom_task_ids and team ID parameters.
• Custom fields are set by field ID (UUID) with typed values (dropdowns take the option ID). Copy them from the Pipedream props.
• Trigger scope. The trigger is set per workspace and can be narrowed to a space, folder or list; without that it fires for the whole workspace.
• Due dates are Unix milliseconds. Convert dates from forms with an expression.

How to move your ClickUp workflows

1. Export the workflows from Pipedream.
2. Upload on /convert; the free report lists ClickUp steps and fields.
3. Download the n8n JSON: 1 workflow is free; full export: $3 per workflow, $19 minimum — coming soon.

Background in the Pipedream to n8n guide; code calling the ClickUp API can be checked in the code step checker. Related: Notion, Jira, Slack.