Teamwork's Board view supports column-based automation rules: when a task is moved into a given column, Teamwork can automatically change its status, reassign it, add a tag, or trigger a notification, without a separate automation product. This is scoped per board rather than being a cross-project rule engine, so a 'move to Done' automation set up on one project's board doesn't apply anywhere else unless configured again.
Beyond Board automations, Teamwork also supports recurring tasks on a schedule and task templates that pre-populate a task list with a standard set of tasks and owners, which is the more common way agencies standardize a repeatable process like client onboarding rather than relying on triggers alone.
- Set up Board automations per project deliberately -- they don't propagate across projects, so a template project's automations need to be recreated, or the project cloned, for new client work
- Use task list templates for repeatable multi-step processes like onboarding, rather than trying to chain several Board automations to simulate one
- Test recurring task schedules after any project date changes, since shifting a project's timeline doesn't automatically reschedule already-created recurring instances
Use cases
Automation use cases in Teamwork
- Auto assign tasks when a new issue is created in Teamwork
- Auto move task status based on progress in Teamwork
- Notify stakeholders when milestones approach in Teamwork
- Generate weekly status reports from Teamwork data
- Enforce naming conventions and permissions in Teamwork