All articles

Available Automation Triggers

Table 95. Availability

Free

Professional

Business

Enterprise


Overview

Automation triggers are an essential part of automation rules. They're the “IF …” statements that define when exactly the automation rule should be triggered. Each rule can have one trigger.

Note

The list of available automation triggers that you see in the rule constructor changes depending on whether your rule applies to tasks or projects. See the “Can be applied to” column in the table below to check if a trigger is available for task- or project-based rules.

Available automation triggers

Task/project status changes to

You can apply this trigger to tasks and projects.

Description

Additional required settings

Notes

It triggers the rule whenever a task or project status changes to a status(es) that you define.

E.g., "If project status changes to Completed or Cancelled, then ..."

Select at least one status group (e.g., Any completed). In this case, the rule is triggered by statuses included in this group in any workflow

Or click Select specific statuses to choose at least one specific status that will trigger the rule.

If at least one of the selected specific workflow statuses is deleted from the account, the rule will be disabled.

Task/project status doesn’t change in

You can apply this trigger to tasks and projects.

Description

Additional required settings

Notes

It triggers the rule when a task or project spends too much time in the same status(es) that you define. Countdown restarts each time the status changes to a new one.

E.g., "If task status doesn’t change in 5 days from In progress, then ..."

Set the number of calendar days during which the status should stay the same for the rule to be triggered.

Next, select at least one status group (e.g., Any active). In this case, the rule is triggered by statuses included in this group in any workflow

Or click Select specific statuses to choose at least one specific status that will trigger the rule.

If you create a rule with this trigger, it won't be applied to tasks or projects retrospectively. Meaning that the rule won't be triggered if the status of a task hadn't been changed for the defined number of days before you created the rule.

E.g., the trigger was set to 5 days, and if a task had already had the same status for five days before the rule was created, it wouldn't be triggered. But if the task had the same status for three days, and then you created the rule, it'll be triggered in two days.

New task/project is created

You can apply this trigger to tasks and projects.

Description

Additional required settings

Notes

It triggers the rule when a new task or project is created in the source location(s) you select in the Apply to section of the rule constructor.

E.g., "If new task is created (in the selected location), then ..."

-

The rule dependent on this trigger won’t work if tasks and projects are created via Excel import, API, or duplication.

The rule dependent on this trigger also won’t work in case tasks and projects are created via request forms or blueprints, which are set up to create 100 or more work items at a time.

All predecessor statuses change to

You can apply this trigger to tasks.

Description

Additional required settings

Notes

It triggers the rule when all predecessors of tasks change their status to the status(es) you define.

Task predecessors are a part of the Gantt chart. You can read more about them here.

E.g., "If all task's predecessor statuses change to Completed, then ..."

Select at least one status group (e.g., Any completed). In this case, the rule is triggered by statuses included in this group in any workflow.

Or click Select specific statuses to choose at least one specific status that will trigger the rule.

The trigger only checks direct predecessors.

Wrike checks if the conditions of this trigger are true every five minutes. So, once all the predecessors of a particular task get the relevant status, it might take up to five minutes for the rule to be triggered.

If at least one of the selected specific workflow statuses is deleted from the account, the rule will be disabled.

All direct subtask statuses change to

You can apply this trigger to tasks.

Description

Additional required settings

Notes

It triggers the rule when all subtasks of a task get the status(es) that you define.

E.g., "If all direct subtask statuses change to Completed, then ..."

Select at least one status group (e.g., Any completed). In this case, the rule is triggered by statuses included in this group in any workflow

Or click Select specific statuses to choose at least one specific status that will trigger the rule.

Wrike checks if the conditions of this trigger are true every five minutes. So, once all the subtasks of a particular task get the relevant status, it might take up to five minutes for the rule to be triggered.

If at least one of the selected specific workflow statuses is deleted from the account, the rule will be disabled.

All subproject or task statuses change to

You can apply this trigger to projects.

Description

Additional required settings

Notes

It triggers the rule when all tasks within a project and its subprojects get the status(es) that you define.

E.g., "If all direct subproject and task statuses change to Cancelled, then ..."

Select at least one status group (e.g., Any cancelled). In this case, the rule is triggered by statuses included in this group in any workflow

Or click Select specific statuses to choose at least one specific status that will trigger the rule.

Wrike checks if the conditions of this trigger are true every five minutes. So, once all the subtasks of a particular task get the relevant status, it might take up to five minutes for the rule to be triggered.

If at least one of the selected specific workflow statuses is deleted from the account, the rule will be disabled.

Project is at risk (AI-based)

You can apply this trigger to projects.

Description

Additional required settings

Notes

It triggers the rule when a project's risk level changes.

E.g., "If project risk level changes to high, then ..."

Select the change in the risk level that should trigger the rule: if it rises or lowers. Or choose the exact risk level: low, medium, or high.

This trigger will work only for projects that:

  • Have a start date and end date

  • Have content (subproject, tasks, etc.)

  • Aren’t in completed status

  • Aren’t two or more weeks overdue.

Custom field changes

You can apply this trigger to tasks and projects.

Description

Additional required settings

Notes

It triggers the rule when a value in a custom field changes.

E.g., "If custom field Urgency changes to any value, then ..."

Select the custom field.

For dropdown fields, select if the rule should be triggered by any value change or by a change to a specific value.

For checkbox fields, select if the rule should be triggered when it changes to any value or specifically to checked or unchecked.

The trigger only works for dropdown and checkbox custom fields that are added to the project, folder, or space that you select in the Apply to section of the rule constructor.

Top