Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Does the "Use Rovo" action in Jira Service Management automation flows use Rovo credits?

Ryan Hormann
Contributor
September 9, 2026

I'm creating an automation flow and I see there is an action "Use Rovo". If I fill out the prompt, finish the flow, enable, and trigger the rule, will it use Rovo credits (once? per trigger? other?)?

 

Screenshot 2026-09-09 162740.png

2 answers

2 votes
Trudy P Claspill
Community Champion
September 9, 2026

Hello @Ryan Hormann 

Referring to this document from Atlassian:

https://support.atlassian.com/cloud-automation/docs/how-is-my-usage-calculated/

Agentic components like Use Rovo, Use agent, or Use Jira Coding agent are billed separately under Rovo credits and do not consume automation steps.

And per the Rovo credits document

https://support.atlassian.com/rovo/docs/rovo-usage-limits/

What consumes Rovo credits

Rovo credits are consumed by billable events. A billable event depends on the action performed.

For example,

  • In chat, each user message is a billable event.

  • For Atlassian agents and AI features, each invocation is a billable event.

 

0 votes
Sami Shaik
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
September 10, 2026

@Ryan Hormann ,

@Trudy P Claspill has the two documents that settle it, so just the direct form of the answer to your "once, per trigger, or other":

Per execution of the action, not once and not per trigger. Enabling the rule costs nothing. Each time the rule runs and reaches the Use Rovo component, that is one billable event drawn from your organisation's shared Rovo credit pool; a run that stops at a condition before the action costs no credits (it costs an automation step, which is a separate meter). So the credit cost is "executions of that action," which you can read per rule in Performance insights.

Two things worth doing before you enable it:

  1. Put your conditions in front of the action. A "Work item created" trigger with Use Rovo first and a filter after it spends a credit on every creation, including the ones you then discard. Condition first, Rovo second, and only the matching runs pay.
  2. Read the meter now. Atlassian Administration, Insights, Platform usage shows the Rovo credits meter alongside the automation steps meter; both have been live since 1 September, and extra usage for both starts billing on 3 December (Rovo usage and credits). Enable the rule, let it run a day, and the delta on that page is your real per-execution cost, which is the number to budget with rather than anyone's estimate.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin Site Admin
TAGS
AUG Leaders

Atlassian Community Events