Start a workflow from ClickUp task events

ClickUp triggers start a run from what happens in your ClickUp Workspace. All four are instant — ClickUp tells Bizomate the moment it happens:

• ClickUp · New task — When a task is created.
• ClickUp · Task status changed — When a task moves to another status.
• ClickUp · Task updated — When a task changes.
• ClickUp · New comment — When someone comments on a task.

Publishing adds a webhook to the ClickUp Workspace for you, and nothing needs pasting — see How instant triggers work.

Who can do this

Workspace Admins and Editors, on every plan. Viewers see the trigger and its status but cannot change it.

Before you start

A ClickUp connection — see Connect ClickUp.

Steps

1. Open the workflow in the designer and open the trigger picker — Browse all triggers on an empty workflow, or select the trigger and Change how it starts.

2. Under ClickUp, select the event. It reads ClickUp · instant. Or type ClickUp in Search triggers.

3. In Connection, choose your ClickUp connection.

4. In Workspace, choose the ClickUp Workspace — Consulace.

5. Optional: narrow it to one part —

   • Space — Empty: the whole workspace. For example Delivery.
   • Folder — Empty or No folder: the whole space, unless a list is chosen.
   • List — Empty: the whole folder or space. For example Client onboarding.

   Only the narrowest one you choose counts: a list, else a folder, else a space.

6. The panel reads Publishing sets this up in ClickUp, and every publish sets it up again. It stays while the workflow is published — switched off, what arrives is ignored — and is taken away when the workflow is deleted or starts another way.

7. Add the steps, then Publish. Bizomate adds a webhook. The panel reads Waiting for the first event — Make one happen; it appears here within seconds.

Test with a real event:

1. Make the event happen in ClickUp — add a task, or move one to review.
2. Within seconds the panel reads Listening — instant — Last event 10:45 · Task status changed · Onboard Northwind Logistics · to do → review.
3. On Output, select Use the last event, then Test run.

What the trigger gives

The task, read back from ClickUp as the ClickUp steps read it — id, name, description, url, status, priority, assignees, tags, dueDate, createdAt, listId, listName, parentId, and each custom field by its name — and user, who did it. Also:

• Task status changed: previousStatus — to do. status is the new one.
• Task updated: changedFields — ClickUp's names for what changed.
• New comment: commentId and text — Contract signed.

What happens next

• Each event starts one run of the live version, in Production, named after it — New task · Onboard Northwind Logistics, Task status changed · Onboard Northwind Logistics · to do → review, Task updated · …, New comment · ….
• Each workflow has its own webhook in ClickUp. Every publish sets it up again; changing to another trigger, workspace or place and publishing, or deleting the workflow, removes it.

How Bizomate knows an event is ClickUp's

ClickUp gives each webhook a secret when Bizomate makes it, which Bizomate keeps encrypted. ClickUp signs every event with it (the X-Signature header), and Bizomate works the signature out again. An event whose signature does not match is answered 401 — The signature does not match. — and starts nothing.

Good to know

• A status change is also an update. Workflows on Task status changed and Task updated both run.
• Task updated hears every change — name, description, assignees, dates, custom fields. Add an If step on changedFields to act on one kind of change.
• A task deleted before Bizomate reads it starts no run.

If something goes wrong

Related

• How instant triggers work
• Connect ClickUp
• Create, update or find ClickUp tasks
• Change how a workflow starts