ClickUp Trigger

Overview

Start a workflow when a task changes in a ClickUp list. Point the trigger at a List ID and choose what fires it:

• Task created — fires once per new task (watches date_created).
• Task created or updated — fires on any change (watches date_updated), including tasks being closed or completed.

How polling works

• Falcon Builder checks the list every few minutes and delivers tasks changed since the last check, oldest first, so nothing is missed between runs.
• Use Statuses to only fire for tasks in certain statuses (e.g. to do, in progress), and Include Subtasks to also watch subtasks.
• Max per Poll caps how many tasks are emitted per check (1–100).

Trigger output ($json)

• {{$json.id}} — the task ID
• {{$json.event}} — task_created or task_updated
• {{$json.name}} / {{$json.status}} / {{$json.priority}} — core task fields
• {{$json.url}} — direct link to the task
• {{$json.assignees}} — assignee list (id, username, email)
• {{$json.dueDate}} / {{$json.dateCreated}} / {{$json.dateUpdated}} — timestamps (epoch ms)
• {{$json.task}} — the full ClickUp task object for anything else

Notes

• In created or updated mode, editing a task re-fires the trigger. Branch on {{$json.status}} (or another field) if you only want to act on certain changes.
• Find the List ID with a ClickUp node (List → Get Many) or from the list's URL in the ClickUp app.
• Production triggers follow the published workflow — publish after adding or reconfiguring the trigger.

Required Credentials