Start with rules triggered by task status changes. They’re predictable and they fire often enough to justify the quota.

What counts against the automation limit?

Every action an automation takes counts — sending a notification, changing a field, creating a subtask. The trigger doesn’t count. A rule with one trigger and three actions uses three actions per run.

That means a 5-rule setup where each rule does two things costs 10 actions per full cycle. On the 100-action free allowance, that’s 10 task cycles a month. Effectively unusable for an active team, and worth knowing before you assume automations will save you time.

Step 1: Build the status-change notification first

Automate > Add Automation > Task Status Updated. Condition: status becomes “In review”. Action: notify a specific person (the reviewer), not a whole channel.

Person-specific beats channel-specific. An automations notification posted to #general trains everyone to mute ClickUp.

Step 2: Auto-assign on stage entry

Condition: status becomes “Design”. Action: change assignee to the design lead and clear the previous assignee. This is the rule that stops work sitting in a stage with nobody accountable.

Use “remove assignee” deliberately — two assignees on one task is the second most common source of confusion after status ambiguity.

Step 3: Set dates automatically

Condition: priority is set to Urgent. Action: set due date to today + 1 day, set a custom field “Escalated” to yes. Two actions, high value, and it removes the debate about what urgent means.

Step 4: Create the subtask checklist

Condition: status becomes “Approved”. Action: create three subtasks — Publish, QA, Announce — assigned by role. This is the most useful automation for repeatable processes, because it removes the step where people forget what comes after approval.

Keep it to three subtasks. Eight-subtask templates generate abandoned subtasks.

Step 5: Add the stale task nudge

Condition: status is “In progress” and last updated more than 7 days ago. Action: add tag “stale” and notify assignee. ClickUp evaluates time-based automations daily on most plans, so this is a nudge, not an alert.

That’s five rules. On Business or above, this set costs almost nothing against the quota. On Unlimited, check the counter under the automation settings before adding more.

What breaks ClickUp automations most often?

Three patterns, in order:

• Two rules fighting over the same field. One sets due date, another recalculates it — you get a subtle drift nobody notices for weeks.
• Triggers that fire on every update. “Task updated” triggers include changes made by other automations, so you get loops. Use status-specific triggers instead.
• Notification spam from group mentions. A rule notifying a group of eight people produces eight notifications for one event.

Test each new rule on a scratch task and watch who gets pinged. ClickUp shows automation history per task, which is the fastest way to debug a rule that appears not to run.

Are automations worth upgrading for?

At Business pricing, if you have two or more people whose day involves moving cards, yes. The 100-action cap on Unlimited is the real dividing line — teams under 5 people can live within it by restricting automations to status changes, and teams above will exhaust it in a fortnight.

If you’re on Free Forever and considering Unlimited purely for automations, price it honestly: $7/user/month buys unlimited storage and 100 actions. $12 buys 25,000. For a 5-person team that’s $25/month extra for automations that actually run.

Quick Summary

• Free Forever and Unlimited allow 100 automation actions per month; Business allows 25,000.
• Every action counts, not every rule — a 2-action rule costs 2 per run.
• Notify named people, not channels, to avoid notification fatigue.
• Time-based automations run daily, not instantly.
• Keep to about five status-driven rules; more rules create conflicts.

Get those three right and the rest is configuration. Get them wrong and you’ll rebuild in month three.

What’s the difference between a Space, a Folder and a List?

Permissions are set at the Space level (private, shared, public). That’s why spaces should follow team boundaries, not topic boundaries. If Marketing and Engineering need different views of the same work, that’s two spaces with a linked view, not one space with 40 folders.

Step 1: Create spaces by team, not by project

ClickUp’s free plan allows unlimited members but only 5 spaces on the Free Forever tier. Even on paid plans, 6-8 spaces is the practical ceiling.

Start with Marketing, Sales, Engineering, Operations. Add Clients only if you share with external stakeholders — ClickUp guests are free and don’t consume paid seats, so a Clients space with guest access is often the cheapest way to work with agencies.

Step 2: Turn off ClickApps you won’t use

Each space has ClickApps settings — time tracking, sprints, custom IDs, priorities. Every enabled ClickApp adds UI to every task view in that space.

Turn off sprints in Marketing. Turn off time estimates in Sales. Default to fewer, and enable when someone asks. Workspaces that look intimidating are usually just ClickApps left at defaults.

Step 3: Name folders after real deliverables

“Q4” is a bad folder. “Q4 Website Rebuild” is a good one. Folders should have a start and an end; if it never ends, it’s a space or a list under a permanent folder like “Ongoing”.

For client work, one folder per client per quarter works well. For product teams, one folder per product area with lists for each sprint or phase.

Step 4: Make lists small enough to finish

A list with 200 tasks is a backlog disguised as a plan. Split by time: a two-week sprint, a campaign, a release. When a list gets past about 40 tasks, split it.

Statuses are per-list, which is the feature people miss. A design list can have “Design, Review, Approved, Built” while an engineering list has “To do, In progress, In review, Done”. Customising statuses per list is more useful than forcing one universal workflow across the workspace.

Step 5: Set the one view per team that people actually use

Each team needs a default view: Board for engineering, List for operations, Calendar or Gantt for marketing campaigns. Pin that view so the space opens to it. If everyone lands on ClickUp’s default Everything view, nobody knows where to start.

Then link, don’t duplicate. ClickUp Views and relationships let Sales see an Engineering list without copying tasks. Duplication is how you end up with two sources of truth and a weekly reconciliation meeting.

What about the free plan limits?

Free Forever gives you 100MB storage, 5 spaces, unlimited members and unlimited tasks. The storage cap is the real constraint — it’s used by attachments on tasks, not by text. If your team shares design files in ClickUp, you’ll hit 100MB in a week.

Unlimited is $7 per user per month billed annually, and it removes the storage cap and adds unlimited spaces and dashboards. For teams over three people, that’s the plan to take.

When is this hierarchy overkill?

If one person manages everything and there are fewer than 50 active tasks, the folder level is dead weight. Go workspace → space → list directly. ClickUp’s flexibility is genuinely a hindrance for solo use, and a single project board in something simpler will beat a half-configured workspace.

Quick Summary

• Hierarchy: Space (team) → Folder (project) → List (weeks of work).
• Permissions live at the Space level, so split spaces by team.
• Free Forever caps storage at 100MB and spaces at 5.
• Statuses are per-list — customise them locally, not globally.
• Pin one default view per team or nobody opens the right thing.