Feature Requests

Problem: Automation does not work for us, because we need to populate properties relative to other properties in the task (not “hard-coded”). From support: Automations currently only support hardcoded values. Dynamic field values for automations is a great suggestion! I would recommend dropping by our feedback board and leaving any suggestions there!

I'd love if I could bulk select a bunch of tasks, and give them all the same "recurring" rules. Right now I'm going through a ton of different tasks and having to do it one by one.

Would love to have the option to create automations on checklists too not just subtasks/tasks

ORIGINAL DESCRIPTION A single place to manage Automations. Browse existing, Create custom, Apply to single and multiple lists, folders and spaces from one place & manage usage. I have 1 automation that I want to apply to roughly 20 lists, this is a real pain at the moment. ________________ Description created by ClickUp after a survey Users are requesting a centralized location to manage and view all automation throughout their workspace with a large focus on applying a single automation to numerous different locations. They want to be able to view automations from different spaces, lists, and folders in one place, and to organize and group them based on their triggers or outputs. Additionally, users want the ability to create, edit, duplicate, and remove automations from a single location, apply automations to multiple locations, and track the history and analytics of each automation.

Hello ClickUp Support, I am currently building a structured operations system in ClickUp that manages customers, orders, and external services. The goal is to use ClickUp as a lightweight ERP-style workflow for an agency environment. However, I have encountered a limitation in Automations that prevents implementing a fully relational workflow. My scenario: 1. I create an order task (e.g. “Test Order”). 2. The order is linked to a customer using a Relationship field. Example: Order → Relationship → Customer: “Test Customer” 3. From the order, I create another task via a Relationship called External Service (e.g. subcontractor work). ClickUp automatically links the new task back to the order, which works perfectly. Desired behaviour: When the new “External Service” task is created, I would like ClickUp to automatically inherit the Customer relationship from the parent order. Example result: External Service Task → Relationship: Order = Test Order → Relationship: Customer = Test Customer (automatically inherited) Currently this is not possible because: • Automations cannot read Relationship values from another task • Relationship fields cannot populate Custom Fields automatically • Custom Fields cannot dynamically create Relationships Why this matters: If ClickUp allowed automations to read Relationship values and reuse them, it would enable fully relational workflows similar to ERP systems. Example ERP-style structure: Customer → Order → External Services → Invoices → Communication With relational inheritance, ClickUp could automatically propagate key relationships (such as the customer) across all dependent tasks. This would enable: • automated data inheritance • consistent relational structures • ERP-style task hierarchies • far fewer manual steps in complex workflows Feature request: Allow Automations to: 1. Read a Relationship value from another task (e.g. Parent Task) 2. Write that value into: • another Relationship field • a Custom Field 3. Reference Relationship fields in Automation conditions This single capability would dramatically improve relational workflows and make ClickUp viable for more advanced operational systems. Thank you for considering this request. Best regards

Logical operators in Actions are necessary such as AND, OR, XOR, etc... for example, Custom Field Value Or another Custom Field Value

Please create an option to automate removing a task from additional list

It will be nice to start timer from automation and stop timer from automation as well.

Today, when we create comments via API or automations (such as n8n), it's not possible to make real mentions of users or tasks. Even using @nome, ClickUp treats this only as text, without generating notification or mention link. This greatly limits the use of automations in real operation and CRM scenarios, where we need to automatically trigger people within tasks. A practical example: imagine an automation that analyzes the copy of a site and identifies an error. In this case, the ideal would be for the automation to automatically create a comment on the task, mentioning the responsible person, requesting the adjustment. Today this does not work properly, as the “mention” sent via automation is not recognized as a real mention, and the person does not receive notification. Another important point is the possibility of mentioning the task itself or other elements to give more context within the automated comments, especially in more complex flows. Without this support, we are forced to use alternatives such as assigning tasks just to generate notification, or even sending alerts from outside (such as Slack or WhatsApp), which breaks the centralized experience within ClickUp. It would be very important for the API and the automations to support real mentions (of users and tasks), just as it works in the manual editor. This would allow creating much more intelligent automations, with automatic, contextual and truly functional communication within the platform.