Forums

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

Rovo agent not publishing output to new confluence page

Phillip C
Contributor
May 28, 2026

This might be a trivial question, but my attempt to have an automation using a rovo agent to summarise steps on a work item into a KB article guide isn't outputing any of the content into the confluence page. 

The steps are:

  1. Manual trigger
  2. use agent "knowledge base article agent" (given it a prompt)
  3. Publish new page in confluence - page content {{agentResponse}}Screenshot 2026-05-29 094350.png

The page gets created, except there is nothing on the page.

I've reviewed the automation logs, there is output from the agent, but its not coming over to the confluence page.

Seems like something basic im missing?

I've looked at many Atlassian articles on how to use rovo agents and in automations, none of them help.

e.g.

How Do You Use {{agentResponse}} in Atlassian Auto... - Atlassian Community

Automating Rovo agents | Rovo | Atlassian Support

 

1 answer

0 votes
Trudy Claspill
Community Champion
May 28, 2026

Hello 

Can you provide the details of the Use Agent step, please?

Are you triggering this rule while viewing a Jira issue?

Before the step to create the Confluence can you add a Log action to print the agent response smart value to the rule execution log? Then try executing the rule again and share the audit log output with us.

Phillip C
Contributor
May 28, 2026

Agent action:

use agent.png

 

Are you triggering this rule while viewing a Jira issue?

Yes, when viewing a JSM work item

 

Log action only shows "Log": when attempting to log the {{agentResponse}} response.

log action.png

 

I've also logged a support ticket and will track and place an update on this.

Trudy Claspill
Community Champion
May 28, 2026

Thank you for the additional information @Phillip C 

I think that the problem is that your agent doesn't know what issue you want it to reference.

Your prompt says "the ticket". I think if you try replacing that with {{issue.key}} it will then know which ticket to reference and your agent response will not be empty. That is what worked in my simple test.

Screenshot 2026-05-28 at 9.21.18 PM.pngScreenshot 2026-05-28 at 9.21.02 PM.png

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events