What we do
Tools
Industries
Department
How we workLet's talk →
Home/Wrike/Wrike Automation Rules, and What They Ignore

Wrike Automation: How Rules Fire, and the Edits They Never Notice

You set a rule to reassign a task when its status changes, and today it did nothing. Wrike automation works on rules made of one trigger, any number of conditions and up to 10 actions, on the Team plan and above. Every rule run draws on a monthly action allowance per paid seat, and some changes don't trigger rules at all, including anything an integration does through the API.

Which part of Wrike handles the step you want automated

What you want to happen Where it runs What to watch
Assign, rename, move or restatus an item when something changes A space-level or account-level automation rule A rule covers a whole space, or up to 10 folders, projects or spaces you pick. Items outside that scope are ignored.
A Slack or Teams message, an Outlook or Gmail email, a calendar event App actions inside the same rule Emails go out from a connected Microsoft 365 or Google account. Shared and collaborative inboxes aren't supported.
A checklist that comes back every month A recurring task, set on the task itself Recurrence runs on its own schedule, apart from the rule engine. Rules can still act on each copy once it exists.
Logged project hours sent to QuickBooks The Export Time Entries to QuickBooks action It works on projects only, and you sign in to QuickBooks while creating the rule.
A record in your CRM, billing tool or anything missing from Wrike's action list Custom work on the Wrike API Rules don't fire on API changes, so the integration has to carry out its own follow-on steps.

Changes your Wrike rules never react to

Wrike lists these in its help center. Each one looks like a broken rule until you know it's by design.

The change came from an integration

How you'll know: Tasks created or edited by Zapier, a sync or your own script never get assigned or moved.

Fix: Rules don't trigger on items created or changed through the API. Have the integration set the field itself, or do the follow-on step it was waiting for.

Someone edited a long list at once

How you'll know: A status change applied to 40 tasks in one go moved none of them.

Fix: Mass edits of more than 29 items skip rules. Edit in smaller groups, or let a script apply the follow-on change.

One rule was meant to set off another

How you'll know: Rule A changes the status, and rule B, which waits on that status, never runs.

Fix: Changes made by a rule don't trigger other rules, apart from the Direct Subitem Statuses Change To and All Predecessor Statuses Change To triggers. Put both actions in one rule where you can.

The month's allowance ran out

How you'll know: Every rule stopped working on the same day, partway through the month.

Fix: Reaching the action limit disables all rules. Admins get warnings at 50% and 10% remaining, so trim rules that fire on every small edit, or move the busiest step off the rule engine.

The items came from a spreadsheet

How you'll know: Tasks imported from Excel arrived without the assignee a rule should have given them.

Fix: Excel imports don't trigger rules either. Put the value in the sheet before importing, or apply it afterwards in groups of 29 or fewer.

One Wrike rule, set up and tested

  1. 1

    Decide where the rule lives

    Space admins create rules in their space's settings, and account owners and admins create account-level ones. Point it at the whole space or at up to 10 folders and projects.

  2. 2

    Choose its one trigger

    Options include Status Changes To, New Item Created, Approver Gives a Decision, Custom Field Changes and When Due Date Changes.

    Watch for: the two time-based triggers, Status Doesn't Change In and Date is Approaching or Overdue. They run just after midnight, not at the moment the date passes.

  3. 3

    Limit it with conditions

    Conditions are checked only after the trigger fires. Use them to limit the rule to a status, an importance level, a billing type or a custom field value. There's no cap on how many you add.

  4. 4

    Add up to 10 actions

    Actions can change the item, create subitems from a blueprint, add a comment or mention, or reach Slack, Teams, Outlook, Gmail and QuickBooks. Each one that runs counts toward the month's allowance.

  5. 5

    Test it with one hand edit

    Change a single item yourself and look for Automation Bot in its activity stream. A bulk edit is a poor test, since edits over 29 items won't trigger the rule at all.

Wrike rule questions

What triggers can Wrike's automation engine use?

Status changes, a status that hasn't changed in a set time, a new item, a date approaching or overdue, a location change, approvals starting, getting a decision or finishing, and changes to an assignee, custom field, start or due date, completed date, duration, importance, name, description or billing type. Two more fire when every direct subitem or every predecessor reaches a status.

Is the automation engine included on every Wrike plan?

Not on the Free plan. Team, Business, Pinnacle and Apex do, with monthly allowances of 50, 200, 1,500 and 3,000 actions per paid seat. Legacy Business and Legacy Enterprise plans have it too.

Can a Wrike automation rule email someone outside my team?

A rule can send email through the Send Outlook Email or Send Google Email action, which sends from a connected Microsoft 365 or Google account rather than as a Wrike notification. Wrike's help article doesn't spell out limits on recipients, so send a test to an outside address before you rely on it.

Does Wrike support recurring tasks?

Yes. Recurrence is set on the task, and Wrike creates the next copy on the schedule you choose. It's separate from automation rules, though a rule can act on each copy once it exists, for instance when its due date gets close.

Who builds the steps a Wrike rule can't reach?

That's the work n-frames takes on, on the Wrike API: the CRM or billing update after an approval, the follow-on for tasks a sync creates, and busy steps moved off the rule engine so the allowance holds out.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.