Jira and Confluence
Start a workflow in one and act in the other, with every step on the record. Ask your AI for it, or build it yourself.
- Jira steps
- 17
- Confluence steps
- 10
Ideas for Jira and Confluence
Each one is a real trigger and action. Ask your AI for any of them, in your own words, and it builds the workflow.
- When
New issueThen
Create a page - WhenNew pageThenCreate an issue
- WhenIssue updatedThenUpdate a page
- WhenBlog post publishedThenMove an issue to a new status
- WhenIssue status changedThenComment on a page
- WhenNew pageThenComment on an issue
What each app adds
Jira
Triggers
- New issueRuns when an issue is created in Jira.
- Issue updatedRuns when an existing issue changes in Jira: its fields, status, assignee or a new comment, with the issue as it is now.
- Issue status changedRuns each time an issue moves to another status in Jira, such as from In Progress to Done, with who moved it and when.
- New commentRuns when someone comments on an issue in Jira, with the comment, who wrote it and the issue it is on.
Actions
- List projectsList the Jira projects your connected account can see.
- Create an issueCreate an issue in a Jira project, with a title and, if you like, a description, type, priority, assignee, due date, labels and component. To make a sub-task, choose a sub-task type and the issue it belongs under.
- List the statuses an issue can move toList the statuses a Jira issue can move to from the one it is in now, with the move that takes it to each.
- Move an issue to a new statusMove a Jira issue to another status, such as In Progress or Done. The project's workflow decides which statuses it can move to from the one it is in now.
- Comment on an issuePost a comment on a Jira issue.
- Get an issueLook up a Jira issue: its title, description, status, assignee, priority, labels and due date.
Confluence
Triggers
- New pageRuns when a page is created in Confluence, with its title, space, link and who made it. Pages already there when the workflow is turned on don't start it.
- Blog post publishedRuns when a blog post is published in Confluence, with its title, space, link and who wrote it. Posts already there when the workflow is turned on don't start it.
Actions
- List spacesList the Confluence spaces your connected account can see.
- Create a pageCreate a page in a Confluence space, with a title and text.
- Get a pageLook up a Confluence page's title and text.
- Find pagesFind the Confluence pages that contain some text.
- Update a pageChange a Confluence page's title, replace its text, or add text to the end of it. Confluence keeps the earlier version in the page's history.
- Comment on a pagePost a comment at the bottom of a Confluence page.
How to connect Jira and Confluence
Connect your AI
Add Lodol to Claude, ChatGPT, Cursor or any MCP tool in one step, or open the editor.
Connect Jira and Confluence
Sign in to each once in your workspace. Their keys are encrypted and used by name.
Describe it, then turn it on
Say what should happen, and when. Try a run, then turn it on; every run is traced.
Jira and Gmail
Jira and Slack
Jira and Claude
Jira and BambooHR
Jira and Google Sheets
Jira and Google Forms
Jira and Notion
Jira and IntercomQuestions about Jira and Confluence
Yes. Connect each app once in your Lodol workspace and any workflow can use both: 13 actions and 4 triggers in Jira, and 8 actions and 2 triggers in Confluence.
Ask Claude, ChatGPT, Cursor or any AI tool connected to Lodol, in your own words, and it builds the workflow in your workspace. Or add the steps yourself in the visual editor, or start from one of the 1 template that already use both.
Free includes 100 runs a month. Builder starts at $18 a month for 2,500 runs and Pro at $120 for 10,000, and every plan has unlimited seats. A run counts once, however many steps it takes.
Connect Jira and Confluence.
Ask for it in Slack, Claude or ChatGPT. Lodol does it every time, and tells you if anything breaks.
Free plan, no credit card