Automate Workflows

Setting Up Basic Automations

Build Automations that watch for a trigger, check optional conditions, and run one or more actions: the full catalogue of triggers, conditions, and actions, plus worked recipes.

An Automation is a rule: when something happens, and only if some conditions hold, then do one or more things. Use one whenever you find yourself making the same change by hand after the same event: routing new items to a team, closing out child work when a story completes, nudging a customer who hasn't replied, or tidying a board after work is done.

Automations live on the Automate Workflows page, under Admin in the sidebar. You need the Automations module and the Create Automation permission to add one; editing or deleting someone else's rule needs Manage All Automations (see Roles & Permissions).

Create an Automation

  1. Click + Automation at the top right. The Add Automation dialog opens.
  2. Give it a Description (this is its name in the list) and pick an Automation Group. Rules with no group land in Other; create your own groups with + Group to keep a long list readable.
  3. Under 1. When this happens..., choose a Trigger and fill in its fields.
  4. Optionally click Add Condition to add And only if cards that narrow when the rule fires. Up to 10 conditions per trigger.
  5. Under 2. Then do this:, choose an action and fill in its fields. Click Add Action to chain more; they run in order, joined by And Then.
  6. Click Create (Update when editing). New rules start Enabled.

Each row in the list has an Enabled/Disabled toggle, Run history, Duplicate, Edit, and Delete. Use Duplicate to clone a working rule and change one thing rather than rebuilding it.

Triggers

Triggers are grouped in the selector exactly as below. Several groups appear only when the matching feature is set up: Service Desk needs the desk enabled, Github needs a connected repository. Knowledge Base appears only to people who hold Manage All Kb Articles.

Time Based

TriggerWhat you setFires
Every Time PeriodFrequency (Daily, Weekly, Monthly), Every n periods, Weekdays (weekly) or Dates (monthly), and the hour of dayOn the schedule. Takes no conditions; pair it with actions such as Create Work Item or Send Notification.
Item Stays Done on BoardSource board and Time spent Done on this board in Hours or DaysOnce an item has sat in a Done status on that board for the delay. Checked hourly. See the recipe below.
Due Date ArrivedTime of Day, and either On the Due Date or n days/weeks/months before or after itOnce per item when the chosen moment arrives.

Work Item

Work Item Created, Work Item Deleted, Subtask Created, and one trigger per field change: Item Type Changed, Item Parent Changed, Item Color Changed, Status Changed, Priority Changed, Team Updated, Assignee Updated, Persona Updated, Point Effort Updated, Time Estimate Updated, Cycle/Board Updated, Custom Field Updated, Tags Updated, Due Date Changed, Time Spent Updated.

Each field-change trigger lets you restrict the change, for example Status Changed has From Statuses and To Statuses (default Any Status), and Tags Updated has From any of and To any of. Leave them open to react to every change of that field.

Workstream

Workstream Created, Workstream Deleted, Workstream Parent Changed, Workstream Color Changed.

Item Request

Item Request Submitted: fires when someone submits an item request form. Under For any of, choose the forms it watches, or leave Any Item Request. Takes no conditions; the request's answers and the item it created are available to the actions.

Service Desk

TriggerFires
Customer RepliedA requester posts a public reply on a ticket.
Channel Message SuspendedAn inbound channel message was held. No ticket exists yet, so only Send Notification and Call Webhook are offered.
SLA At Risk / SLA BreachedA ticket's SLA target is approaching or missed.
Customer Marked SolvedA requester marks their ticket solved from the portal.
Client Approved Review / Client Requested ChangesA client decides a client review of a work item in their portal. Conditions work as for Customer Marked Solved; the routing company is the one the review was sent to. Send Customer Reply is not offered on these triggers.
Ticket Time SweepHourly, for every open ticket matching your elapsed-time conditions. Needs at least one condition. See Time-Based Ticket Automations.

Knowledge Base

TriggerWhat you setFires
Spec Reached a StageWhen a spec reaches: one of your spec stages, or Any stageA Knowledge Base article is moved into that stage, in the editor, by the AI Assistant or through the API. Clearing an article's stage never fires it. Only Create Work Item, Send Notification and Call Webhook are offered, because the trigger hands over a spec, not a work item.

Saving a Spec Reached a Stage automation switched on needs Manage All Kb Articles, because it runs for every spec in the workspace, drafts included; a save that switches it off is always allowed. Its Create Work Item action has a Link the new item to the spec switch, on by default, that links each created item to the spec. See Specs and work items.

Github

Pull Request Opened, Branch Created, Commit Created, All Checks Passed, Check Failed, Review Requested, Changes Requested, All Reviews Approved, All Pull Requests Merged/Closed. Each fires on the work item the GitHub activity is linked to.

Conditions

Conditions appear as And only if cards inside the trigger column. A rule with several conditions fires only when all of them match. Which fields are offered depends on the trigger:

Trigger familyCondition fields
Work Item, Time Based (Item Stays Done on Board, Due Date Arrived), Service Desk ticket triggers, GithubDirect Parent, Parent Hierarchy, Color, Item Type, Priority, Author, Tags, Time Estimate, Effort Points, Status, Team, Board, Cycle, Assignee, Persona, Custom Field, Due Date, Time Spent. With Service Desk enabled, also Channel, Requester, Company, Customer Importance, Customer Status, Closed Status Mapping, and SLA Due.
Subtask CreatedSubtask Assignee, Subtask Team, Parent Item Assignee, Parent Item Team
Ticket Time SweepThe list above plus Hours Since Created, Hours Since Status Changed, Hours Since Staff Reply, Hours Since Customer Reply
WorkstreamDirect Parent, Parent Hierarchy, Color
Spec Reached a StageSpec Publish State (is equal to / is not equal to), Spec Work Items (already exist / do not exist yet)
Every Time Period, Item Request Submitted, Channel Message Suspendednone

Operators follow the field: is equal to / is not equal to for choices; contains / does not contain for Tags and Parent Hierarchy; is set / is not set for optional fields such as Assignee, Team, Board, and Due Date; numeric comparisons for Time Estimate, Effort Points, Time Spent, Due Date, and SLA Due; Cycle offers is a current cycle, is a future cycle, is a past cycle, and is not set; the Hours Since fields take is at least / is less than with a number of Calendar hours or Business hours.

Actions

Actions are grouped in the selector as below. Not every action is offered under every trigger: an action that changes an item needs a trigger that supplies one.

GroupActionsAvailable under
MessagingSend Notification (to a person, team, or channel such as Slack or Microsoft Teams)Every trigger
Send Customer Reply (a public reply on the ticket; needs the Send Public Replies permission)Service Desk ticket triggers and Ticket Time Sweep
IntegrationsCall Webhook (one request shaped by this rule; to mirror every change into another system, use Webhooks instead)Every trigger
Work ItemCreate Work ItemEvery trigger. Under Spec Reached a Stage it can also link the new item to the spec
Create SubtaskEvery trigger except Spec Reached a Stage
Apply Template (creates an item template's items and subtasks under the triggering item, or under one item you choose; must be the last action)Work Item Created and Item Request Submitted
Change Subtask Assignee, Change Subtask Status, Set Subtask Due DateSubtask Created only
Archive ItemWork Item Created, every field-change trigger, Due Date Arrived, Item Stays Done on Board, and the Service Desk ticket triggers (not Work Item Deleted or Subtask Created)
Complete Child Items or SubtasksThe field-change triggers (Status Changed and the other "Updated/Changed" triggers) and the Github triggers
Change Item Parent, Change Item Color, Change Status, Change Item Type, Change Priority, Change Team, Change Assignee, Change Persona, Change Point Effort, Change Time Estimate, Change Cycle/Board, Change Custom Field, Add Tags, Remove Tags, Set Due Date, Change Time SpentWork Item Created, every field-change trigger, the Github triggers, Due Date Arrived, Item Stays Done on Board, and the Service Desk ticket triggers (not Work Item Deleted)
WorkstreamCreate WorkstreamEvery trigger except Spec Reached a Stage
Change Workstream Parent, Change Workstream ColorWorkstream Created and the Workstream Changed triggers
RelationshipsCreate RelationshipsEvery trigger except Spec Reached a Stage

Under the Subtask Created trigger only the three subtask actions, Send Notification, and Call Webhook are offered.

Under Work Item Created, Create Work Item creates a full item, for example a Task for each step of a new-hire Request. Give the rule an Item Type condition that excludes the type it creates (Request in, Task out); without one, every created item would start the rule again, and the builder refuses to save it. While you build a rule whose actions can start other automations, the builder reminds you of the automation chain limit.

Use values from the triggering item

Most action fields accept either a fixed value or a reference. Flip the reference toggle on a field to pick from the triggering item: Item Parent, Item Type, Item Priority, Item Color, Item Team, Item Assignee, Item Persona, Parent Item Assignee, Parent Item Team, Item Author, Item Cycle/Board, Item Status, Item Due Date, Item Start Date, Item Tags (workstream triggers offer the workstream equivalents). This is how "assign the new item to its parent's assignee" or "give the subtask the parent's team" is expressed.

Notifications and webhooks can also embed item fields (title, number, status, assignee, custom fields, and so on) as text. Under Spec Reached a Stage there is no item; they can embed the spec's Spec Title, Spec Stage, Spec Previous Stage and Spec Id instead.

Tags

The same tag selector appears wherever tags are involved: From any of / To any of on Tags Updated, Any of these tags on the Tags condition, and Tags to Add / Tags to Remove on the actions.

Recipes

Route new work to a team

  1. Trigger: Work Item → Work Item Created.
  2. Condition: Parent Hierarchy contains Product.
  3. Action: Change Team → Product.

Every item created anywhere under the Product workstream is handed to the Product team. Add Change Assignee with the reference Parent Item Assignee to also hand it to whoever owns the parent.

Apply a template to new requests

To build a standard set of work, such as an onboarding checklist, under every item a request form creates:

  1. Trigger: Item Request → Item Request Submitted. Under For any of, choose the form, for example New Hire. The template goes under the item the submission created.
  2. Action: Apply Template. Leave Apply under on The item that set this automation off, or flip the reference toggle to pick one specific workstream or item.
  3. Choose the template. The note beneath the picker says which item types it can go under. A template that starts with a workstream is refused, because an automation always applies under a work item.
  4. Under Template values, give each of the template's variables a fixed value, or flip its toggle to take it from the triggering item: a form answer, its assignee, a date. People, team, date and text variables take a reference; choice, number and board variables take a fixed value only.
  5. Save and enable the automation.

To apply a template to items created any other way, use Work Item → Work Item Created with conditions instead, for example Item Type is Request and Custom Field Request Type is New Hire. The Item Type condition must rule out every type the template creates; otherwise the created items would start the rule again, and the builder refuses to save it.

Apply Template must be the last action: the template's items are created after the automation finishes, so no later action can use them, and the builder offers no Add Action after it. In Run history the run reads Applying template… until the items exist, then says how many were created, or why the apply was refused. The created items are credited to the automation's creator, who must be able to open the template. A template an automation uses cannot be deleted until the action is removed; the message names the automation.

A template that reads Needs review still applies. No one is there to choose, so each run applies it and leaves off the values your organization no longer allows, such as a member who left or a tag taken off the item type. The run's history line ends with Left off because this organization no longer allows them: and names each one, and the action shows the same note under the template you picked. Fix the template in the builder to stop the note. A Broken template is refused, and the automation stays on.

Complete a Story's child work

To complete QA work when its Story is completed:

  1. Choose Status Changed as the trigger. Leave the previous status unrestricted and select your completed status, such as Complete, as the new status.
  2. Add an Item Type condition matching Story.
  3. Choose Complete Child Items or Subtasks as the action.
  4. Select Child items and subtasks, Child items only, or Subtasks only, then save the automation.

The action completes work directly under the triggering item. Child items move to the Done status available on their own board or team. Already-completed work and archived child items are left alone. The action itself does not complete deeper descendants or the Story's parent project.

Child status changes can trigger matching automations. The Story condition keeps this recipe from matching QA Task children. If a child is also a Story, it can match and start another run. Each action invocation completes direct children only.

This action works with Automate New/Done switched off. That organization setting controls separate upward completion; if you leave it enabled, its parent-completion behavior still applies. Leave it off when maintenance projects should stay open while this automation completes their Stories' QA work.

An action supports up to 100 selected direct child items and subtasks combined, including completed entries; archived child items do not count. A larger selection fails before changing any selected work, and the automation remains enabled.

If a child's status configuration is unavailable, the action also leaves its selected work unchanged and records a failed run. The automation stays enabled for future triggers. Check Run history for the reason.

Give new subtasks their parent's assignee

To have every new subtask start with the person who owns its parent item:

  1. Choose Work Item → Subtask Created as the trigger.
  2. Optionally add conditions, such as Subtask Assignee is not set so subtasks someone already assigned are left alone, or Parent Item Team to limit the rule to one team.
  3. Choose Change Subtask Assignee as the action. Use the parent item's assignee is selected by default; leave it on.
  4. Save and enable the automation.

When someone adds a subtask, it takes whoever the parent item is assigned to. A parent with no assignee leaves the subtask unchanged. To assign a specific person instead, clear Use the parent item's assignee and choose them; if that person is not on the parent item's team, the action does not run.

The same trigger can also set a new subtask's status with Change Subtask Status (New, In Progress, or Done), or give it a due date a number of days after it is created with Set Subtask Due Date (0 means the same day).

Remove completed work from a board after a delay

To keep a perpetual board focused on current work, or to tidy finished work away entirely:

  1. Choose Time Based → Item Stays Done on Board as the trigger.
  2. Select the Source board and enter Time spent Done on this board in Hours or Days, such as seven days.
  3. Choose Change Cycle/Board as the action, then Remove Cycle/Board. To move the item elsewhere instead, choose Set to Cycle/Board and the destination. To archive it instead, choose Archive Item.
  4. Save and enable the automation.

The rule is checked hourly, so removal happens on a check after the chosen delay, not at an exact minute. It runs once per qualifying stretch in Done. Only items completed after the automation is enabled qualify; existing Done items are not swept up retroactively. Reopening an item or changing its board starts a new waiting period. Re-enabling the rule or changing its source, delay, or conditions starts fresh.

Archive Item archives the item and everything under it, keeping its history; unarchive it from its workstream if you need it back. "Archive tickets a week after they close" is this recipe with Archive Item as the action and seven days as the delay.

Removing board placement does not delete the item or its history; you can still find it in its workstream. For removing an archived board or folder itself, see permanent board and folder deletion.

Nudge a customer who has gone quiet

  1. Trigger: Service Desk → Ticket Time Sweep.
  2. Conditions: Hours Since Staff Reply is at least 48 Business hours, and Customer Status is equal to Open.
  3. Action: Send Customer Reply with your follow-up text.

The sweep runs hourly over open tickets; the conditions make it fire once a ticket has waited two business days on the customer. Full guide, including auto-closing solved tickets: Time-Based Ticket Automations.

Work with personas in Automations

Use Persona Updated to react when an item's chosen persona changes, Persona conditions to narrow the rule, and Change Persona to assign the required kind of work. Persona values can also be used in supported automation references.

These changes follow the same assignment rules as the chooser: selecting a persona preserves a compatible person and clears an incompatible one. Clearing the persona while keeping a person with personas applies that person's first active persona. Personas grant no extra permissions to the automation or to members. See Personas.

Monitor runs

Click Run history on a rule to open Automation Runs: one row per run with Run Date, Status, and Actions Executed. Each run ends in one of three states:

  • Completed: the actions ran. A run can still carry a Note, for example when one of several actions had nothing to do.
  • Skipped: nothing could be done, and the Reason says why in plain words. A Change Cycle/Board action that points at a cycle with no board (say current cycle + 6 when only five cycles are scheduled) is skipped rather than reported as a success, and the reason names the board folder and the cycle. The item stays where it was.
  • Failed: an action hit an Error; the message tells you which one. An Apply Template that was refused (the template is broken or no longer fits, or needs a variable the rule does not fill) fails this way; the automation stays on. A template that only holds values your organization no longer allows is not refused: the run leaves them off and names them.

Skipped and failed runs still count toward your plan's monthly automation actions. When the month's allowance is used up, further runs fail with "Monthly automation action limit reached"; usage resets at the start of the next calendar month, and upgrading the plan raises the limit.

Automation chain limit

When an automation's action creates or changes something that starts another automation, or the same one again, the runs form a chain. A chain stops after 25 automations in a row: the run that would go further is marked Failed with "Automation chain limit reached", executes no actions, and the automation stays switched on, so its next run started by a person works normally. In Automation Runs, a run stopped this way shows an Automation chain limit link beside its status, leading here.

The limit counts automations triggering each other one after another, not items: a single run with many Create Work Item actions is unaffected, and so is a chain of legitimate steps such as a Done roll-up climbing a deep hierarchy. A chain that reaches the limit is almost always a rule that matches its own result; tighten its conditions as the tip above describes.

Filter the list

The Automate Workflows page has its own Filters button (by Trigger, Condition Field, Action, Status, Created By) and a search box. See Automations filters.