Automate Rovo agents

Agents can be automated to perform repetitive tasks.

Using an agent within an automation flow allows the agent to take actions directly in any apps the agent has access to, like updating work items, creating pages, or posting comments.

There are two ways to do this: add a trigger to an agent's configuration, or add the agent to an automation flow.

When agents are used in automations, they can be configured without requiring user confirmation for every action.

Think carefully about how you configure your agent and follow our recommended best practices

Admins and users can prevent agents from acting in automations.

If they do, any agent tools that perform any kind of write action will fail and you'll need to use the {{agentResponse}} smart value in automation actions for all flows.

Add a trigger to an agent

If you are an agent’s manager or editor, you can add a trigger in the agent’s configuration.

  1. Navigate to Studio from the App switcher ().

  2. Select Agents.

  3. Browse agents to find the agent you want to automate.

  4. Select the agent to open it’s settings.

  5. Select Triggers from the sidebar.

    1. Any existing flows that trigger this agent are listed, organized by app.

  6. Select Add automation trigger to configure an event that will trigger this agent.

  7. You’ll be redirected to Automations to finish configuring your flow.

  8. Save and enable your flow.

  9. Refresh your agent’s Triggers screen to see it listed.

Add an agent to an automation flow

If you are a space or app admin in Jira or Confluence, you can create an automation flow that invokes an agent to perform a secondary action.

Anyone with Studio access can create an automation flow.

  1. Navigate to Studio from the App switcher ().

  2. Select Automation.

  3. Select Create flow.

  4. Add a trigger to your flow and configure it if needed.

  5. Select Next, then Add an action.

  6. Find and select the action, Use agent.

    1. Connect Rovo to automation to allow agents to act on your behalf

    2. Select an agent (required)

    3. Write a prompt (required)

If the agent can’t act in automations, you'll need to add additional actions that use the output of the agent with the {{agentResponse}} smart value.

More about how to configure the Use agent action

Example flow that uses an agent in the automation steps. The agent is set up with a users permissions
A snippet of the flow builder showing two steps, one which the agent will act on

Flow examples

Out-of-the-box agents don’t take actions. Add actions to the automation after the agent step.

For your own agents, add tools so the agent performs your chosen actions. Your automations can be simple, like triaging a work item.

View available out-of-the-box agents

Scenario

Rule

Use the agent, Decision director

The automation flow is triggered when new Confluence pages are published with “DACI” in the title. The Decision director agent should review the page and leave a comment suggesting improvements.

 

WHEN: Page published


IF: Rovo condition

Content in the title relates to given text:

DACI (field text)


THEN: Use agent, Decision director

Review the content on this page and give recommendations (prompt)


THEN: Add comment to page

{{agentResponse}} (field text)

Use the agent, Jira work item organizer

The automation flow is triggered when a work item is created without a parent task or epic. The Jira work item organizer agent should find a relevant parent and leave the suggestion as a comment on the new work item.

 

WHEN: Work item created in Jira


IF: Work item field condition

Type is one of [all child work item types]


AND

IF: Related work item condition

Parent does not exist


THEN: Use agent, Jira work item organizer

Find a relevant parent (or epic) for this work item and explain why you recommend it (prompt)


THEN: Add comment to work item

{{agentResponse}} (field text)

Use the agent, Jira theme analyzer

The automation flow is triggered every 2 days at 8am. The Jira theme analyzer agent should analyze data from work items created in the past 2 days and send a summary in Slack, organized by theme.

 

When: Scheduled

Every 2 days at 8:00am


THEN: Use agent, Jira theme analyzer

Identify themes from work items created in the past 2 days (prompt)


THEN: Send Slack message

{{agentResponse}} (field text)

 

Still need help?

The Atlassian Community is here for you.