Automation rule trigger on task name
It doesn't look like we currently have a way to create an automation rule that is triggered by a task name. For example, if the task name contains the word "video" we'd want an automation rule to tag that task with the appropriate folder. This would help all those tasks that get created for one team but also need shared with another (sooner rather than later).
Welcome to the Community Kayla Upchurch 👋 This is a very interesting idea, thank you for sharing it!
I'll now pass it on to our Product team responsible for request forms 👍
Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Lisa Wrike Team member Become a Wrike expert with Wrike Discover
Agreed! I love the idea of automations in Wrike but have found the feature to be in a fairly early state of development. Kayla Upchurch I don't know if this will help your use case at all, but what I had to do to get the automations to work kinda like that was to use dedicated folders for triggering the automations. To get tasks created from outside wrike, I had to create trigger folders. Power Automate then emails notifications to the Wrike email address of the trigger folders, which then activate the automation within Wrike to, in our case, create a project from a specific blueprint in another specific folder. Then the automation moves that original task that was created in the trigger folder to the folder the Blueprint was created in. Our PM then has to manually rename the new project and assign dates manually.
It would be very nice if the automations were more robust and could respond to text, not only using text to trigger specific automations, but also to be able to take recieved text and add it to Project and Task titles, descriptions, etc.
Hi @..., not quite, although these are some great additions. I'm looking for a way to tag a folder when the task name contains a value. Giving the ability to cross tag tasks for awareness among other teams. Our specific use case is when a task is created that contains the word "video", we want to tag the task with the "video production" folder so that the video production team is aware of any video related requests.
Does anyone else feel it is limiting to have the following rule:
Automation rules won't be triggered in case the changes to tasks or projects are made by another automation rule.
I want to automate a Project rule to move the project location when the status is Complete but I have an automation rule in place already that sets the project status to Complete when all sub-tasks or related tasks are Complete.
Everyone remembers to Complete their own tasks but no one Completes the project. If the rule completes the project, the project should be moved to the Completed folder and removed from the In Progress folder. Any thoughts?
TYIA
Hi Bonnie Watkins, would it help to add another action to mention the user and ask them to complete the Project as well?