ClickUp automations not working usually comes down to one of six things: the workspace has hit its monthly automation usage limit, the automation is turned off, the trigger or condition does not match what actually happened, the automation is set on a different location than the task, a custom field or status it relies on changed, or the user or integration behind it lost access. Check them in that order and you will find most problems in a few minutes.
I troubleshoot broken automations for agencies regularly, both native ClickUp rules and the Make scenarios that sit around them. Here is the checklist I use.
ClickUp automations not working? Step 1: check the usage limit
ClickUp meters automation usage per month, and the allowance depends on your plan. When a workspace goes over its limit, automations are paused until the allowance resets. This is the most common reason every automation stops at once.
What to check:
- Open the Automations manager and look for the usage view, which shows how much of your monthly allowance is used.
- Check whether workspace owners or admins received a usage warning email.
- Look at which automations use the most actions. One rule that fires on every comment or every field edit can consume most of the allowance.
If you are near the cap every month, either cut noisy rules, move high-volume logic to an external tool, or move to a plan with a larger allowance. The details are in ClickUp automation limits and pricing.
Step 2: Confirm the automation is active
Automations can be switched off individually. This happens more than you would expect: someone pauses a rule while testing and forgets to turn it back on, or an automation was disabled after an error.
In the Automations manager for the space, folder or list, check that the toggle is on for the rule you expect to run.
Step 3: Check the trigger matches exactly
A trigger has to match precisely. Common mismatches:
- Status names. The rule triggers on "Client Review" but the list uses "Client review" or a status that was renamed.
- From and to statuses. A rule set to trigger when status changes from In progress to Review will not fire if the task jumps from To do to Review.
- Task created versus task moved. Moving a task into a list is not always the same event as creating it there.
- Custom field changes. A rule watching a dropdown field fires only when that field changes, not when it is set as part of a template or a bulk import, depending on how the change was made.
Read the trigger as literally as possible and then reproduce that exact event on a test task.
Step 4: Check the conditions
Conditions filter which tasks the rule acts on. If you added a condition such as "priority is Urgent" or "assignee is X", a task that does not meet it will be skipped silently. Remove the condition temporarily to see if the rule fires, then add it back.
Step 5: Check where the automation lives
Automations apply at the level where they were created. A rule on one list will not run for tasks in a sibling list. A rule on a folder applies to its lists. When agencies duplicate client folders, they sometimes expect automations to come with them, and depending on how the folder was created, they may not.
Ask: is this task actually inside the location where the automation is defined?
Step 6: Check fields and statuses still exist
If a custom field was deleted and recreated, or a status set was replaced, an automation that referenced the old one can break. The rule might still look fine in the list, but it points to something that no longer exists. Open the rule and reselect the field or status.
This is why I recommend creating shared custom fields at the space level in ClickUp for marketing agencies setups.
Step 7: Check permissions and the user behind it
Automations and integrations act with some user's permissions. If that person left the workspace, lost access to a space, or had their role changed, automations or integration actions tied to them can fail. Check who created the rule and whether they still have access to the location.
For integrations, also check that the connection in ClickUp's integration settings is still authorized.
Step 8: Look for loops and conflicts
Two automations can fight each other. For example, one rule sets status to Review when subtasks finish, and another sets it back to In progress when a comment is added. The task ends up somewhere unexpected and it looks like nothing worked.
Map every rule on a list on paper: trigger, condition, action. Look for actions that are also triggers for other rules.
Step 9: Check the external side
If the automation involves another tool, the failure might not be in ClickUp at all.
Make, Zapier or n8n scenarios
- Is the scenario or workflow switched on?
- Did it run? Check the execution history.
- Did a module error? Look at the error message, which often names a missing field or an expired connection.
- Did the external tool's usage allowance run out?
ClickUp webhooks
If you trigger external automations from ClickUp webhooks, check that the webhook still exists and is active. ClickUp can mark webhooks as failing if the receiving endpoint keeps returning errors. More detail in ClickUp webhook automation.
ClickUp automation errors I see most often in agencies
- One noisy rule eating the whole monthly allowance
- Status renamed during a cleanup, breaking several rules
- Client folders duplicated without the automations they relied on
- An integration authorized by a former employee
- A Make scenario turned off after a run of errors, with nobody alerted
The last one is the worst, because nobody notices until a client asks why something did not happen.
How to stop it happening again
- Name every rule clearly with the list and purpose.
- Keep a simple automation register in a sheet: name, location, trigger, action, owner, date added.
- Use a service account or shared admin for integrations instead of a personal login where possible.
- Add error alerts to every external scenario that post to a Slack channel someone watches.
- Review usage monthly and retire rules nobody needs.
When to rebuild instead of patch
If you are fixing the same automation every few weeks, the design is usually the problem. Signs it is time to rebuild:
- Rules depend on manual steps people forget
- Logic is spread across ClickUp, Zapier and Make with no single owner
- You regularly hit usage limits
- Nobody knows what half the automations do
For that situation I offer Automation Rescue, a 48-hour fix for broken scenarios and workflows.
How I build this
When I audit ClickUp automation setups, I list every rule and scenario, find the ones that misfire or waste usage, and rebuild the important ones with clear owners and error alerts. If you want me to look at yours first, the free 15-minute teardown is the quickest way. You can also see examples of ClickUp builds on the work page.
FAQ
Why did all my ClickUp automations stop at once?
The most common reason is that the workspace hit its monthly automation usage limit, which pauses automations until the allowance resets. Check the usage view in the Automations manager.
Why is my ClickUp automation not triggering?
Usually the trigger or condition does not exactly match the event, for example a renamed status, a different from-status, or a task outside the list where the rule lives. Reproduce the exact trigger on a test task.
How do I see ClickUp automation errors?
Check the Automations manager for the location, which shows rule activity, and check the execution history of any external tool like Make or Zapier that the rule depends on.
Do ClickUp automations stop when someone leaves the workspace?
They can, if the rule or integration depends on that person's access. Use a shared admin account for integrations and recheck rules when someone leaves.