Feature Requests

I really hate that I always have plenty of Company Logos within my task attachements. Please stop that.

An Inbox for your Email in ClickUp! You'll be able to see all of your emails and replace your email inbox with ClickUp. You'll also be able to quickly link and create tasks, docs, and more to emails.

Enable ClickUp's email-to-task feature to recognize email threads and add reply emails to the existing task instead of creating duplicate tasks. Current Behavior: When using ClickUp's email-to-task functionality: Initial email to List email address creates Task A User replies to client from within ClickUp task Client replies to that email thread ClickUp creates NEW Task B instead of adding the reply to Task A Requested Behavior: When a client replies to an email thread that originated from a ClickUp task: ClickUp should recognize the email thread/conversation ID Add the reply as a comment/update to the original task Maintain the full email conversation within one task Optionally notify assigned users of the new reply Business Use Case: Many teams want to use ClickUp as a customer support help desk system with a single support email address (e.g., support@company.com ). For this to work effectively, email conversations need to be threaded within the same task, not scattered across multiple tasks. Current Workaround Limitations: Manual task merging (time-consuming, error-prone) Losing conversation history across multiple tasks Poor customer experience tracking Forces teams to purchase separate help desk software (Teamwork, Front, Help Scout, Zendesk) just for email threading Impact: This feature would allow ClickUp to serve as a true help desk ticketing system, eliminating the need for third-party integrations and making ClickUp more competitive with dedicated support platforms. Technical Requirements: Parse email headers to identify thread/conversation IDs Match incoming emails to existing tasks by conversation ID Add subsequent emails as task comments with email metadata Maintain ability to reply from task and continue thread Priority: High - This is a major limitation preventing ClickUp from being used as a complete support solution. Thank you!

When you create an email action in an automation, you have to choose which email to send from in the automation. This is a serious limitiation. If you have multiple users, you would often want them to be able to send emails individually, and not all rely on the same shared account. Only way around this is to create individual automations for each user. If you have 10 users, that means 10 automations! Also, you have to figure out a way to know which automation to trigger. Back in piloting I created a button on a task type that neatly did this: Use the custom field "Customer email" as To Use the task title as Subject Use the task description as Body Voila: one button to create an email from within clickup, all based on dynamic data. Except it wouldn't work for multiple users, as I found out the hard way when adding more user emails. The AI Brain actually suggested this clunky solution: create one button for each automation, ie: "Send email (Ken)", "Send email (Dave)" and so on. Then link the buttons to different automations. Of course I'll have none of that, so now the button is triggering Make, which in turn finds out who pressed the button, writes this back to a custom field on the task, which in turn triggers one of those 10 automations. Yes, it's even more clunky, but at least the users won't see 10 buttons, and accidentally hit the wrong one (which does nothing)... Today the only practical use case I can see for the send email action, is when you have a shared account like support@ or sales@. But not all use cases involve shared email accounts.

We need a way for email replies to trigger automations. I need to update my tasks when an email comes in for ITSM that I need to change the status so I know I need to view it again.

Please add the functionality to integrate a shared outlook inbox with the email integration ClickApp

It would be nice if the email to task would clean up the contents of the email before attaching it to the task. They sometimes become hard to read with email signatures and spacing.

Hi, We use ClickUp as a tool to manage various tasks. This includes tasks for which several emails were the trigger and where processing the respective email for documentation must be a separate subtask. These emails cannot be forwarded to ClickUp today because emails to lists generate tasks and emails to tickets become comments in the respective ticket. It would therefore be helpful if a task had, for example, a second email address to which emails could be sent to record subtasks. salute erik

Import contacts from email account. Autofilled when typing "To: " line.

We use ClickUp as an IT ticketing system. Users email itsupport@domainname.tld (Google Workspace). When a requester replies to an existing ticket email (subject contains “Ticket #119”, etc.), ClickUp currently creates a new task when the message is forwarded/ingested, instead of attaching the reply to the original ticket task. Requested feature: Add subject-based email threading so inbound emails can be automatically associated to an existing task when the subject line matches a known ticket identifier. Acceptance criteria: Workspace admins can define a matching rule; example: Match pattern: Ticket #(\d+) (or similar) Map captured number to Custom Field: Ticket # When an inbound email is ingested (Email to List or other email ingestion address), if the subject matches an existing open task, the email content is added as a comment to that task (attachments preserved), not a new task. If multiple tasks match, provide configurable handling (most recent, prompt, etc.). If no match exists, create a new task (current behavior). Optional: normalize subjects to handle common prefixes like Re:/Fwd:. Why this matters: This would allow ClickUp to behave more like a helpdesk system where email replies stay in one ticket, without per-ticket unique addresses or manual routing rules.