[Automations] Possibility for an automation to be triggered by a change of state generated by another automation (not just manually)

Avatar
Giovanni De Giovanni

  • We would greatly appreciate if an automation could be triggered by a change of state generated by another automation (not just manually). I won't bore the Community with our fairly complex use case, but if I were to explain it, I'm confident you would immediately understand how crucial this step is. Conditioning the trigger of this automation on the circumstance that the state is manually changed would essentially render the automation meaningless.
Upvote 25
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos
12 comments
Avatar
Lisa

Hey Giovanni De Giovanni, could you please clarify if by "change of state" you mean status change, or is it something else? Thanks! 

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

1
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos
Avatar
Giovanni De Giovanni

Hi Lisa, yes, I do absolutely mean "status change" (I apologize if I was not clear in describing it).

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos
Avatar
Lisa

Thanks a lot for clarifying Giovanni De Giovanni! I've now discussed your feedback with the team and for now, it's not possible to have an automation rule trigger another rule. Our team is aware of this and they would like to address this in the future.

Thank you for your feedback and for posting your idea 🙌

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

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos
Avatar
Giovanni De Giovanni

Hi Lisa, thanks a lot for your message. I truly hope that this implementation can be seriously considered and maintained in your development pipeline, as it would objectively mark a significant change from the past, providing the opportunity to customize the workflows of Wrike's customers (I'm not referring to workflows in the technical sense used by Wrike - new-in-progress-etc. - but in a broader sense) and reducing the reliance on external automation tools like Workato and Zapier.

1
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos
Avatar
Calvin Coberly

Lisa - What is the progress of adding this into Wrike? I would also love to have this be a possibility as well!

3
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos
Avatar
Rohan V

Hi Calvin Coberly, Welcome to the forums! 🙂
 
I'm chiming in on behalf of Lisa. Currently, there are no further updates for this suggestion. We require a minimum of 60 upvotes on the original feedback post to assign a status to it. You can read more about our product feedback guidelines in this article.
 
In the meantime, feel free to let me know if you need assistance with anything else! 👍

Rohan V Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover

Rohan V Wrike Team member Become a Wrike expert with Wrike Discover

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos
Avatar
Giovanni De Giovanni

Hi Rohan,

Since I was the author of the first message, and given that more than a year has passed since I wrote it, I’ve had the opportunity over the past year to analyze the situation more deeply and encounter further limitations that, unfortunately, Wrike’s internal automations still have.

In light of the experience I have gained over this year, I would like to broaden the context of the original request a bit.
What I (and I believe many other Wrike users as well) would like to see is that Wrike’s internal automations are actually triggered by the event indicated in the "Trigger" section when creating a new automation, and that the current limitations are removed, such as:

  • The automation does not trigger if the event that should trigger it (theoretical trigger) was performed by another internal automation;
  • The automation does not trigger if the task that should trigger it was created via Blueprint;
  • The automation does not trigger if the task that should trigger it was created via Workato.

Unfortunately, all these scenarios paralyze the "automate-ability" of operations, undermining trust in the tool because, when setting up a workflow, you’re forced to ask yourself a thousand preliminary questions to avoid the possibility that any of the real-life cases you will encounter might fall into one of the limitations I described.

It’s a real shame because, apart from these limitations, the internal automations menu would be quite complete and certainly suitable for managing a large number of automations without having to resort to using Workato, which could then be reserved for handling more complex automations.

I am available to provide further information if necessary.

Thank you, and good work, Giovanni

3
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos
Avatar
Rohan V

 
Thank you for taking the time and effort to provide such detailed feedback. I understand that more than a year has passed since your original message, and we genuinely appreciate the insights and perspectives you've shared based on your experiences with Automations over the past year. We will ensure your concerns are communicated to the relevant Product Teams, and if we need further information, we will definitely reach out to you.
 
Thank you for your patience and understanding as we work towards enhancing the functionality of our platform.

Rohan V Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover

Rohan V Wrike Team member Become a Wrike expert with Wrike Discover

1
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos
Avatar
Kristy Schaan

Hello Giovanni,

You are spot on and there are a number of other posts on this subject.  You can seek those out and add to them if they are closer to 60 or provide additional links to your post and/or others to help move the process along toward getting 60 votes for your post. 

Kristy

1
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos
Avatar
Tracy McCrory

Thank you for submitting this request. We are in the process of onboarding and setting up automations and were running into this exact issue this week. Definitely giving this an upvote!

1
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos
Avatar
Craig Lansley

I would also like to upvote this suggestion. Due to the limitation of 250 items being created by a request form submission I have to create a few sub admin tasks seperately in a project via automation which works but then date rescheduling is not possible because of this automation limitation (not allowed to be triggered by another automation). 

1
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos
Avatar
Rohan V

Hey all 👋 thank you for sharing your feedback, use cases, and for upvoting the post above. Your comments have been forwarded to the responsible Product Team for their visibility. At this time, I don’t have any updates to share, but I’ll keep you in the loop if there’s any progress in the coming months.
 
Thanks again!

Rohan V Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover

Rohan V Wrike Team member Become a Wrike expert with Wrike Discover

2
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Folllowing List for Post: [Automations] Possibility for an automation to be triggered by a change of state generated by another automation (not just manually)
[this list is visible for admins and agents only]

Top

Upcoming Live Sessions

Didn’t find what you were looking for? Write new post