Introducing Create with Rovo for Automation

[#1]

👋 Hi Community! Sophia from the Automation team here with something we’re excited to announce!

Say hello to Create with Rovo - a faster way to build automation without starting from a blank canvas.

Some of our regular Automation users might remember this feature, which we've been improving over the past months. Just describe what you want in plain English, and Rovo turns it into a working automation flow for you.

In this post, we’ll walk through what it is, how it works, and how to try it today.

What is Create with Rovo?

We know that getting started is often the hardest part of building an automation. Knowing which trigger to pick, which components to add, and how to wire it all together can be confusing.

Create with Rovo takes that first step for you. Instead of building a flow component by component, simply tell Rovo what you’re trying to do in natural language. For example:

• “Assign new tasks to the onboarding team and send them a Slack message.”

• “Email the reporter when an expense claim is submitted without an attachment.”

• “Every 9am on Monday, send me a summary of my meetings for the week.”

How it works

When you head to Automation in your product, you’ll now see Create with Rovo as an option under the Create flow button. Here’s the flow:

1. Click Create flow → Create with Rovo.

2. Describe the automation you want in plain English.

3. Rovo generates the flow for you to review, tweak, and save.

From there, it’s a normal automation flow - you can edit any part of it, add or remove components, and turn it on whenever you’re ready. You stay in full control; Rovo just gives you a big head start.

Where you’ll find it

We’re rolling this out across Product Automation, including Jira, Jira Service Management, and Confluence, for tenants with Rovo/AI enabled.

The flows you build will live in Rovo Studio, but you can view and access them from your Product Automation Flows List.

Try it and let us know what you think

Give Create with Rovo a go the next time you’re building an automation, and let us know how it goes.

As always, we’d love your feedback. Feel free to leave a comment below or book in time with me here.

[Mia Tamm _Simpleasyty_]

Hey @Sophia Do nice direction. I think this could become particularly powerful in Confluence once flows can be driven by structured page context.

For example: “when a policy reaches its review date and still has no owner, flag it for review” is simple to describe in natural language, but depends on having reliable structured data behind the page.

Curious how far you see Create with Rovo going with content properties or other page-level metadata as conditions.