Are you using Rovo to automate small & repetitive tasks in Confluence?

[#1]

I've been using Rovo periodically to handle small, monotonous Confluence tasks. For example: reorganizing pages and folders alphabetically when there isn’t a convenient built-in way to keep them that way automatically (feature request under consideration: CONFCLOUD-65454)

It made me wonder: Are you using Rovo for similar small-scale automation? 🌱

Not necessarily big workflows or complex agents, but the repetitive little tasks that are annoying to do manually and easy to forget.

I'd be interested to hear:

• What small or repetitive tasks are you automating with Rovo in Confluence?

• Are you running them manually when needed or have you found a way to make them more systematic?

• Which use cases have actually saved you noticeable time (and effort)?

Would love to collect a few practical examples from the community - the boring automations might actually be some of the most useful ones 😊 💙

[Jay Maechtlen]

I haven't attempted to do any organization of this maze of pages yet.

And it can be confusing, we have 'design' pages in several spaces that overlap.

Mainly I am using ROVO as a fact-gathering tool (within Confluence and Jira) to learn status of features, etc.

Mainly, I'm using it to review documents I am creating - I attach a pdf to a suitable page (I'm using the 'attachments' macro) and ask ROVO to review it. Sometimes I ask ROVO to ignore the other things I've written, and only consider other sources. This has been quite useful.

[Jay Maechtlen]

Note that we use Confluence in the PM, Dev, Product Support and several other such spaces, but marketing, training, and many others use SharePoint. My docs need to reach everyone, so I create in Word and publish in PDF.

[Brita Moorus]

That's a really interesting use case, @Jay Maechtlen! 😊

I like the idea of using Rovo as a reviewer rather than only as a search or creation tool by asking it to look beyond your own content and compare against other sources. That feels like one of those small uses that can really save a surprising amount of time.

Your Confluence/SharePoint split is interesting too. I can imagine that makes knowledge discovery harder when different teams live in different systems. Have you tried connecting SharePoint to Rovo as well, so it can search across both sources? That could potentially reduce some of the need to republish the content.

[Jay Maechtlen]

Rovo can't touch SharePoint content directly - I have to upload to Rovo or attach a file to a Confluence page for that. We have Copilot too - but Copilot isn't permitted to touch content directly - I must upload to Copilot for it to act on a file. 

These are probably great safety features, but they do limit things a bit.

Copilot will offer to create various kinds of automation, at least some of which I can execute.

(I am contractor, and my laptop belongs to my employer - so I have a couple of restrictions that a regular employee at the client site would not have)

But I can upload multiple files to Copilot and have it do work on them, or extract content from them. So there is definitely room for creativity here!