604
Add Tags to 'When' side of automation | Tag as Automation trigger
in progress
Cristian Cabrera
It would be a good idea to add the tags in the 'When' condition. Our idea is to be able to automate with tags.
Log In
Zach - ClickUp
in progress
Don't mind the ugly screenshot I'm sharing. But we're working on it folks 🫡
Maren Fox
Zach - ClickUp: 😍😍😍
Maren Fox
Zach - ClickUp: YES BAYBEEEE
Zach - ClickUp
planned
👀
Zach - ClickUp
Merged in a post:
When tag added/changed/deleted, then do this
Paul Osetinsky
Very much need this ability. When I tag a task, I want it to be added to certain lists.
Adam Hammond
Yes Zach, that video is perfect!
Zach - ClickUp
Merged in a post:
Allow automations to trigger from tags
Laura Nunnally
Hi, I'm not sure if I'm missing it here, but I was hoping to create a set of automations so that I can use a minimal number of lists and view everything through filters and tags. I want to create a set of automations that would trigger as I process tasks using tags, but I'm not seeing a way of doing this. I think that'd be useful quite a few folks.
Zach - ClickUp
Hey all, I think this one is pretty straightforward but please let me know if I understand the solution correctly here: https://www.loom.com/share/1a21dfd821494b74b6602ef64d306829
João Pimentel
Zach - ClickUp: maybe a mockup of the left part would help us better understand your proposal? But I think you got it right: trigger an automation whenever a tag is added or removed from a task
Gabriel Hoffman
Zach - ClickUp: Perfect! It would be amazing!
A
Andrea Bullock
Zach - ClickUp: Yes. This would work..
Jeremy Stoller
Zach - ClickUp: I think you're on the right track. To clarify... I think you probably need three triggers: Tag Added, Tag Removed, and Tag Changes (but that's a lower priority, IMHO). All of these should accept multiple tags, much like the Status Changes trigger.
Kelsey Ledford
Zach - ClickUp: This would cover our need, thanks!
Nathaniel Cassidy
Zach - ClickUp: Spot on Zach.
Jeremy Stoller's suggestion would be the power version though.
Jan
Zach - ClickUp: Thanks for this video! It's reassuring that you guys are hearing us! I think you are on the right track however, in your solution, it will still need the main trigger for the automation to work. Sometimes, we do not update the status but we just need to add/remove tags in order to create other tasks or move the projects in a separate space. For example, if we are still waiting on payment for a new project but internally we need to prepare for it ahead, we add tags to let our onboarding team start the ball rolling. We add tags for this. We've worked around this scenario using zaps but even zaps are limited as they do not have the "when tag is removed" trigger. If we could do it all within ClickUp, that would be most ideal. Thanks!
Pierre Becher
Zach - ClickUp: correct, but ideally the trigger should work for
- tag added
- tag changed
- tag deleted
Zach - ClickUp
Very helpful, thanks everyone!
Kamryn Wies
I would definitely use this. I've made a work around by using Custom Fields but Tags would be better.
James Crook
It's disappointing how limited clickup's native automations are.
Gerrit Jessen
James Crook: yes, this sucks a lot
Zach - ClickUp
James Crook: we're working on making it better! Thanks for the feedback
M
Mark Vittetoe
Yes, please! I want the setting of ceratin tags to trigger the application of certain templates. Or, for instance, when the "user story" tag is applied, I would like to automatically create two more tasks - one for api end point documentation and one for UX designs, etc. I can only automate this if the creator remembers to add the tag while creating the task (assuming that you would know which tag to apply at that time). If a tag is added after a task is created, I cannot cause it to trigger anything in the automations. This is a real setback for the way we are using ClickUp. I cannot even cause a label change to trigger an action.
Jan
Mark Vittetoe: "I cannot even cause a label change to trigger an action." -- I think you can use "When custom field changes" as the trigger, then just specify which custom field it is, ie in your case the name you assigned to your labels. I hope this makes sense :)
When LABEL NAME changes from any to any, then action.
D
Daniel Antoniów
currently, due to the lack of this function, our company, after entering tasks based on a new task plus a specific one, changes another numerical field, it has to copy these 10,000 tasks from scratch for the automation to start a new task for the process, and after adding the TAGS it would simply change this numerical field, it is used for sorting according to the hierarchy of tasks. Without such automation, we had to have exactly 21 lists and check them every day depending on the implementation of lists with filters for other tags.
That is why the introduction of this function is a must, because it saves us a lot of time, as I wrote before, only the options with TAGS work like a new task, etc. After adding tags, no action will be performed. I am the author of the "AWARENA HIERARCHIA" system - a hierarchy of tasks to know what we have to do in life and work every day according to the best, ideal order of performing these tasks.
thanks to this system, which is currently based on a new task + tags, we have an ideal order in two list views because one is up to 7 days ahead and the second view of the entire list of tasks when the tasks from the first list are completed. Without this automation, we would have 21 lists with tasks for 7 days ahead and another 21 lists without time limits, i.e. a total of 42 lists to be checked every day.
The next stage of development is the introduction of automation based on adding or removing tags, because this will allow us to automate the changes in our numerical field in the task already created, which is used to determine the best order for performing all tasks
Load More
→