Enable Automation to work for Tasks Created by API, Import or Blueprint/Request Form

I have just learned that Automations in Wrike (either in Settings or in the Space itself) do not work for 99% of tasks in my projects. Based on Wrike customer service note: "According to one of the Automation Engine restrictions, existing active automation rules won’t be triggered if the tasks or projects that the rules should apply to were initially created through API, mass actions, or Excel import. However, if you later make manual changes to these tasks or projects or edit the existing active rules, these rules will be triggered by the items initially created through API, mass actions, or Excel import."

I would like to request automations to apply to all tasks regardless of how they are created. This is a huge inconsistency - some tasks get automatic comments or other automations and then vast majority does not.

Find more posts tagged with

Gathering votes

Status: Gathering votes

Comments

Cansu Yetisgin

Thank you for taking the time to share your feedback @Eliska Ohler, I'm passing it on to our team.

Curtis J

+1 for this. We rely heavily on the automations to notify team members and change statuses for tasks. As we scale up, we need to create these tasks via the bulk import Excel function. Not having the automations work is a huge problem.

Cansu Yetisgin

Hi @Curtis J, welcome to the Community and thank you for adding your support here!

Idoya Sanz

Hello! is there any news on this feature? I would also need the automation rules to work for projects that have been created from blueprints.

Ian Kizer

1 Upping this.

In an enterprise integrated workflow, it would be great to be able to use Wrike automations for actions carried out by the API.

Elizaveta Bogdanova

Hi folks! If the trigger comes via API, automation will not be triggered because it's not currently supported. If the trigger comes via in-app mass actions like creation via Request Forms, blueprints, or duplication, it will work, but there's a limit for 250 items created, it won't work after that limit is reached.

MSCC Consulting

+1 Vote!

Hello Team Wrike! I am facing the same issue when automating my enterprise tasks between systems. I would like to trigger Wrike automations for tasks created via the API. Is there a plan to implement this feature in the future?

Rohan V

Hi @MSCC Consulting 👋 Welcome to the Community, and thanks for the +1 upvote! Currently, this isn't on the roadmap for this year, but if there are any updates in the coming months, we'll be sure to let you know 👍

Chris DeFelice

I really need this.

Sofia Felici

+1 vote for this, but I would give it another 10 if I could

Currently, I am unable to implement automations on all tasks in my company's projects, because all tasks are created through an automation: within the project, there is a custom field that, when flagged, ensures that all tasks (taken from various parts of different blueprints) are added to the project.

This automation is very convenient and allows us to create tasks within an already created project - which unfortunately is not possible via request forms, since in request forms it is not possible for the user to select which project to add the tasks to.

Unfortunately, however, the fact that the tasks are created automatically does not allow us to activate other automations on the tasks, which is so bad for us

Rohan V

Thanks so much, everyone, for upvoting, sharing your feedback and use cases. While there are no updates to share at this time, we are making sure to send every comment from the post to the Product Team. In case of any changes or developments, we will definitely share an update. Thank you again for your patience and understanding!

Beth, Williams

We also really need this feature- it seems like something that most with API integrations would need, as a fundamental automation.

Rohan V

Welcome to the Community, @Beth, Williams! Thank you for sharing your feedback here.

Daniel Dutra

We here in Brazil also need this feature. We are integrating wrike with external tools, and many flows would be greatly improved if API calls actually triggered automations.

Meanwhile, it would be nice to have this limitation clearly stated in the API documentation. We've only discovered this after a lot of development. :-(

Guilherme Leroy

Help us!!!

Rohan V

Welcome to the Community @Daniel Dutra and @Guilherme Leroy! 👋

Thank you for taking the time to share your comments here. While there is no update to share at this time, I will make sure to forward your comments and your feedback regarding the API documentation to our team. I’ll keep a close eye on any changes, and if there are any updates in the future, we will definitely post them in the Community.

Sofia Felici

I still think this post doesn't have enough votes and visibility.

I've discovered in these days that some features may not work properly if the trigger point is modified via automation.

In my case: I've implemented an automation that clears dates of a task when that task is set to Canceled status.
The issue is that if the task in Canceled status is the predecessor of another task, I would expect the dates of the successor task to be modified accordingly.
Well, this doesn't happen. The reason given by support is that "When an automation rule deletes the dates of a predecessor task, this is considered a mass action or a system action, not a manual user change. Wrike’s automation engine does not trigger dependency rescheduling based on date changes made by automation rules or mass actions. This is expected and is a known technical limitation."

The only solution I have to make the project plan work properly with dependencies is to clear dates manually, and this is really a constraint.
Wrike provides automations but then doesn't guarantee the complete infrastructure to work with these automations.

Guilherme Leroy

It's a shame. It's made it impossible to use Wrike here, so we're canceling the service and switching tools!

Matthew Connell

The reasoning given for not providing this obvious functionality is also puzzling at best. "iT cOuLd TrIgGeR iNfINiTe LoOpS". Really? Boy that does sound like a really tough problem to solve! /s

I wonder how Wrike Integrate solves that? I guess if you pay for the license you will discover the true nature of this "problem" is marketing all along, not technical. A lovely bait and switch!