Custom fields in ClickUp can drive an automation, not just record information. How to use one as a trigger, as a condition, and as an action, built on a live sales pipeline.
-
/
3 min watch
Chapters
Custom fields as triggers, conditions and actions in ClickUp
A custom field records something specific to your process. It can also decide what happens next, which is the part most teams leave switched off.
This walkthrough builds three automations on a live ClickUp list. A Deal Stage field that moves a task to the onboarding list the moment its value changes to Won, a Department field used as a condition so only design tasks reach the design lead, and an Account Manager people field set automatically when a task lands in the active projects list.
It closes on the failure mode worth planning for. An empty field never fires the automation, so the team has to know which fields the workflow depends on.
A custom object is the record type Zendesk does not ship: assets, contracts, subscriptions. How to define one, and the lookup field that puts it on a ticket.
A macro is a saved reply plus the ticket changes that go with it. What sits inside a macro, how to build one, and what an agent sees when they apply it.
