Feature Requests

Need ability to restrict who can and cannot see and who can and cannot change Automations. Automations should still be able to run when conditions are satisfied, but their existence should be made invisible to selected users or roles if/when necessary.

--------------------------------- 🔍 Overview --------------------------------- ClickUp's current status system follows a linear progression model with tasks moving sequentially from one status to the next, right? Well, real-world business processes often require dynamic, multi-path workflows with conditional transitions. To bridge this gap, I propose an advanced visual workflow builder—similar to Jira’s workflow editor—that would provide greater flexibility in managing statuses and processes. --------------------------------- 🎯 Key Benefits --------------------------------- 🔹 Non-Linear Transitions – Move beyond the A-to-B status system and allow multiple pathways. 🔹 Visual Workflow Mapping – Enable teams to design and visualize workflows using a drag-and-drop builder (possibly leveraging ClickUp Whiteboards). 🔹 Conditional Status Progression – Set requirements (e.g., field completion or approvals) before tasks can transition to the next stage. 🔹 Native Automation Integration – Leverage ClickUp Automations to streamline process execution. (Technically, it would be possible out of the box but there's room for extension.) 🔹 Improved Process Control – Spaces could define custom process rules, ensuring compliance and structure in task management. --------------------------------- 📌 Suggested Features --------------------------------- 🔹 Visual Builder – A flowchart-style interface for designing workflows intuitively. 🔹 Flexible Status Paths – Allow statuses to branch into different paths based on rules. 🔹 Automated Transitions – Integrate workflow steps with ClickUp Automations for hands-free status updates. 🔹 Conditional Logic – Require specific conditions (fields, approvals, dependencies) before tasks progress. 🔹 Field Locking – Lock down fields after a particular status of the workflow. 🔹 Whiteboard Integration – Embed workflows into ClickUp Whiteboards for real-time collaboration. --------------------------------- 📈 Long-Term Vision --------------------------------- This feature would elevate ClickUp’s workflow capabilities, making it a more powerful tool for more complex business processes. Over time, it could evolve into a fully conditioned process engine, allowing teams to enforce rules and possibly integrate with the upcoming Teams Hub vision, automate tasks, and finally create more bespoke operational flows. --------------------------------- 💡 Why This Matters for ClickUp Users --------------------------------- 🔹 Enhances Workflow Flexibility – Supports non-linear, adaptable processes. 🔹 Boosts Productivity – Reduces manual status management, enhances automation and authenticity to a status being changed. 🔹 Improves Collaboration – Helps teams map out and enforce structured workflows. 🔹 Aligns with Business Needs – Brings ClickUp closer to enterprise-level workflow management tools.

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.

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

Proposed Functionality & Requirements: Automation Trigger: Form submission or new entry added to an intake list. Dynamic Folder Naming: Ability to map the form's "Project Name" field to dynamically set the name of the newly created Folder. Conditional Template Selection: Ability to select and apply a specific Folder Template (preserving all subfolders, lists, views, and custom fields) based on a tag or dropdown field (e.g., "Project Type"). Dynamic Location Routing: Ability to route the newly created Folder into a specific Space or Hierarchy location based on a tag or dropdown field (e.g., "Department"). Current Limitation: Native ClickUp Automations currently lack the action to dynamically generate and name full Folders from templates or route them to specific locations using variable inputs from Form submissions. Business Impact: Eliminates manual project setup, prevents human error during intake, and guarantees standardized operational governance across departments.

I'd love to be able to apply automations on a global level (across the whole workspace). The way our company uses ClickUp means that we want each space to have the same "features", are organized the same, and are utilized the same. This means whenever I create a custom automation for one space, I then have to manually add it to all of our other spaces. We have quite a few spaces, so it takes a while. Having the ability to apply automations to a whole workspace would save a lot of time :).

Default due-date time at the Space/List level. Currently, when a due date is set, the time defaults to end-of-day (midnight). I want to configure a default due time (e.g. 4:00 PM) at the Space or List level, so every new due date inherits that time automatically, while still letting the assignee override it per task. Right now the only options are manually clicking "Add time" on each task, or building automations that risk overwriting a user's custom time. A native default-time setting would solve this cleanly.

What would make automations significantly better, in my experience, is them being able to do 2 things: Know what Today is, as in when you have an automation that is looking for, say, a best time to contact and the date in the field is today's date, then show that task, DM the team member, whatever. That would unlock a TON of productivity. It would also be game changing to be able to have automations run on a scheduled trigger. I know that is previously shown as not on the roadmap, but it really would be incredible. To be able to select a certain day of the week it runs, or even a specific time, would be incredible. I understand that does probably undercut the use case and value prop of Super Agents in a way, but this would keep adjacent abilities contained inside the lists where they operate and keep the information bloat that sometimes happens with SuperAgents at bay for lighter automated tasks. I think the first one, really, would be the most impactful. My use case, being outside sales, is to be able to set a custom field for the days that a business is available, or a day that they say 'I'm only in on Thursday and Friday, call me one of those days,' and be able to set that variance in a custom field and then the automation knows when the current day of the week is matching with what's in that custom field, and then surface that lead in my CRM view of today's to-contact leads/people. I do understand tho, that that likely requires the automations to be able to run on a schedule, which seems to not be on the roadmap...

Automations that are set in a list should be adopted directly when duplicating them, so that you no longer have to manually duplicate each individual automation.