Atlassian is leveraging OpenAI’s large language models to streamline the creation of Confluence automation rules, aiming to make the powerful but complex feature more accessible and efficient for admins.

  • AI generates complete automation rules from natural language prompts
  • Process reduces token usage by 47%, lowering costs
  • Automation now easier to configure despite growing feature complexity

What happened

Atlassian has introduced a new method for generating Confluence automation rules using large language models from OpenAI. This innovation allows admins to simply describe the automation use case or rule behavior in natural language, which the AI then converts into a fully configured automation rule.

The system employs a three-step process that starts with selecting relevant automation components before generating a complete rule. This stepwise approach addresses challenges related to the AI’s token limits and helps manage the complexity of more than 40 configurable components in Confluence automation.

Why it matters

Automation in Confluence has traditionally required a detailed understanding of numerous components and configurations, making initial setup and scaling difficult for teams. As more components are added over time, this complexity and the associated costs increase.

By enabling natural language inputs and using an intelligent component selection process, Atlassian cuts the AI token usage by 47%, significantly reducing operational expenses while making automation creation more intuitive. This advancement enables broader adoption and maximizes the value of Confluence and Jira at scale.

What to watch next

Future updates may focus on expanding the AI’s ability to handle even more complex automation scenarios and component configurations, improving the accuracy and usefulness of the generated rules. Monitoring Atlassian's rollout and user feedback will be key to understanding real-world impact.

Additionally, similar AI-powered automation improvements could extend to other Atlassian products, potentially setting a precedent for how large language models can simplify enterprise software configuration and management across the SaaS ecosystem.

Source assisted: This briefing began from a discovered source item from Atlassian Blog. Open the original source.
How SignalDesk reports: feeds and outside sources are used for discovery. Public briefings are edited to add context, buyer relevance and attribution before they are published. Read the standards

Related briefings