Automation in Wrike
Wrike’s Automation helps reduce repetitive and manual work, speeds up your work process, and minimizes the likelihood of human error. Instead of handling all the work by yourself, you and your team can employ the automation of various actions with tasks, projects, and custom items in Wrike.
Automation is easy to use and doesn’t require any coding experience to create automation rules. The rules have a simple “WHEN ..., THEN …” structure. The automation rule constructor guides you through the rule creation process. All you need to do is let Wrike know:
-
Which tasks or projects to apply the rule to. 1
-
When to trigger the rule — the "WHEN" statement. 2
-
Additional conditions for the trigger to meet before the rule is triggered — the additional "IF" statement. This step is optional. 3
-
Additional mention for comments or mentioning followers. 4
-
What action should happen when the rule is triggered — the “THEN” statement. 5
Wrike Automation is available on the account level and on the space level.
|
Account-level rule |
Space-level rule |
|
|---|---|---|
|
Managed by |
Account admins and owner |
Space admins |
|
Applies to |
|
|
|
Scope |
Works in up to 10 specific folders, projects, and spaces across the entire account |
Works in the entire space or in up to 10 specific folders and projects within the space |
Here are a couple of automation rule examples:
-
WHEN the statuses of tasks (from a certain project) don’t change for 5 days from "Pending changes," THEN @mention assignees and leave a comment.
-
WHEN the status of projects (from a certain space) changes to "Completed," THEN move the projects to the "Archive" folder.
Rule Limits by Account Type
-
Team Accounts: Up to 1,000 rules per account
-
Business Plus (and legacy Business) Accounts: Up to 2,000 rules
-
Enterprise Standard (and legacy Enterprise) Accounts: Up to 3,000 rules
-
Enterprise Pinnacle Accounts: Up to 4,000 rules
Note
Automation rules for custom item types also count toward your account's rule limit.
Monthly Action Limits
-
Team Accounts: 50 actions per paid seat per month.
-
Business Plus (and legacy Business) Accounts: 200 actions per paid seat per month.
-
Enterprise Standard (and legacy Enterprise) Accounts: 1,000 actions per paid seat per month.
-
Enterprise Pinnacle Accounts: 1,500 actions per paid seat per month.
When you reach the limit, all rules will be disabled automatically. Wrike will notify all account admins by email, and we'll also send alerts when your account hits 50% and 10% of the monthly action limit.
Action Rate Limits
-
If a rule performs more than 200 actions per minute, it'll be disabled automatically.
-
If a rule performs more than 100 actions per minute for five consecutive minutes, it'll be disabled.
In both cases, the rule creator or the current owner will receive a notification.
Rule Configuration
Automation Bot
-
Actions executed via Automation appear in the task/project stream with the Automation Bot as the author. This also applies to the Activity Report.
Trigger Conditions
-
If you have an Account-level automation and a Space-level automation rule with the same set of triggers and conditions, they will be triggered independently and perform the relevant actions.
-
Active automation rules won't trigger for tasks, projects, or custom items initially created through API, mass actions, or Excel import.
-
Rules won't trigger if changes are made by automatic task rescheduling. Date triggers won't work on items created from blueprints if rescheduling has been applied.
-
If you manually change these items or edit existing active rules, the rules will trigger.
-
New or enabled automation rules will trigger for items created via API, mass actions, or Excel import.
Additional Notes
-
Rules won’t trigger if more than 29 items (tasks, projects, or custom items) are edited via mass actions.
-
Rules won't trigger if changes are made by another automation rule.
-
If a rule stops working because its original settings are no longer valid (e.g., a task status is deleted), Wrike will disable the rule and notify you by email.
-
Rules are not triggered by changes that occurred before the rule was created or enabled.