What we do
Tools
Industries
Department
How we workLet's talk →
Home/ClickUp/ClickUp Automations Across Spaces, Plus Limits
ClickUp

ClickUp Automations: Build One, Stay Under the Limit, Change It Everywhere

A task lands in Ready for review and you still assign the reviewer, set the due date and post the checklist yourself. A ClickUp automation does those three things for you: a trigger, optional conditions, then one or more actions, attached to a Space, Folder or List. Here's where to build one, what fits which job, what the monthly allowance counts, and the part that hurts once the same automation runs in thirty places.

ClickUp automations, the short version

Build one: open the Space, Folder or List, click Automate (the lightning bolt) at the top right, then Create Automation. You can also start from a template or a suggested automation.

Automate Create Automation

Find the ones you've got: they're listed in the Manage tab of the same window. Each level of the hierarchy keeps its own, so a List's automations don't show up at the Space.

Know the limit: Free Forever allows 5 active automations and 100 actions a month, without task webhooks or integration actions. Paid plans get a bigger monthly allowance. Go over it and the Workspace's automations pause for the rest of the month.

Which ClickUp trigger and action for the job

You want Trigger, then action Good to know
The right person picks up a task the moment it reaches review Status changes to Review, then change assignees and post a comment with the checklist Add a condition on the List or a custom field, or every review status in the Space fires it.
Every new client project starts with the same subtasks Task created, then apply a task template The template is copied at that moment. Editing the template later doesn't touch tasks it already built.
A nudge before a deadline is missed Due date arrives, then change priority or status Tasks without a due date are never picked up.
Another app hears about a ClickUp change Any task trigger, then Call webhook Business plan and up. Failed calls are retried for 1 hour and 15 minutes, then dropped.
Something outside ClickUp moves a task Webhook received, then update status or fields The other app has to post to ClickUp's URL, which most accounting and payment tools won't do in that shape on their own.

Thirty Spaces, one automation: template copy or live rollout

Agencies hit this first: one client Space per customer, and the same onboarding automation in each.

New Spaces

Save the Space as a template

  • Saving a Space, Folder or List as a template can bring its automations along into every new location made from it.
  • Right for clients you haven't onboarded yet.
  • A copy is a copy. Change the automation in the template, and the Spaces already made from it keep the old version.
Existing Spaces

Change the automation where it already runs

  • ClickUp's API has no endpoint to create or edit an automation, so this is done in the builder, Space by Space.
  • Thirty Spaces means thirty rounds of the same clicks, and one missed Space quietly runs the old logic.
  • n-frames drives the builder with browser automation, makes the same edit in each Space, and reports which ones changed.

Most agencies need both: a template so new clients start right, and a rollout whenever the process itself changes.

A ClickUp automation that worked last week and now does nothing

The Workspace ran out of actions

How you'll know: Every automation stops on about the same day each month.

Fix: The allowance is shared by the whole Workspace. Open the usage figures in Manage Automations to see which automations spend the most, then narrow their triggers with conditions, or move the busiest job off ClickUp's automations onto its API.

The trigger is close, not exact

How you'll know: The rule fires on some tasks and not others.

Fix: A status renamed from "In Review" to "Review", or a custom field option that changed, no longer matches. Open the automation and reselect the value.

The person it acts as lost access

How you'll know: Actions on one List fail while the same automation works elsewhere.

Fix: Actions run with the permissions of the user who owns the automation. If that person left or was removed from the List, reassign it.

The webhook it calls was switched off

How you'll know: The automation shows as inactive and nobody touched it.

Fix: Deactivating a webhook also deactivates the automations that use it. Turn the webhook back on, then re-enable each automation.

Questions people ask

How many automation actions does ClickUp allow per month?

Free Forever gets 100 actions a month and 5 active automations. Paid plans get larger allowances, and the exact figure depends on the plan you're on, so check the usage view in Manage Automations. Once the Workspace hits its cap, automations pause until the next cycle, so don't hang anything critical on them without watching usage.

Why is my ClickUp automation not working at all?

The usual causes are a used-up monthly allowance, a trigger value that no longer matches (a renamed status, a changed field option), an action the owning user no longer has permission for, or a webhook that was deactivated and took the automation with it. The automation's history in the Automations window usually shows which.

Can I build a ClickUp automation across multiple Spaces at once?

Not as one automation. Each one lives on a Space, Folder or List. You can save a location as a template that carries its automations into new locations, but changing an automation that's already running in many Spaces means editing it in each one.

Is there an API to create ClickUp automations programmatically?

No. ClickUp's API covers tasks, Lists, custom fields, webhooks and more, but automation triggers, conditions and actions are only built in the app. n-frames handles large rollouts by driving the builder with browser automation and checking each result.

Can a ClickUp automation trigger an action in another tool?

Yes, on Business and higher plans. Call webhook sends task data to another app when a trigger fires, and integration actions cover tools such as Slack. It works the other way too: the Webhook received trigger lets an outside app start an automation, as long as that app can post to ClickUp's URL with the details the automation needs.

When the event that should move a task happens somewhere else

The Webhook received trigger solves half of this. ClickUp gives you a URL, and anything that posts to it can start the automation. The catch is the sender. A Stripe payment, a signed proposal or a QuickBooks invoice knows its own invoice number or customer, not the ClickUp task ID, and these tools send their events in their own format to their own kind of endpoint.

So something has to sit between them. n-frames builds that relay: it receives the payment or signature event, checks it's genuine, looks up which ClickUp task it belongs to, and calls the automation with the right fields, so the task moves to Paid or Kickoff the minute it's true. For the API side of ClickUp, see ClickUp integrations. For the templates your automations apply, see ClickUp templates.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.