It would be great if we could set up automations so that it could scan for a trigger + the person assigned to the task that triggered it (for example the trigger can be a adding a tag -- next step is the automation should scan for what the assignee of the task is) and use this information to populate the "to" field in an send email automation (since Clickup already has the email of the member)

As this is merged with the ticket I created: it would be great if I have a custom "email" slot entered by a person filling in the form, so that these people that are not part of our clickup environment can receive a copy of their own answers.

I'd also love if you would be able to email anyone watching the task too

And any other "People" Custom Field as well.

Solve the following and you will solve a problem for everyone in the community. I want a customer to email us for parts and Cu creates a task and immediately auto reply to them using the "created by" email address with "We got your request". I don't need to have them as CU user. They want to order a part. Not learn a system. All that is needed to to make available for merge field is the "Created by" field to "TO:" field. This would be a game change for a ticket system.

Also see https://clickup.canny.io/feature-requests/p/allow-assignees-to-be-chosen-in-the-to-section-of-an-email-automation (merge?)

To really take advantage of being a full email ticketing system we would like to be able to set a custom automatic reply from a task when the user creates a task or it reaches other statuses.

We have 5 statuses

New - Ticket/task just received

Open - Tech is actively working on it

Pending - Waiting on user for information or reply

On Hold - Scheduled for a certain date, Waiting on parts or vender

Complete/Closed - Ticket is done

For example:

I need assistance so I email support@domain.com which pops open a task in ClickUp. If I cc someone in they are also attached and receive updates. ClickUp then emails back with an auto notice that the ticket has been open with the task ID in the ticket (There needs to be an option to pick either Task ID or the Custom Task ID). Once the support staff starts working there is communication. When the support is waiting to hear from someone it goes into pending. If the ticket/task is in pending it will email a daily response checking in for the reply. If we haven't heard from that person in x amount of time, ours is set to 4 days, it auto closes the ticket.

We also have auto routing based on subject/body of incoming email which is nice but not necessary.

One thing I like about your setup is the ability to email separate people within a single task separately. So If I need approval or contacting a vendor I can keep it all within one task. Subtasks could be used for this and the main portion can keep the user that submitted the task up to date. This is probably the best solution.

There also needs to be the ability to exclude certain emails. So if you have a proactive ticket from some vendor or something like that going to your board. You don't want to end up with a ticket loop.

The last think would be the option to deny emails. If someone is trying to spam the board you want to be able to deny those.

Let me know if you need further information on this?