Feature Requests

From Support Ticket: I can't automate status change or anything based on email thread (eg WHEN New Email received THEN change status)

Add the ability to create custom automations, including webhooks to personal DMs

I have many automations with descriptions, and scrolling through them to find the one I need is a pain. It would be helpful to have a 'Search automations...' function, similar to the 'Search tasks...' feature in views.

Add the ability to apply folder and space templates via the "Create Folder" and "Create Space" automation actions, similar to how you can now apply list templates in the "Create List" action (with date remapping, import settings, etc). This would let you spin up entire folder or space structures automatically when triggered by status changes, forms, scheduled dates, and more.

We'd love to be able to automate: When a task or subtask is created, and the task creator IS/ISN'T [User], then [Action] We have clients creating tasks in our workspaces, and so it would be helpful for specific people to get notified when those happen.

The problem we want to solve: We have product team - with 5 members, we want that the status CONFIRMED is set only by these people, no one else must be able to skip status TO CONFIRM and set straight CONFIRMED. So the feature requester (not from Product Team) must set status TO CONFIRM, and he is not allowed to skip this and set stright CONFIRMED. Infact the important thing is that anyone from the Product Team is notified about the feature. So based on that - We created automation that - incase none - "is not any of Team" of Product Team is as watcher, that means none of them is notified by the task. Also if any of them received task in status TO CONFIRM and sets CONFIRMED then automation is not executed, because when they set status they are automatically followers. In result we are able to reset the status back to DRAFT incase someone tries to skip the TO CONFIRM, and incase the current user is from Product Team, then by changing status CONFIRMED he automatically becomes watcher, so its allowed for him. This all works - except one thing - you cannot create automation by providing Product Team, since "is not any of Product Team" is not working, the current workaround is by mentioning every member of Product Team - like is not John, is not Anna, etc. This ir maintanability issue - because when changing team, you must also go and find the automation, instead I would like to create automation mentioning only the Product Team, and the automation at execution moment looks at Team members, looks at Watchers and answers is it there a team member in watcher list or not.

In the 'Change task name' action for an automation triggered by 'Subtask Created', the dynamic variable for Parent Task Name is missing from the list of available fields. Use Case: Our video production workflow relies on creating parent "Batch" tasks with several subtask deliverables. For clarity and file management, it is essential that each subtask is automatically renamed to include the parent batch's name (e.g., "Batch 02 - Mixed Variation 1"). Without this variable, we have to manually rename every single subtask, which is time-consuming and prone to error. Adding the Parent Task Name variable would automate a critical step and ensure consistency across all our projects. This seems like a very very simple addition that would take long, please HELP!!

I'd like to be able to set the Sharing and Permissions on a task via automation. Currently this option does not exist. A simple use case would be: Upon creation of a task, set Sharing and Permission to the task creator and the ClickUp Team responsible for the list/the list owner. In general it seems like the Sharing and Permission on Tasks (aka private tasks) is an underserved feature. I'm guessing it's maybe not the most popular feature per usage, but then personally, I wasn't aware of its existence, and an automation tie-in feels like it could make this more usable.

It appears that the “Include Threaded Comments” checkbox has been removed from ClickUp Automations. Previously, this option allowed users to choose whether replies within comment threads should trigger an automation. This was extremely useful for teams that organize discussions using threads while still relying on automations for notifications and workflow actions. Expected behavior * Restore the “Include Threaded Comments” checkbox as an option when configuring comment-based automations. * Allow users to choose whether threaded replies should trigger the automation. Why this matters * Threaded conversations help keep task discussions organized. * Teams should be able to decide whether threaded replies should trigger automations instead of being forced to use only top-level comments. * Existing workflows that depended on this behavior can continue working without requiring users to move discussions outside of threads. This was a very useful option, and bringing it back would restore flexibility while maintaining the benefits of threaded discussions.