Loading tutorials…
Loading tutorials…
ClickUp ships with 200+ Automation recipes. Most teams turn on 30, forget what 20 of them do, and watch tasks slip through the cracks. This walks the right way to roll out Automations — and the registry that keeps them maintainable.
Who this is forMarketing leads, ops leads, and ClickUp admins ready to move beyond manual Task management. If you find yourself moving Tasks between statuses, re-assigning people, or sending status update DMs more than 5 times a day, Automations will pay for themselves in week one.
What you'll need
Step 1
Automations are Trigger → Condition → Action recipes. ClickUp has 200+ pre-built recipes and supports custom multi-step Automations with conditional logic.
Open a List → top-right "Automate" button (lightning bolt icon).
Every Automation has three parts: Trigger (what starts it — status change, due date, task created, etc.), Condition (optional — only fire if X is true), Action (what happens — change status, assign, notify, post comment, create Subtask, etc.).
ClickUp ships with 200+ pre-built recipes — Status Change → Assign, Task Created → Set Priority, Due Date Arrived → Notify, etc. Browse these first before building from scratch.
Custom Automations support multi-step Actions and conditional logic (e.g., "When status changes to In Review AND priority is Urgent → notify Marketing Lead in Slack AND set due date to 2 days from now").
Automations run per-List, but Workspace-level templates exist on Business tier and above.
Step 2
Start with the universally-useful Automations every team needs. Wait to build custom ones until these are running cleanly.
1. Auto-assign by status: When status changes to "In Review" → Assign to: {Reviewer User}. Eliminates the "who is reviewing this?" question.
2. Status-driven due-date update: When status changes to "In Progress" → Set due date to 5 days from now. Forces realistic timing.
3. Overdue notification: When due date passes AND status is not Done → Post comment "@assignee This is overdue. Update status or move the date." Cuts overdue Tasks by 40-60% in 30 days.
4. New request acknowledgment: When task is created via Form → Post comment "Thanks for the request. Marketing will triage within 2 business days." Sets SLA expectations automatically.
5. Slack/Discord notification on Task complete: When status changes to "Done" → Send Slack message to #marketing-launches "✓ {Task Name} just shipped." Celebrates wins, builds momentum.
Build these one at a time. Test each before adding the next. A bad Automation that fires 200x a day is harder to debug than 5 clean ones.
Step 3
Most teams' first Automations are too broad and fire on Tasks they should not affect. Conditions narrow the trigger to the right Tasks.
Edit an existing Automation → "+ Condition." Pick a Custom Field or built-in attribute (Priority, Status, Assignee, Tag, Due Date, etc.).
Example: "When status changes to In Review → IF Priority = Urgent → Notify Marketing Lead in Slack." Without the condition, ALL "In Review" Tasks ping the Lead — annoying. With the condition, only urgent ones do.
Common conditions worth adding: by Priority (Urgent vs Normal), by Tag (Brand vs Demand Gen), by Assignee (notify the team only when it is their Task), by Channel/Type custom field.
Test conditions on a test Task before going live. Conditions are where silent failures happen — a typo in a Tag name means the Automation never fires.
Step 4
A ClickUp Doc listing every Automation, what it does, who built it, when it was last audited. Without this, Automations rot in 6 months.
Create a "Ops Handbook" Space → "+ New Doc" → name it "ClickUp Automations Registry."
For each Automation, document: Name, List(s) it lives on, Trigger, Condition(s), Action(s), Built By, Built Date, Last Audited Date, Business Reason ("why does this exist?").
Use a Table inside the Doc — 8 columns matching the fields above. Add a row per Automation.
When you add a new Automation, you also add a row. No row = the Automation does not exist (in governance terms).
Quarterly review: open the Registry, walk through every row, ask "is this still needed?" Disable Automations whose business reason no longer applies. Update the Last Audited Date.
Step 5
Sync ClickUp Automations with Slack, Microsoft Teams, Discord, or email. The right channel reduces noise; the wrong one creates more.
Settings → Integrations → connect Slack (or Teams / Discord / Gmail).
In an Automation → Action → "Post message to Slack" → choose channel and message template.
Best-practice channels: #campaign-launches for "Task done in Campaign Tracker," #marketing-firefighting for overdue Tasks, #marketing-requests for new Form submissions. Do NOT route all Automations to #marketing — it becomes noise.
Message templates: include the Task name, assignee, and a direct ClickUp link. Use ClickUp's variable system: "✓ {Task Name} just shipped — owner: {Assignee Name} — {Task URL}."
Audit Slack/Teams noise monthly. If a channel is getting 50+ messages a day from ClickUp Automations, narrow the conditions. If it is getting 0, the Automation may be broken — check the Registry.
Step 6
ClickUp Automations are quota-limited per plan tier. Free = 100 actions/mo, Unlimited = 1,000, Business = 10,000, Business Plus = 25,000, Enterprise = 250,000.
Settings → Workspace → Automations → check current month's usage.
Each Action consumes one credit (not each Automation). A multi-step Automation with 4 Actions = 4 credits per trigger.
When you hit the cap, Automations silently stop firing. Tasks are not routed, notifications go silent, work falls through.
Math: if you have 20 Automations averaging 5 fires per day each, that is 100 fires × 30 days = 3,000 actions/month. Business tier (10,000) is fine. Unlimited (1,000) is not.
Audit per-Automation fire counts in Settings → Automations → Activity Log. Disable high-frequency low-value Automations first to free quota.
If you genuinely need 25,000+ actions/month, upgrade to Business Plus. The cost ($19/user/mo) is usually cheaper than the lost productivity from missed Automation fires.
Step 7
Every quarter, open the Registry and run the audit: still needed? Still firing? Still routing correctly?
Block 60 minutes quarterly (the Friday before each quarter close works well).
Open the Automations Registry Doc.
For each Automation: (1) Open ClickUp → find the Automation → check the Last Fired timestamp. If not fired in 90+ days, ask "is this still needed?" If no, disable. (2) Test-fire by creating a dummy Task. Did it route correctly? (3) Update Last Audited Date.
For broken Automations: usually a Custom Field rename, a status rename, or a deleted user in an Action. Fix and re-test.
Document changes. If you disabled 3 Automations, write a 1-line note in the Doc: "Q2 2026 audit: disabled 3 unused Automations covering [reasons]."
Audit Slack channels too — if a channel got noisy, narrow the upstream conditions.
Common mistakes
Building 30 Automations in week one
What goes wrong: You go on an Automation bender and ship 30 recipes the first weekend. Two weeks later, the structure changes, half the Automations break silently, and the team blames ClickUp. Lost productivity: ~$3-5K/quarter from misrouted Tasks plus 6+ hrs of debugging time.
How to avoid: Roll out 5 Automations the first week. Run them for 7-10 days. Add the next 5 once the first batch is stable. Cap total Automations at 20-30 unless you have a documented Registry and quarterly audit habit.
No Automations Registry
What goes wrong: Past 15 Automations, nobody can list them all. One breaks. A campaign launch slips because Tasks are not routing. Cost: $5-12K per missed launch + team trust erosion in ClickUp itself.
How to avoid: Create the Automations Registry Doc on day one. Add a row every time you add an Automation. No row = the Automation does not exist. Audit quarterly.
Automations that fire on every Task without conditions
What goes wrong: An Automation 'Notify Marketing Lead when status changes to In Review' fires on every In Review Task across 20 Lists. The Lead gets 80 notifications/day and starts ignoring them. Real issues get missed — typical cost is 1-2 missed deadlines per quarter worth $3-10K each.
How to avoid: Add conditions: by Priority, by Tag, by Assignee. The Automation should fire on the 10% of Tasks that genuinely need attention, not the 100%.
Hitting the Automation quota cap silently
What goes wrong: You burn through the Unlimited tier 1,000 action cap by day 15 of the month. Automations stop firing. Tasks stop routing. Nobody notices for 10 days because there is no alert. ~$5-8K/month of lost workflow value.
How to avoid: Check Settings → Automations → Usage weekly. If you are over 60% by day 20, either narrow conditions or upgrade tier. Business tier (10,000 actions/mo) is the right floor for any team with 15+ Automations.
Automations changing status in ways that break reports
What goes wrong: An Automation auto-moves Tasks to 'Done' after 30 days of inactivity. Now your Dashboard shows 95% Done — but most of those are stale Tasks, not actually completed. Decisions made on inflated completion data: typical cost $2-5K/quarter in wrong priority calls.
How to avoid: Automations should reflect REAL state, not aspirational state. Auto-archive (move out of active view) is fine. Auto-marking Done is almost always wrong.
Not connecting Slack/Teams for important Automations
What goes wrong: Critical Automations (overdue alerts, urgent-priority routes) fire as in-app ClickUp notifications only. Team checks ClickUp 2x a day. Urgent stuff sits for hours. Cost: 1-2 SLA violations per month worth $2-5K each in client trust.
How to avoid: For genuinely urgent triggers (Urgent priority, SLA-bound requests, blocking dependencies), route to Slack/Teams in addition to ClickUp. Real-time visibility on the 10% that actually needs it.
Recap
Done — what's next
How to set up a ClickUp workspace and hierarchy without painting yourself into a corner
Read the next tutorial
Hand it off
Automations that work compound. Automations that rot quietly cost more than no Automations at all. A specialist who has built 200+ Automations across 50+ teams installs the right Registry, the right starter recipes, and the right audit habit — typically a $200-500 one-shot engagement, or ongoing ops support at $14-16/hr.
See specialist rates
Typical mature setup: 15-25 Automations across the Marketing Space. Less than 10 means you are doing too much manual work. More than 30 usually means duplicate logic and undocumented sprawl. Audit quarterly and aim for the 15-25 range.
For ClickUp-internal workflows (status changes, assignments, notifications): yes, Automations are faster and free. For cross-tool workflows (ClickUp ↔ HubSpot, ClickUp ↔ Mailchimp, ClickUp ↔ Stripe): Zapier or Make is usually still needed. Use Automations for internal logic and Zapier for the external bridges.
ClickUp does not loudly alert you. The Automation just stops firing — or fires incorrectly. Symptoms: Tasks stop routing, notifications go silent, statuses do not update. Check Settings → Automations → Activity Log to see recent fires. If an Automation has not fired in 30+ days but the trigger condition has happened, it is broken.
Yes — but you need to explicitly enable 'Apply to Subtasks' on the Automation, otherwise it only fires on parent Tasks. Common mistake: status-change Automation on parent Tasks does not affect Subtasks, so the Subtasks stay in old statuses. Always check the Subtask toggle when building.
Not directly. Automations are Workspace-scoped. To replicate Automations across Workspaces, export the List as a Template (which includes Automations on Business tier and above) and import the Template in the new Workspace. Multi-Workspace teams should standardize on Templates from day one.
ClickUp
ClickUp is famously deep — five levels of hierarchy and 40+ ClickApps before you even create a task. Most teams end up with 8 Spaces, 60 Lists, and no idea where anything lives. This walks the setup sequence that keeps ClickUp usable past month three.
ClickUp
ClickUp ships with 15+ view types and 30+ Dashboard cards. Most teams use 3 views and 0 Dashboards because the rest is overwhelming. This walks the views worth building, the cards worth showing, and how to keep the team on the same page.
ClickUp
ClickUp has 40+ ClickApps and 40+ Custom Field types. Most teams turn them all on within the first week and spend the next six months wondering why ClickUp 'feels heavy.' This walks the lean subset that delivers 90% of the value.
Zapier
One trigger, three or four actions. Easy to draw on a whiteboard, easy to break in production. This walks through chaining, naming, and the error scenarios that hit you on day 30, not day 1.
ClickUp
DIY ClickUp is a great idea — until you have 60+ Lists, 25 enabled ClickApps, and the team has stopped trusting the data. This is the honest framework: when the cost of self-managing exceeds the cost of hiring.