nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Jira -Confluence automation

Iryna Lienska

Hello everyone, hope you can help me
We need to create an automation.

When an Epic is closed, a request should be sent to our LLM, where will be analysed, and after Confluence page should be automatically created with a summary (like guide, cause automation should look at comments, look at description and summary).

The page should include something like:
The ticket key

The Epic title

A structured summary (for example, formatted as a guide — depending on how we design the prompt)

We previously implemented this using Rovo, but with our own LLM the setup is slightly different, and I’m not fully sure how to structure the request properly.

Accepted answers

All comments

Trudy P Claspill

Hello @Iryna Lienska

Do you have a REST API interface for your LLM that you can use to send it the work item information?

Automation rules include an action for sending web requests that works for such APIs. You can also read the response for such requests and then use additional actions to create the Confluence page and then edit it to add the content, if that was in the response from your LLM.

Iryna Lienska

yes, we have

Evgenii

Hi, @Iryna Lienska

This is a great use case! Here's a possible approach to achieve this:

Jira Automation + "Send Web Request" action

Jira Automation has a built-in action to create Confluence pages. You can set up a rule:

• Trigger: Epic status changes to "Done"
• Action: "Send web request" to your LLM endpoint with the Epic's description, comments, and summary as context
• Action: Use the LLM response in a second "Send web request" to the Confluence REST API (POST /wiki/rest/api/content) to create the page

Step-by-step description:

1. Create an automation rule with trigger "Issue transitioned → Done" filtered to Epic issue type
2. Add a "Send web request" action pointing to your LLM API with a JSON body containing {{issue.summary}}, {{issue.description}}, and {{issue.comments}}
3. Save the LLM response using Smart Values
4. Add another "Send web request" to Confluence Cloud API to create the page with the generated content
5. Optionally add a "Link" action to connect the Confluence page back to the Epic

Monika Ambrozowicz_Seibert_

Hi @Iryna Lienska if you or your team work with n8n or Make, I would suggest it as a solution. You can build an automation that triggered by the epic status change will send a prompt to your LLM and then update the epic and/or create a Confluence page directly. To be honest, I haven't built such an automation with Jira but I did build similar ones, with LLMs involved, and it worked very well, so this should be possible too. However, if you are not familiar with tools like n8n, doing it with Jira automations as suggested in previous answers is a better option because you won't have to learn and maintain another tool.

If you're open to trying 3rd-party apps for better Jira-Confluence intergration, I recommend AutoPage. It lets you create a well structured page in real-time, each time a Jira work item is created or updated. However, it doesn't have integration with LLMs at the moment - generating descriptions with Rovo is planned though (I am affiliated with the team).

Iryna Lienska

Thank you!!

Evgenii

You're welcome. If answer helped you, feel free to accept it, to help other people with similar problems.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud