Pipedream ClickUp → n8n

4 Pipedream ClickUp actions and 2 event sources, and the n8n nodes they become. Converted nodes keep your configured values; expressions like {{steps.x.$return_value}} are rewritten to n8n expressions. Pipedream app slug: clickup.

Actions

Pipedream action	n8n	Fit	Notes
clickup-create-task	Click Up task → create	Check output	n8n sends the description as body.content and markdown as body.markdown_content, where PD used description/markdown_description; verify that the ClickUp API still honours these legacy field names for your account. dueDate is converted with new…
clickup-update-task	Click Up task → update	Check output	PD assignees are ADDED (assignees.add); n8n addAssignees is a comma-separated string parsed to ints. Dates are YYYY-MM-DD strings converted with new Date().getTime() in both. workspace/space/folder/list props only drive PD dropdowns. priority is not mapped…
clickup-create-task-comment	Click Up comment → create	Direct	Same endpoint POST /task/{id}/comment. assignees is not mapped: PD sent an `assignees` array, which the ClickUp comment API ignores (it reads a single `assignee`).
clickup-get-task	Click Up task → get	Direct	includeSubtasks / includeMarkdownDescription default to false, which matches PD.

Triggers (event sources)

Pipedream trigger	n8n	Fit	Notes
clickup-new-task	Click Up Trigger	Direct	PD registers a workspace-wide webhook and filters by listId in code (via GET /task); n8n passes list_id as a server-side webhook location filter (same result). PD ignores spaceId/folderId at runtime (they only scope dropdowns), so they stay unmapped; set…
clickup-updated-task	Click Up Trigger	Check output	PD dedupes on history_items[0].id. ClickUp's taskUpdated fires for most field changes; status/assignee/due date changes also have dedicated events (taskStatusUpdated, ...) that n8n can subscribe to instead.

Credentials

Create a ClickUp credential in n8n (type clickUpApi). Converted nodes reference it by name, so n8n links it on import when the names match. Pipedream connected accounts can't be exported and are deleted by April 30, 2027.

What "Fit" means

Direct: same operation, same inputs. Check output: the n8n node returns a different JSON shape, so later steps that read its result need a look. Partial: some options have no n8n equivalent. Mappings verified on 2026-10-13 against the Pipedream registry and n8n source.

Questions

Does n8n have a ClickUp node?+

Yes. 4 of the 4 Pipedream ClickUp actions listed here map to a native n8n node.

Will my Pipedream ClickUp connection move to n8n?+

No. Pipedream exports only an account ID, never the token, and deletes connected accounts by April 30, 2027. Create a ClickUp credential in n8n (type clickUpApi) and select it on the converted nodes.

Are Pipedream ClickUp triggers supported in n8n?+

2 of the 2 Pipedream ClickUp event sources listed here have an n8n trigger node. The rest are rebuilt with a Schedule Trigger that polls the API, or a Webhook node.

What happens to code steps that call the ClickUp API?+

Code steps keep working through a compatibility layer, and tokens read via this.<app>.$auth move to a secrets block in the Code node. Steps that use an npm SDK are rewritten to plain HTTP calls so they run on n8n Cloud.

Other apps

Airtable Asana Calendly Discord Dropbox Email (SMTP)GitHub Gmail Google Calendar Google Drive Google Gemini Google Sheets All apps →