Available with limits on all Teamwork.com plans. See Usage limits for more information.
Feature overview
What
Automation triggers define when an automation runs based on changes to tasks or projects.
Why
  • Reduce manual work by automating repetitive actions.
  • Ensure consistency across workflows.
  • Respond automatically to task and project updates.
Who
Users with permission to create automations. Administrators can run automations on private tasks.
When
Use automations when actions should happen automatically based on task updates, dates, or user activity.
← Swipe to scroll

Automations are made up of triggers, optional conditions, and actions. See Supported triggers, Supported conditions, and Supported actions.

Automation triggers define when an automation runs. When a trigger event occurs, optional conditions are evaluated and the configured actions run automatically.

Automation flow: Trigger → Conditions (optional) → Actions (with target selection)
When something happens, and optional criteria are met, an action is performed on the selected target.
Task-based actions can run on different related tasks depending on the selected target, such as the trigger task, parent task, subtasks, or a previously created task.

Automation examples

Trigger
Condition(s)
Action
Task's start date arrives
Task priority is high
Notify task assignees
Task is completed
None set
Move task to Done column
Task's due date arrives
Task progress is 90%
Add comment

Automation triggers

Automation triggers are grouped by the type of event they respond to, such as task lifecycle changes, dates, content updates, user activity, and time tracking.

All triggers can be scoped to one or more projects unless stated otherwise.
Automations run on private tasks if the user who created the automation is an administrator.

Task lifecycle triggers

Trigger
Trigger options
Every day
  • Select the day of the week and time.
Task added (any or via forms)
  • Select project(s).
Task completed
  • Select project(s).
Board column changes (task moves to a specific column)
  • Select a project.
  • Select the board column in that project.
  • Only one project can be selected when using the board column trigger.
Task inactive
  • Set the inactivity period in days or weeks.
  • Select project(s).

Date-based triggers

Trigger
Trigger options
Due date arrives
  • Set a specific time on the due date.
  • Or set a custom offset before or after the due date.
  • Select project(s).
Start date arrives
  • Set a specific time on the start date.
  • Or set a custom offset before or after the start date.
  • Select project(s).
Due date changes
  • Select project(s).
Start date changes
  • Select project(s).

Task content and field changes

Trigger
Trigger options
Task name changes
  • Trigger on any name change.
  • Or trigger when the change contains specific text.
  • Select project(s).
Task description changes
  • Trigger on any description change.
  • Or trigger when the change contains specific text.
  • Select project(s).
Tag added (to a task)
  • Select one or more tags.
  • Select project(s).
Tag removed (from a task)
  • Select one or more tags.
  • Select project(s).
Custom field changes
Field type-specific options. See Custom field triggers below.
Priority changes
  • Set a From value: any, none, low, medium, or high.
  • Set a To value: any, none, low, medium, or high.

Time and progress triggers

Trigger
Trigger options
Estimated time exceeds
  • Set a duration in hours and minutes.
  • Select project(s).
Logged time / estimated time
  • Trigger when logged time exceeds estimated time by a custom duration.
  • Or trigger when logged time reaches a custom percentage of the estimate.
  • Select project(s).
Time logged (to a task)
  • Select project(s).
  • Optionally limit the trigger to billable time entries only.
Progress exceeds
  • Set a progress percentage.
  • Select project(s).

People and collaboration triggers

Trigger
Trigger options
Assignee added (to a task)
  • Select one or more assignees, or leave blank.
  • Select project(s).
Assignee removed (from a task)
  • Select one or more assignees, or leave blank.
  • Select project(s).
Comment added
  • Select one or more possible authors.
  • Select project(s).

Some triggers, such as comment-based triggers, do not support additional conditions.

Custom field triggers

Custom field triggers allow automations to run based on changes to field values. Available options vary depending on the custom field type selected.

Field type
Available options
Dropdown fields
  • Value change: Trigger when the field changes from one specific value to another.
  • Flexible matching: Set either the starting or ending value to any to trigger on broader change conditions.
Date custom fields
  • Days after the trigger date: Trigger a set number of days after the field is updated.
  • On the trigger date: Trigger when the updated field date matches the date of the change.
  • A specific date: Trigger when the updated field date matches a specific date set in the automation.
  • Within a time period: Trigger when the updated field date falls within a defined future time range.
Project scope
  • Select project(s).