SoftTech AI Registry
Atlassian · Rovo

Automated Rovo Agents

Invocation of a Rovo agent by an Atlassian Automation flow so the agent analyses trigger context and generates a response without a person starting each interaction.

Recorded characteristics

Function
Allows a Rovo agent to be invoked automatically by an Atlassian Automation flow. A trigger can be added from the agent's Triggers screen in Studio, or the agent can be added to a flow using the "Use Rovo agent" action. Each time the flow runs, the configured prompt is sent to the agent, which analyses the trigger context and generates a text response exposed to the flow as the smart value {{agentResponse}}. Atlassian states that when agents are automated they pass their response to a secondary action rather than perform the specialised skills they were configured with, and that any skills the agent runs during an automated run are read-based, such as Read content.
Data access
During an automated run the agent reads the Atlassian context supplied by the trigger and prompt, including Jira work items and their fields and Confluence pages, using smart values such as {{workitem.description}}. Atlassian states that automated agents operate on behalf of the flow creator and assume that person's app permissions, so the agent can only read content the flow creator can access.
Actions
Generative only
External actions
Unknown
Human confirmation
Not required
Permission basis
User permissions
Administrative control
An automation trigger can be added to an agent by the agent's manager or editor from the agent's Triggers screen in Studio; a flow that invokes an agent can be created by a space or app administrator. Atlassian states that for agents to work autonomously they must be managed through existing Confluence space or Jira project administrators via an automation flow, and that without automations and admin setup agents cannot work autonomously. The flow must be saved and enabled, and Rovo must be connected to Automation to allow agents to act on the flow creator's behalf. Administrators select the agent and write the prompt, choose the app and space the flow runs in, and can enable or disable the flow. Studio admins can restrict who may create agents in the organisation to all users, up to 10 selected groups, or no users; agent owners set editors and managers and can restrict who can see and use an agent, and restricted agents do not appear as options for automation.
Default state
Disabled
Availability
Documented for Atlassian Cloud Jira, Jira Service Management and Confluence through Studio and Atlassian Automation. Rovo Studio agent governance settings are documented as available on Atlassian Cloud Standard, Premium and Enterprise and not available on Atlassian Government Cloud.
Licensing
Atlassian states that Rovo credits are included in all paid Jira, Confluence, Service Collection and Teamwork Collection cloud subscriptions, and that an organisation admin on a verified business domain must turn Rovo on.
External model or provider
Not established in the reviewed Atlassian documentation.
Limitations and uncertainty
The agent itself produces a generated text response; any resulting state change is performed by a separate Automation action such as Add comment, Create Confluence page or Send Slack message, and Atlassian states that the response-producing action must be coupled with a secondary action that publishes text. Atlassian states automated agents pass their response to a secondary action rather than perform their configured specialised skills, so this record does not establish that an automated agent executes its own state-changing or third-party tools; external action capability is recorded as unknown rather than no. Atlassian documents third-party tool use and per-user third-party authentication for agents generally, but not for automated invocation. No per-execution human confirmation step is documented once the flow is enabled; Atlassian documents that the prompt is sent to the agent each time the flow is triggered, including on a schedule. The underlying model or provider used for automated runs is not established.

Evidence