Feature Requests

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.

Keeping track of potential customers is often harder than finding them in the first place. When a lead generation team india https://pearllemonleads.in/lead-generation-team/ handles many conversations, small follow-up details can easily get overlooked. A simple task structure can make each stage easier to see and manage. Instead of relying on scattered notes, teams can record the next action directly alongside the relevant task. This gives everyone a clearer understanding of what needs attention. Different stages can also help separate fresh opportunities from conversations that are already underway. That separation makes daily priorities easier to identify. Assigning tasks to specific people can prevent confusion when several members are involved. Deadlines can provide an additional reminder when an important response is expected. Team comments can be useful for sharing context without creating another place to search for information. A consistent naming system can also make larger lists easier to navigate. For repeated activities, having a familiar workflow can reduce the time spent setting up routine work. Views and filters can then be used to focus on particular groups or pending actions. This kind of organization is especially helpful when priorities change throughout the day. It also allows team members to see progress without constantly asking for updates. Small workflow improvements can make a noticeable difference when the same process happens every week. The most effective setup is usually one that people can understand without extensive instructions. Too many steps can create unnecessary work, so keeping the structure practical is important. Regular feedback from the people using the workflow can reveal where adjustments are needed. Some teams may benefit from more detailed tracking, while others may prefer a simpler approach. Flexibility makes it easier to adapt the process as workloads change. A clear workflow can also make it easier to review unfinished tasks at the end of the day. Over time, these habits can create better visibility across the entire process. The main objective is to keep information organized, responsibilities clear, and follow-ups easy to manage.

Currently we use ClickUp forms for UAT and we are wanting a feature where when an issue is submitted that the task that gets created can move to be a subtask under a UAT parent task we have. This would help us tremendously with accurate reporting and organization.

Give hte users the ability to automate upon task creation based on text contained or not in the task description field. Use case: We forward our emails to create a task list in clickup and based on if the task description contains a specific text like email address- move the tasks to designated Lists and/or add tags. Currently text in task description is not available as a condition upon task creation.

I really need an automation that can do this. When 'X' happens → REMOVE task from list. Currently you can only get an automation to add to a list - I need the inverse. Just moving a task is not a solution. I know this has been requested before, but it's been over 5 years withs no traction https://feedback.clickup.com/feature-requests/p/remove-from-list

Hi ClickUp Support Team, I would like to check whether it is possible to enable file attachments when setting up an automated email through ClickUp Automations. Currently, we can set up an automation to send an email, but it appears that the email can only contain text/content without the ability to attach a file from the ClickUp task. For our workflow, being able to automatically send an email together with a file attachment would be very useful. For example, when a task reaches a certain status, we would like ClickUp to automatically send an email to the relevant recipient with a document or file attached to the task. If the automation can only send a simple email without attachments, the use case for automated emails is quite limited for our workflow. Could you please advise: Is there currently a way to attach files from a ClickUp task to an automated email? If not, is this feature planned or available through any workaround/integration? If this is not currently supported, could you consider this as a feature request? This capability would significantly improve our workflow automation and reduce the need for manual email follow-ups. Thank you, and I look forward to your advice.

When a client submits a Form, I'd like to automatically send them a public link to the task that was created. Currently, the "Task Link" variable in email Automations only provides an internal link ( app.clickup.com ) that requires login. I'd like a new Automation action that enables public sharing on a task and exposes the public URL as a variable, so it can be included in a "Send email" action. This would be extremely useful for support/helpdesk workflows where external clients need to view their request status without being invited as guests (which consumes a license). Use case: Form submission → Automation enables public sharing on the task → Sends confirmation email to the client with the public task link → Client can view their request and reply by email to add comments.

Managing files from different financial systems can create unnecessary extra steps. A financial file conversion tool https://lemsubs.com/tools/financial-file-converter could help make these workflows easier to organize within a project. Teams often receive spreadsheets, reports, statements, and exported data in different formats. Before the information can be reviewed, someone may need to manually convert or restructure the files. This can become difficult when several files are involved in the same task. It would be useful to have a more flexible way to handle file conversion as part of the workflow. Users could upload a supported file and choose the format needed for the next step. The converted version could remain attached to the original task for easier tracking. This would also help keep related files and project discussions in one place. A clear record of the original and converted files would reduce confusion. Teams could spend less time switching between different applications. It may also help when sharing information with people who use different systems. Automation options could make the process even more useful for recurring tasks. For example, selected file types could be converted automatically when added. The original file should remain available to avoid losing source information. Permissions could also control who is allowed to access converted files. This feature could fit well into document-heavy workflows. It would be especially helpful for teams managing regular reports and structured data. The goal would be to reduce repetitive manual steps. A simple conversion workflow could make file management more consistent. It could also improve collaboration when multiple people work with the same information. Having this capability connected to tasks would keep the process easier to follow. I think this could be a useful addition for teams handling different file formats regularly.