How to set up ClickUp automations

If you’re already using ClickUp to manage your work, you’re sitting on top of an automation engine that most people never touch. Every time you manually change a task status, assign a teammate, post the same update, or move a card from one list to another, you’re doing work that ClickUp could be doing for you — silently, instantly, and for free on most plans. This guide walks you through setting up ClickUp Automations from your very first one to a handful of recipes that save real hours every week.

The good news: you don’t need any technical skill to do this. Learning how to set up ClickUp Automations comes down to one plain-English pattern — “when this happens, do that” — and the whole thing is built with dropdown menus.

What ClickUp Automations Actually Are

A ClickUp Automation is a rule that runs by itself inside your workspace. You define a starting event and the action you want to follow, and ClickUp watches your tasks around the clock so you don’t have to. Think of it like a tireless assistant who only knows one job but does it perfectly every single time: “whenever a task is marked Done, move it to the Archive list.” You set it once, and it runs forever.

It helps to picture automations as the office light that turns itself off when everyone leaves. Nobody flips a switch — a sensor notices the room is empty and acts on a rule somebody set up months ago. ClickUp works the same way, except the “sensor” is an event on a task and the “switch” is whatever change you want made. Once you internalize that mental model, every automation you’ll ever build is just a matter of choosing the right sensor and the right switch.

The key thing to understand up front is that ClickUp Automations work inside ClickUp. They move tasks, change statuses, assign people, post comments, and apply templates within your workspace. This is different from a tool like Make.com or Zapier, which connects ClickUp to outside apps like Gmail, Stripe, or your CRM. We’ll come back to that distinction at the end, because it’s the single most important thing to get right when you’re deciding how far ClickUp alone can take you.

The Anatomy: Triggers, Conditions, Actions

Every automation in ClickUp is built from the same three parts. Learn these three words and you’ve learned the entire system.

Triggers — the “when this happens”

A trigger is the event that starts the automation. It’s the sensor noticing something changed. Common triggers include a status change, a new task being created, a due date arriving, an assignee being added, or a custom field changing value. If you’ve ever thought “every time X happens, I end up having to do Y,” then X is your trigger.

Actions — the “then do this”

An action is the change ClickUp makes once the trigger fires. This is the switch being flipped. Actions include changing a status, assigning a person, moving the task to another list, applying a task template, posting a comment, sending an email, or changing a priority. You can stack several actions in a row, and they run top to bottom in the order you arrange them.

Conditions — the optional “but only if”

Conditions are filters that make an automation more precise. They let you say “when a task is marked Done but only if it’s assigned to the design team, then archive it.” Conditions are powerful, but here’s the catch most tutorials skip: conditions are only available on the Business plan and above. On the Free and Unlimited plans you get triggers and actions, which is plenty for the vast majority of small-business workflows.

Build Your First Automation Step by Step

Let’s build something genuinely useful: an automation that assigns a task to you automatically whenever its status changes to “In Progress.” No more forgetting to claim work — the moment a task goes active, it lands on your plate. Here’s the exact path.

Congratulations — you’ve built a working automation. The exact same five-step flow builds every other automation in ClickUp. From here it’s only a matter of swapping which trigger and which action you pick.

Five Automation Recipes Worth Stealing

These are the workflows small teams reach for most often. Each one follows the same when/then pattern you just learned. Build them in minutes.

1. Auto-archive completed work

Keeps your active boards clean without anyone manually shuffling finished tasks out of the way.

2. Hand off between teams

The work moves to the next person the instant it’s ready, with no “hey, this is ready for you” message needed.

3. Set deadlines automatically

Every new task gets a default deadline so nothing sits without a date and quietly rots.

4. Escalate overdue tasks

Stale tasks raise their own hand instead of getting buried. (The “status is not Done” part is a condition — Business plan and above.)

5. Onboard with a template

Every new client task instantly spawns your full checklist of onboarding subtasks. This one alone justifies learning automations if you run client work.

Plan Limits: What Each Tier Gives You

This is where most guides hand-wave, so here are the real 2026 numbers. The thing that ultimately pushes teams onto a paid plan isn’t features — it’s the monthly automation cap and the 100MB storage ceiling on Free.

For most small businesses, the Unlimited plan at $7/user/month is the sweet spot. The jump from 100 to 1,000 automation actions a month is the difference between “I tested it once” and “it quietly runs my operation.” The Business plan only earns its keep once you genuinely need conditions and advanced reporting.

Common Mistakes and How to Avoid Them

A few traps catch almost everyone building their first handful of automations. Knowing them in advance saves you the head-scratching.

Building automations in the wrong location. An automation created on one List doesn’t apply to others. If your rule “isn’t firing,” nine times out of ten it’s because you built it on the wrong List, Folder, or Space. Build it where the tasks actually live.

Burning through your action quota. Every single action counts against your monthly cap, and stacked actions multiply fast. An automation with three actions that fires 40 times a month is 120 actions — already over the Free plan’s 100 limit. Watch your busiest automations.

Creating accidental loops. If automation A changes a status that triggers automation B, which changes something that re-triggers A, you’ve built a loop that devours your quota in minutes. When two automations touch the same status, check they can’t chain into each other.

When ClickUp Automation Isn’t Enough

ClickUp Automations are excellent at one thing: moving work around inside ClickUp. The moment your workflow needs to reach outside ClickUp — pull a new lead from a web form into a task, charge a customer in Stripe when a task closes, send a Slack message to a channel ClickUp doesn’t natively connect to, or sync data between three different apps — you’ve hit the edge of what native automations can do.

That’s not a flaw; it’s a boundary. ClickUp is a project management tool with automation built in, not a dedicated integration platform. For cross-app workflows you want a tool whose entire job is connecting services: Make.com. Make sits between your apps and passes data among them, and it integrates with ClickUp directly. A typical setup is ClickUp handling everything internal — statuses, assignments, templates — while Make handles every handoff to the outside world.

So the honest rule of thumb is this. Use ClickUp Automations for anything that starts and ends inside ClickUp; they’re free, fast, and you’ve now got the skills to build them. Reach for Make.com the moment a workflow needs to touch another app. Most small businesses end up running both, and the combination is far more powerful than either alone.