Which ClickUp Automations Should a Small Team Set Up First?

Coding Liquids tutorial cover featuring Sagnik Bhattacharya for Which ClickUp Automations Should a Small Team Set Up First?
Coding Liquids tutorial cover featuring Sagnik Bhattacharya for Which ClickUp Automations Should a Small Team Set Up First?

A small team should build five ClickUp automations first: assign and date new tasks, reassign on a status handoff, remind before the due date, chase overdue tasks, and update a parent when subtasks finish. They cost nothing extra, but Free allows 100 actions a month, Core 1,000 and Business 10,000.

The Complete Excel Course with AI Integration

From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.

By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner

Buy now

The limit that bites is not the number of rules, it is monthly actions shared by the whole Workspace. One busy intake List can use up the Free allowance in a week, so the order you build in matters as much as the choice of rules. Build each rule in a scratch List first, see what one run costs on the Usage tab, and only then switch it on where every new task will fire it.

Do ClickUp automations cost extra?

No, automations are included on every ClickUp plan, but each plan caps how many rules can be active and how many actions the Workspace can use in a month; past the cap, automations pause.

This table comes from ClickUp's help-centre article on automation availability and its pricing page, read on 22 November 2026.

PlanActive automationsActions per month (Workspace-wide)ConditionsUsage history kept
Free Forever5100No1 day
Core500 on the help centre's table; the pricing page says unlimited rules1,000No1 day
BusinessUnlimited10,000Yes1 day
Business PlusUnlimited25,000 on existing plans, 100,000 on new plansYes30 days
EnterpriseUnlimited250,000 on existing plans, 1,000,000 on new plansYes6 months

Five things are worth knowing before you build:

  • The limit is per Workspace, not per person. Ten people share the same 1,000 actions on Core.
  • When the limit is exceeded, the Workspace's automations are paused for that month. Limits reset on the first of the month, Pacific Time, and owners and admins get emails at 90 percent and 100 percent.
  • Conditions (extra filters such as "only if the priority is Urgent") are on Business and above. On Free and Core you filter by choosing the trigger and the List carefully.
  • Task webhooks and automation integrations are Business and above.
  • Business Plus and Enterprise can buy more actions. On the lower plans you upgrade.

How are ClickUp automation actions counted?

ClickUp counts a dispatched action as one monthly action whether it succeeds or fails, and an action skipped because a condition is not met counts as zero. Its usage help page also describes each triggered automation as one use, so the safest way to learn your real count is to test.

Open any Space, Folder or List, click the robot icon in the upper right, choose Manage Automations, then open the Usage tab. It shows total actions used against your monthly allowance and total active rules against your plan's allowance. The tab updates after every ten automation uses, so a single test will not move it. Run a rule ten times on dummy tasks, note the change, and you will know whether a two-action rule costs one or two.

Until you have that number, budget on the worse case: every action counts. The example below does that.

Which five automations should a small team build first?

A small team's first five ClickUp automations, in order, are: assign and date on creation, reassign on handoff, remind before the due date, chase when overdue, and move the parent when subtasks finish. Together they remove most manual chasing in a List.

Create each one the same way. From the Space, Folder or List, click the robot icon, click Create Automation, pick a suggested automation, a template or a custom build, set the Trigger, add any Conditions, set the Actions, optionally name it, and click Create. If the AI ClickApp is active and you leave the name empty, ClickUp generates a name for you. An admin or owner must switch on the Automations ClickApp first.

Rule 1: assign an owner and a due date when a task is created

Use this on an intake List such as Requests, where tasks arrive from a form, an email or a teammate and nobody has yet picked them up.

  1. Trigger: Task or subtask created. In the Created by dropdown, leave Forms, Email and Users ticked; untick Automations so rules cannot trigger each other.
  2. Action 1: Change assignee, and add the person who triages. Under advanced options you can also choose to reassign, replacing whoever was on it.
  3. Action 2: Change due date, using Days after trigger date and the number your team can honour, say 2.

Why it is first: unowned, undated tasks are where requests disappear. One rule closes both gaps. If you have set up AI Assign for the List, the Change assignee step can be replaced by the AI Assign action, which picks the person from prompts you wrote; it is available only on the Task created or Task updated triggers and only after you set up AI Assign for that List.

Rule 2: hand the task on when the status changes

Use this wherever work moves from one person to the next, such as Drafting to Ready for review.

  1. Trigger: Status changes, with To set to Ready for review.
  2. Action 1: Change assignee, choosing the reviewer and using the reassign option so the author is removed.
  3. Action 2: Add a comment that mentions the reviewer, for example "@reviewer ready for you. Needs a decision by tomorrow."

An automation can only set a status that exists in the List where you build it, so create the statuses first. Without the comment the reviewer only gets a notification of reassignment, which people skim past.

Rule 3: remind the assignee before the due date

  1. Trigger: Date is Before/After. ClickUp sets it to 1 day before the start date by default, so change the date dropdown to the due date, and the number to 2 if you want two days' notice.
  2. Action: Add a comment mentioning the assignee, with the task name and due date as variables.

Date-triggered automations fire at 4 am local time unless the date has a time, using the time zone of the person who created the rule. If your team works across time zones, create it as the person whose morning you want. You can use the alternative Due date arrives trigger to fire on the day itself. On Business and above, add a Condition to skip tasks that are already in a done status; on Free and Core, check the Activity tab after a few days to see whether finished tasks are being reminded, and tidy your statuses if they are.

Rule 4: chase when the task is overdue

  1. Trigger: Date is Before/After, set to 1 day after the due date.
  2. Action 1: Change Priority to Urgent.
  3. Action 2: Send a direct message to the assignee, or add a comment mentioning the manager, whichever your team will actually read.

This is the rule that replaces the Monday "who is late?" hunt. Keep the tone neutral in the message: "This task passed its due date yesterday. Reply with a new date or what is blocking it." A bare "OVERDUE" teaches people to mute it.

Rule 5: close the loop when all subtasks are done

  1. Trigger: Subtasks resolved. ClickUp fires it when all subtasks directly beneath the parent are resolved.
  2. Action: Change status to Ready for review on the parent task, and optionally add a comment.

A project with eight subtasks otherwise sits in "In progress" for days after the work is finished because nobody remembers to move the parent. The same pattern works with the Checklists resolved trigger for tasks that use checklists instead of subtasks.

How many actions will five rules use? A courier firm's budget

For a courier firm with eight people on Core, handling about 140 delivery-request tasks a month, five rules cost roughly 785 actions in the worst case, which fits inside Core's 1,000 but overruns Free's 100 within the first week. All numbers here are illustrative.

RuleFires onActions per runWorst-case monthly actions
1. Assign and date140 new tasks2280
2. Hand off to review140 tasks2280
3. Due-date reminder140 tasks1140
4. Overdue chaseAbout 25 late tasks250
5. Close parentAbout 35 parent tasks135
Total785

Rule 5 is sized to the 35 parent tasks that actually have subtasks, not all 140 tasks. Leave a margin for seasonal peaks and for rules you add later; in this example, 785 of 1,000 leaves 215 spare, which is a comfortable margin until a rule starts firing on a larger List. If the firm ran the same rules on Free, rule 1 alone would use all 100 actions after 50 new tasks (two actions each), and every automation in the Workspace would pause for the rest of the month.

If the Usage tab shows that a two-action rule counts as one, the total halves. Either way the Free plan is a poor home for rules that fire on every task; use it to prove one or two rules on a small List, then move up.

If you want help choosing which of your own Lists deserve these rules, I offer one-to-one AI consultations for small businesses.

How do you test an automation before the team sees it?

Test a new ClickUp automation in a scratch List with dummy tasks, then check the Activity tab for each run before you copy the rule to the live List. A test List catches wrong statuses and runaway loops before they use real actions.

  1. Make a test List in the same Space with the same statuses as the live one, and add yourself as the only person.
  2. Build the rule there and create or move a task to fire it.
  3. Open the Activity tab. Click the robot icon, then Manage Automations, and use the Activity tab, or open the Automations and Agents activity view. Filter by Location, Date run and Status. A run shows as Pending, Failed, Skipped or Success.
  4. Expand the run to see which actions ran. Skipped means the criteria were not met, which is expected if a Condition filtered the task out.
  5. Check the Usage tab after ten runs to learn the cost of one run.
  6. Rebuild on the live List once the behaviour is right.

Watch for two traps. Applying a template can create subtasks, and if the trigger is Task created the new subtasks can trigger the rule again; ClickUp warns that this can start a loop and says to disable the trigger to end it. To head it off, untick the Automations and Templates & Duplicated Tasks sources in the Created by dropdown, and prove the rule in the scratch List first. Second, the Send Email action can only be combined with other Send Email actions in one rule, so a rule that emails and changes status needs two rules on the same trigger.

What can AI add to ClickUp automations?

AI can pick the assignee or priority and judge a plain-language condition in ClickUp automations, but each uses AI credits, so keep the five core rules on plain triggers. Save AI for judgement calls; with the AI ClickApp on, ClickUp will also name a rule for you if you leave the name empty.

  • AI Assign and AI Prioritize: set up on a List with a prompt for each person or priority level, then call them as actions from a Task created or Task updated trigger. The setup has a Try in view option that tests the first three tasks before anything is applied. ClickUp refreshes automatically updated values about every 20 minutes unless you switch auto update off.
  • Describe any condition: on Business and above you can write a rule in plain language, for example "this request mentions a damaged parcel", and AI evaluates whether the automation continues. You can have only one AI condition per automation.
  • AI Automations: the AI-run kind, previously called Autopilot Agents. ClickUp's credits page lists them as using credits on every paid plan, with unlimited use only on Max and the Everything AI add-on.

Core includes 1,000 AI credits per seat each month, pooled across the Workspace, and credit features pause when the pool runs out. What Brain and the AI add-ons cost for ten people goes through the credit maths, and AI against rule-based automation helps you decide which jobs need which.

An example of where AI beats a plain rule: a courier firm's intake List gets requests about damaged parcels, missed collections and invoice queries. A plain Created trigger cannot tell them apart, whereas AI Assign with three prompts ("damaged or missing goods go to the claims handler", and so on) routes them. A plain rule is still better for "set the due date to two days", because it costs no credits and never guesses.

What should the comments and messages say?

Automated messages get ignored when they are vague, so write each one to answer three questions: what is it, what is wanted, and by when. Variables such as the task name and due date can be added to comments and messages, so the rule fills in the specifics. Here are before and after versions for the three messaging rules, with illustrative wording:

RuleBeforeAfter
2. Handoff"Reassigned to you.""@reviewer [task name] is ready for review. Approve it, or comment what needs changing. Please decide by the due date."
3. Reminder"Due soon.""@assignee [task name] is due tomorrow. If it will slip, change the due date now and say why."
4. Overdue"OVERDUE!!""@assignee [task name] passed its due date yesterday. Reply with a new date or the blocker, and @manager if you need a decision."

The "after" versions tell the reader what to do next, which is the difference between a comment people act on and a notification they swipe away. Keep them short enough to read on a phone lock screen.

How would a translation agency use the same five rules?

A six-person translation agency can reuse all five rules by renaming the statuses to its own stages: New job, Translating, Proofreading, Client review and Delivered. The structure is identical, and only the triggers and names change.

  1. Assign and date: when a job is created from the client request form, assign the project manager and set the due date three working days out. Illustrative numbers, but the shape matters: the manager triages, then reassigns to a linguist.
  2. Handoff: when the status changes to Proofreading, reassign to the proofreader and comment with the language pair from a Custom Field.
  3. Reminder: one day before the due date, comment on the linguist's task.
  4. Overdue: one day after the due date, set the priority to Urgent and message the project manager, who may need to warn the client.
  5. Close the parent: a book translation has one subtask per chapter; when every chapter subtask is resolved, move the parent to Proofreading.

At roughly 90 jobs a month and two actions in each of the first two rules, plus one for each of the others, the worst case is 90 x (2 + 2 + 1) = 450, plus about 20 overdue jobs at two actions each and 15 book parents at one, giving 505 actions. That fits Core's 1,000 with room to spare, and it would exceed Free's 100 in the first week.

What prompt makes AI Assign route requests correctly?

AI Assign works from one prompt per person, so write each prompt as the plain-language description of the work that person owns. In the List view, click the Assignee column header, choose Assign with AI, add the people, and write a prompt for each one. Illustrative prompts for the courier firm:

The claims handler: requests about damaged, wrong or missing goods, or customer complaints about a delivered parcel.
The dispatcher: requests to change a collection time or address, or to reschedule a delivery.
The accounts clerk: invoice queries, price questions and account set-up.

Use Try in view first. It tests AI Assign on the first three tasks in the view, so you can see the choices before anything is applied. An illustrative result: "Parcel arrived crushed, customer wants a refund" goes to the claims handler; "Can you collect from the other warehouse on Friday?" goes to the dispatcher; "Why was I charged twice?" goes to the accounts clerk. What you fix in it: requests that fit two prompts, such as a damaged parcel with an invoice dispute. Add a line to one prompt saying which person takes the mixed cases, or leave the field blank and let the dispatcher decide.

How do you check the rules worked after two weeks?

Check ClickUp automations after two weeks by comparing three numbers from before and after the switch-on: unowned tasks at day's end, overdue tasks nobody commented on, and time spent chasing. For the courier firm, that last one is the dispatcher's chasing time. A small team can count the first two in a saved List view in a few minutes.

  1. Week 0: save a view filtered to tasks with no assignee and another for overdue tasks; note both counts on the same weekday.
  2. Week 1: switch on rules 1 and 2 only. Check the Usage tab on day 3 and day 7.
  3. Week 2: add rules 3 to 5. Read the Activity tab for Failed and Skipped runs and fix each cause.
  4. End of week 2: compare. Unowned tasks should be close to zero; overdue tasks with no comment should be far fewer; if the allowance is more than 70 percent used, plan the upgrade now rather than discovering a pause mid-month.

Ask the team one question as well: which message did you act on? Rewrite the ones nobody mentions.

Mistakes that make automations noisy or stop them silently

Most failures come from five avoidable mistakes, and each shows up in the Activity tab.

  • A status was renamed. The rule that sets "Ready for review" fails if that status no longer exists in the List. After any status clean-up, open Activity and filter by Failed.
  • A person left. A rule that assigns a former colleague will fail. ClickUp emails the creator, or the Workspace owner if the creator has gone. When someone leaves, open Manage Automations and change every rule that names them before their account is removed.
  • Rules overlap. Several automations with the same trigger fire at the same time, so two rules that both change the assignee race each other. Combine them into one rule with ordered actions; you can drag actions to reorder them.
  • The rule fires on everything. A reminder on a big shared List reminds people about tasks they closed last month. Limit each rule to the List where it belongs, and use Conditions on Business and above.
  • Nobody owns it. Six months on, nobody remembers why a rule exists. Name each rule with its purpose and add a description. After more than five failures with the same error in one week ClickUp switches a rule off, which is helpful but silent for people who do not read email.

A one-page register for your rules

Keep a simple register so you can see your allowance, owners and purpose at a glance. A spreadsheet works: one row per rule, with its List, trigger, actions per run, expected runs a month, worst-case monthly actions, and the person who owns it. Filled in for two rules from the example above:

RuleListTriggerActions per runRuns a monthTotalOwner
Assign and dateRequestsTask created2140280Dispatcher
Overdue chaseDeliveries1 day after due22550Operations lead

The total at the bottom, set against the Usage tab's figure on the first of each month, tells you whether you are drifting towards the limit. If building registers like this one is the slow part, try The Complete Excel Course with AI Integration on Coding Liquids.

What to build after the first five

Once the five rules run cleanly for a month, add them in this order: a rule that applies a task template when a task is created in a particular List, a rule that sets a Custom Field when a status changes (for example, a checkbox that marks "client notified"), and a weekly Every trigger that sets a field on all tasks in a List. Two reasons for the order. The template rule saves the most typing, and the Every trigger is the easiest way to run out of actions, because it acts on every task in the List each time it fires. ClickUp also notes that the Every trigger does not fire on closed or completed tasks.

When the work is a form-driven flow, a ClickUp intake form with Brain triage pairs well with rule 1: the Created by filter on Forms means the rule only fires for form submissions. For a sales pipeline, the same building blocks appear in setting up ClickUp as a CRM for a small agency, where a status change moves a lead to the next List.

ClickUp automation questions small teams ask

Are ClickUp automations free?

Yes, up to a limit. Every plan can use them, but the Free plan allows 5 active automations and 100 actions a month, and Core and Business raise the monthly actions to 1,000 and 10,000. Past the limit, ClickUp pauses the Workspace's automations until the next month unless you upgrade or, on higher plans, buy more actions.

What happens when I run out of automation actions?

The Workspace's automations pause for the rest of the month. Limits reset on the first of the month, Pacific Time, and owners and admins get emails at 90 percent and 100 percent usage. Check the Usage tab in Manage Automations, which updates after every ten automation uses, before a busy month starts.

Can a ClickUp automation remind someone before a due date?

Yes. The Date is Before/After trigger can fire a set number of days before or after a due date, for example to add a comment that mentions the assignee; switch its date dropdown from the default start date to the due date. The Due date arrives trigger fires on the due date itself, at 4 am in the creator's time zone unless a specific time is set.

Do I need AI credits to build automations?

No. Standard triggers and actions use monthly automation actions, not AI credits. AI features inside them do use credits: AI Automations, AI conditions written in plain language, and the AI Assign and AI Prioritize setups. Those draw on the pooled monthly credits, which are 1,000 per seat on Core.

Why did my automation stop working by itself?

ClickUp deactivates an automation that fails more than five times in one week with the same error, and emails the person who created it. Open the Activity tab, filter by Failed, and read the error. Common causes are a status that no longer exists in the List and a person who has left the Workspace.

Further reads

Sources: ClickUp pricing page and help-centre articles on Automations availability and limits, creating automations, triggers, actions, conditions, usage and activity (read on 22 November 2026).

Ready to put AI on the jobs that eat your week?

No data team or big budget needed. In a 1:1 consultation I show small and medium-sized businesses and self-employed people which AI tools they can use, one workflow at a time.

Book a 1:1 call with me