Within Teamwork.com, you can create
automations to help streamline your processes
in creating and managing tasks.
The automations feature provides
a
variety of trigger options you can
use as the
basis for your automations to
initiate certain
actions. Automations can also have
multiple
levels of criteria by setting
additional
conditions to the trigger.
Automation flow
Trigger
event >
Additional
condition(s)
(optional) >
Action
event
When
this happens >
and
these
conditions are
true > perform
this
action
Examples
Trigger (when
this
happens) | Condition(s) (and these conditions are true) | (perform
this
action) |
|---|---|---|
| Task's
start
date
arrives | Task
priority
is set to
high | Notify
task
assignees |
| Task is
completed | none
set | Move task
to Done column |
| Task's due
date
arrives | Task
progress
is set to
90% | Add
comment |
Supported triggers
For each automation, you can
choose
to apply it to one, multiple, or all
projects. Certain triggers have
additional options to set refined
criteria.
Note: Automations do
not run on private tasks.
| Trigger | Trigger options |
|---|---|
| Every day | Choose a day of the week and time. |
| Task added (any or via forms) | Project(s) to apply the
trigger
to. |
| Task completed | Project(s) to apply the
trigger
to. |
| Board column changes (task moves
to a specific column) | Project to apply the trigger
to. Board column in the
selected project. Note: Only one
project can be selected when
using the board column
trigger. |
| Task inactive | Task is inactive for X number
of days or weeks. Project(s) to apply
the trigger to. |
| Due date arrives | At a specific time
on the due date or At a specific time a custom # days/weeks before or after the task's due date. Project(s) to apply
the trigger to. |
| Start date
arrives | At a specific time
on the start
date or At a specific time a custom # days/weeks before or after the task's start date Project(s) to
apply the trigger
to. |
| Due date changes | Project(s) to apply the
trigger
to. |
| Start date
changes | Project(s) to apply the
trigger
to. |
| Task name changes | Any change to the name or Change contains one
or multiple specified text
terms. Project(s) to apply
the trigger to. |
| Task description changes | Any change to the
description or Change contains one or multiple specified text terms. Project(s) to apply
the trigger to. |
| Tag added (to a
task) | Tags: Select one or
multiple tags. Project(s) to apply
the trigger
to. |
| Tag removed (from a
task) | Tags: Select one or
multiple
tags. Project(s)
to apply the trigger to. |
| Custom field changes | Choose a custom field and corresponding value. Project(s)
to apply the trigger to. |
| Estimated time
exceeds | Hours & Minutes:
Set a
duration as the trigger
point. Project(s) to apply
the trigger to. |
| Logged time / estimated
time | Task's logged time exceeds
task's
estimated by a
custom
duration or Reaches
a custom % of the task's
estimated
time Projects(s) to
apply the trigger
to. |
| Time logged (to a task) | Project(s) to apply
the
trigger
to. Check
the Billable checkbox
to only trigger the automation
when billable time is logged
against a task. |
| Assignee added (to a
task) | Assignee: Select one
or multiple
assignees or leave
blank. Projects(s) to
apply the trigger
to. |
| Assignee removed (from a
task) | Assignee: Select one
or multiple
assignees or leave
blank. Project(s) to
apply the trigger
to. |
| Progress exceeds | Progress: Set a % as
the trigger
point. Project(s) to
apply the trigger
to. |
| Comment added | Author - select one or
multiple possible
authors. Project(s) to apply the
trigger to. Note: When using
the comment added trigger, it
is not possible to set
additional trigger
conditions. |
| Priority changes | From: any | none |
low | medium |
high To: any | none | low
|medium |
high |
For more information, see: Automations -
Supported Conditions