Board Automation

Board Automations let you create simple rules that update tasks or create new ones automatically. They are configured per board and are useful for things like auto-assigning bugs, setting deadlines when status changes, or creating recurring tasks.

You can create as many automations as you need for each board.

• Access Board Automation Settings
• Automation Types
• Create A New Automation
• Task-Based Automations (Task Created / Updated)
  • Configure Task Conditions
  • Update Task Properties
• Schedule Automations (Recurring Tasks)
  • Configure The Schedule
  • Create The Recurring Task
• Enable, Duplicate, And Delete Automations

#Access Board Automation Settings

1. Open the board where you want to configure automations.
2. Click the Board Settings button in the top-right corner.
3. Go to the Automation tab.

If there are no automations yet, you will see an empty state with a + Add Automation button.

#Automation Types

Each automation has:

• A Name - used to describe what the rule does (e.g. "Bug", "Assign Reviewer", "Monthly Client Report").
• A Trigger - when the automation should run.
• A Scope - which board or project the rule applies to.
• Optional Conditions - filters to limit which tasks are affected.
• One or more Actions - what should happen when the rule is triggered.

There are two trigger types:

1. Task Created / Updated Runs when a task is created or when its properties change (status, tags, assigned user, etc).

2. Schedule Runs on a defined schedule (for example, every month on the 1st at 11:00 AM) and is typically used to create recurring tasks.

#Create A New Automation

1. Go to Board Settings → Automation.

2. Click + Add Automation.

3. Enter a Name for the automation (for example, "Bug" or "Assign Reviewer").

4. Use the switch in the top-right corner of the card to enable or disable the automation.

5. Choose the Trigger:

   • Task Created / Updated, or
   • Schedule.

6. Set the Scope:

   • Board - rule applies to all projects on the board.
   • Or pick a specific Project to apply the rule only there.

7. Configure Conditions (optional).

8. Configure Actions - either updating an existing task or creating a new one (depends on the trigger type).

9. Click outside of the fields or close Board Settings - changes are saved automatically.

#Task-Based Automations (Task Created / Updated)

Use the Task Created / Updated trigger to react to changes on tasks, for example:

• Auto-assign tasks with specific tags.
• Set deadlines when the status changes.
• Change priority when a task is moved to a review column.

#Configure Task Conditions

Under CONDITION, click + Add Condition to add filters. Each condition row consists of:

• Field - what you want to check:

  • Status
  • Tags
  • Assigned
  • Priority
  • Custom properties (Board Properties)

• Operator - how the field should be matched (for example, "any of" for lists).

• Value - specific statuses, tags, users, etc.

Examples:

• Status - any of - Review Only tasks whose status is "Review" will match.

• Tags - any of - Bug Tasks that contain the "Bug" tag will match.

You can add multiple conditions. All conditions must match for the automation to run on a task.

#Update Task Properties

Under UPDATE TASK, click + Add Property to define what should change when the rule runs.

Available actions include:

• Assigned - assign the task to a specific user.
• Priority - set the priority level (for example, High).
• Status - move the task to a different status/column.
• Tags - add or adjust tags on the task.
• Start Date - set a start date, often relative to when the rule runs.
• Deadline - set or shift the due date.
• Custom Properties - set or adjust custom properties on the task.

For date fields you can use relative values, such as:

• Start Date - 0 - Days after (start today)
• Deadline - 3 - Days after (due 3 days after the rule runs)

This is useful for automations such as:

• When a task moves to Review, assign a reviewer and set deadline to 3 days after.
• When a task is tagged Bug, assign it to a specific developer and set priority to High.

#Schedule Automations (Recurring Tasks)

Use the Schedule trigger when you want t0ggles to create tasks on a recurring basis.

#Configure The Schedule

When Trigger = Schedule, you will see:

• Project scope at the top - choose which project the recurring tasks should be created in.

• A CONDITION block with:

  • Frequency: Every Month, Every Week, Every Day.
  • Day selector (for example, "on 1st").
  • Time selector (for example, "at 11:00 AM").

Example:

• Every Month - on 1st - at 11:00 AM

This will run the automation once per month at the specified time.

#Create The Recurring Task

Below the schedule, you can configure the task that will be created:

• CREATE TASK

  • Title (for example, "Monthly Report" or "Monthly Client Report").
  • Initial Status (for example, "To-Do").

• TASK PROPERTIES (via + Add Property):

  • Tags (for example, "Reporting").
  • Start Date (relative, for example 0 days after).
  • Deadline (relative, for example 3 days after).
  • Assigned user and other task fields, if needed.
  • Priority (for example, "High").
  • Custom Properties (Board Properties) - set or adjust custom properties on the task.

Typical use case:

• Automatically create a Monthly Client Report task in a specific project on the 1st of every month, with:

  • Tag "Reporting",
  • Start date set to the day it’s created,
  • Deadline 3 days later.

#Enable, Duplicate, And Delete Automations

Each automation card has a control area in the top-right corner:

• Toggle switch - turns the automation on or off without deleting it.
• Duplicate icon - creates a copy of the automation, useful when setting up similar rules for different projects.
• Delete icon - removes the automation from the board.

You can keep multiple automations active on the same board. When several rules match the same task, they will all run in the order defined internally by the system.

---

Board Automations give you a way to automate common workflows on each board without writing code. You can start with simple rules like auto-assigning bugs or creating monthly reports and later combine conditions and actions to support more advanced workflows as your projects grow.