The ability to use "created_by_email" in automations, in ClickUp email and custom fields
Ahmed Abbas
Currently, if a task is created by send an email to the list email address, the original sender email address is being added to the description and the task creator email address is changed to a CU user.
If I want to build a automatic reply, or if I want to easily reply to an email, I would need to copy the email address first.
We need to be able to utilize the original email address in automations, custom fields and in ClickUp email.
The data already has this but we can only utilize it if we use the API:
"data": {
"via": "email",
"trace_id": "########",
"subcategory_id": "#########,
"created_by_email": "example@hotmail.com"
},
Log In
Zach - ClickUp
Merged in a post:
Add "Creator email contains" Condition to Automations
Miraç AKÇA
Hello ClickUp Team,
In the Automations section, we can currently add conditions such as "Task Name Contains" (as shown in the attached screenshot). However, there is no option to add a condition like "Creator email contains" (for example, if the task creator's email address contains a specific domain).
Especially in environments where users from different companies collaborate, being able to trigger automations based on the creator's email domain (e.g., to automatically fill a custom field or start a different workflow) would be extremely useful.
Therefore, I kindly request that you add a "Creator email contains" or "Creator email domain" filter to the automation conditions. This would allow for more flexible and automated processes based on email addresses.
I would greatly appreciate it if you could consider this feedback.
Thank you!
Photo Viewer
View photos in a modal
Zach - ClickUp
Filtering automation conditions by the creator's email domain isn't possible today. The condition picker has some creator-based options, but email isn't one of them. For a shared workspace where users from multiple companies are contributing, routing automations by domain is a clean, non-intrusive way to segment workflows without needing separate spaces.
Not something with a near-term timeline, but it's a reasonable gap and I'm noting it.
Miraç AKÇA
Zach - ClickUp thanks for comment.
We have companies in different spaces. We've designed a demand management system to manage requests between spaces. For example, a request from space X goes to space Y. I haven't seen any space automation that would filter out requests originating from space X. I report all requests in a dashboard, but I don't see a distinction like the number of requests coming from space X. It would be great if we could filter this out.
Miraç AKÇA
Hi Zach - ClickUp, when take action for this request ?