Automation at the TASK LEVEL | Voters

Automation at the TASK LEVEL

planned

Mukul Singh

Right now, automations are done at the list level. This gives far less control since every task in that last would be subject to that automation. I am suggesting that automations be done at the TASK level so that you can set something for just 1 task.

May 2, 2020

Harold

I would like an automation that makes it possible to allow people who do not have access to a list to access a specific task in that list.

Carolina Saraiva

I would like to create an automation that fromwhen the status is changed to 'x' status, it removes the task form the list.,

Katie Evridge

Is the plan for this automation to be at the parent task or also the subtask level?

Zach

And as for an update to this feature request...
Caroline’s update (definitely go try out the new button custom fields!) is a solid option to use in the meantime while we work on building out the original feature request here. 
In fact, we’re in the early stages of that work now, so please stay tuned!

Uriah Inspiration

thanks!

Caroline Ginty

Hi everyone - happy Friday! I wanted to share with you the new Button Custom Field, which is now live in all Workspaces! With a Button field, you can manually trigger automations for specific tasks with, you guessed it, the click of a button. You can create Button fields on any List, Folder, or Space in your Workspace, and can customize the text on the button, add an optional color/icon, and more. Please reach out with any feedback!

Here's a quick demo and walkthrough to get you started: https://share.clickup-stg.com/clip/s/t333/d58e5f9f-bb2a-4e9d-997c-6a4321ab7253/d58e5f9f-bb2a-4e9d-997c-6a4321ab7253.webm?filename=screen-recording-2025-07-18-17%3A07.webm

Vincent D'Amico

Caroline Ginty 
Thanks for sharing this, but this button lacks enough power to handle things.  It's a great first step but more is needed behind it.  I was very excited when i saw this posted on reddit last weekend.
The Button needs Pressed Statuses and Logic.  It can spam notifications since there's no indication if its pressed or not.
For instance, to control automations it has to have different states if its been pressed.  There is no in between it can keep looping automations since there is no pressed status.  For me creating custom automations needing checkboxes etc is still the way thats need to go right now. 
Also I do believe you are limited and can not modify the left side of the automations.  So you are limited to what automations it can control.

Caroline Ginty

Vincent D'Amico Thank you for this feedback - it is greatly appreciated! We will certainly be continuing to add functionality to this new field type, so it's great to hear about what you would like to see.

Mark Khazanovich

Caroline Ginty This feature definitely has its uses, but it's not quite "task-level automation" - what we're really looking for are task-level automations that enable us to streamline our recurring processes.

For example, when the status changes of a particular task, a subtask is created with that is assigned to the appropriate user and with a due date of tomorrow. Then, another automation that when that subtask is completed, the parent task updates with the appropriate user, status, due date, etc

Rakesh Rathore

Caroline Ginty 
Thanks for sharing the demo, 
But there will be a bug, when i have created two or more then two buttons in the single list, then all buttons automotions are worked on single click, this will lost the control for the button field. 
please solve this, if we clicked on the single button then automation will excuted for the respective button only.

Gurminder Dhami

Caroline Ginty Thanks for rolling this out. As righly pointed out by Vincent D'Amico there scope of improvements. 
Plus I want to add 1 more thing, that the placement for this Button when a Task is Opened should not be mixed within Custom Fields. 
It should be either in the Sidebar or in the area where key properties (Start Due Date etc.) are shown. 
Having these buttons at prominent space in the Task View would make it convenient to use.

Nicola Graves

Caroline Ginty Thank you for this but not quite the automation at task level I would like. It would be better for us to have an automation that works at a task level that when a Task A status is set for ready for internal approval, it add's a comment into the task where you can mention someone into the task for them to review it.

Tony Henderson

Caroline Ginty as with others, I do like this feature but it's not really delivering what I need. I need to be able to trigger from task A when it meets a certain condition in field X but then cross reference or update field Y in task B.
As a simplified use case;
I add an install budget in my budget task.
I then add installation task(s) each with their own cost. 
I want to be able to automatically trigger a flag if the sum of the cost is greater than the budget.
I know I could create the install costs as columns in the budget task but we can have multiple installations, each with their own parameters and workflow that we need to track separately. 
We would need to create some kind of rolling decrement from the budget or perform a sum of the installation costs and compare to the budget, and then trigger the flag. 
This is just one example and we have several more.
I also know we can achieve this through API's (which costs) but it would be such a powerful enabler if we can use automation's across different tasks and fields.

Caroline Ginty

Mark Khazanovich Thanks for your feedback! We know this isn't a full solve for what all the voters here are looking for, which is why I haven't marked this request Complete, but wanted folks here to be aware of the option. Thanks again!

Caroline Ginty

Tony Henderson Thanks for your feedback! We'll be continuing to work to make this better for you over the coming weeks and months.

Guy Mannerings

I simply want an automation where each day the Task sets itself and its subtasks as Open.
So rather than creating a new Task, it wipes itself clean, as it were.
Useful for daily repeating Tasks where you know you want to check certain things off, but don't need it to just keep creating new Tasks all the time.

Ruud

Guy Mannerings have you tried recurring task option?

Guy Mannerings

Ruud I have thought about this, but:-

There are no settings for changing subtasks' statuses on repeat. So the parent task repeats and can be set to "Open", but the subtasks can't.
I actually don't want to give these due dates, because I don't want them to appear on my calendar. But there is no way to repeat a task without giving it a due date.
I worry about having hundreds of repeating tasks, clogging up my ClickUp and slowing it down. It seems inevitable that it would get slow the more tasks you have.

Ruud

Guy Mannerings Other alternative (for now), use the recurring automation to run daily and run through all tasks that have a certain type/custom field/checkbox value to reopen them.  E.g. a daily custom field checkbox.
Not sure if the AI automations are already powerful enough to do just that.
Doesn't take away this is a good feature, I just thougth your use case could maybe already be resolved ;)

Guy Mannerings

Ruud Cool idea! Will look in to this, thanks!

Tony Henderson

If they were at the task level, would this include the ability to have conditional automation across tasks; i.e. if task 1 meets condition x, then task 2 should have field Y updated? This is what I really need.

Zach

marked this post as

planned

Jacques Rossouw

I hate that I cannot trigger an automation on a task level 🙈

Vanessa Machado

This would be so helpful for project team workflows. This way we can have reminders on specific important tasks.

→