Fresh terminology for automation rules and components

An automation ‘rule’ is now a ‘flow', and a ‘component’ is now a 'step’. You may notice some inconsistencies in the documentation while we make this change. Read more about the updates in Automation

What are automation flows?

This page includes features in the Rovo Studio experience, which is currently in open beta.
If you don’t see Studio beta in your site yet, your admin may not have opted in.

Read more about Studio beta

An automation flow is a repeatable workflow that tells an app or an agent what to do when a triggering event occurs. Instead of manually performing the same tasks over and over, you define the pattern once as a flow, and the system “listens” for the appropriate moment to perform the task for you.

In simple terms, an automation flow is an “If this happens, then do that” instruction:

  • When a specific event occurs

  • If certain conditions are met (optional)

  • Then automatically perform one or more actions

Flows are especially helpful for repetitive tasks like assigning work items or sending notifications.

Automation flows can help your team:

  • Reduce manual updates and handoffs

  • Keep information in sync

  • Make sure important work is never missed

Parts of an automation flow

Automation flows are made up of three parts: triggers that kick off the flowconditions (if needed) that tell the app or agent to look for specific circumstances, and actions that are the tasks to be performed.

For example, if you want to make sure urgent work is never missed, you could create the following automation flow:

  • Trigger: When a new work item is created

  • Condition: and the work item Priority is “Critical”

  • Action: Slack the team lead

The automation trigger = work item created. The condition = Priority 1. The action = Slack the person with this email address

This way, every urgent work item is instantly surfaced to the right person without anyone needing to manually do anything.

If you wanted, you could even branch the flow so it performs different actions for different work item Priorities.

For example:

Trigger: When a new work item is created

Condition 1

If the work item Priority is “Critical”

Condition 2

If the work item Priority is “Major”

Condition 3

If the work item Priority is “Minor”

Action 1

Slack the team lead

Action 2

Slack the team Channel

Action 3

Add a comment to the work item that mentions <this person>

 

You can create your own automation flow in Studio by describing it to Rovo as a prompt (what you want it do and when), or by configuring the specific trigger, conditions, and actions from scratch.

Still need help?

The Atlassian Community is here for you.