Confluence integration
Turn screen recordings into Confluence pages
Record a process once. Clevera writes the how-to article and publishes it to the Confluence space you choose, with the screenshots attached to the page and callouts as Confluence panels. Publish again and the same page updates, history and comments intact.
Confluence Cloud
Screenshots as page attachments
Same page on every update
Info, tip and warning panels
What you can do
Fill your knowledge base spaces,
one recording at a time.
Confluence is the knowledge base for a lot of Atlassian teams: a space for support, one for IT, one for each product. The spaces are only as good as the pages in them. Clevera turns the walkthroughs your experts already give into finished Confluence pages, in the right space, looking like Confluence.
Runbooks and how-tos on demand
Record the support fix, the IT setup or the release process. Clevera writes the page with numbered steps and screenshots, so the space gets the page the moment the knowledge exists.
Panels, expands and tables
Callouts become Confluence panels with their title in bold, collapsible sections become expand blocks, and tables keep their header row and column alignment.
Screenshots attached to the page
Each screenshot is uploaded as an attachment of the page, with its caption, alignment and width kept. Publishing again adds a new version of the same attachment, not a duplicate.
Updates keep the history
Publishing an edited article updates the same page: same address, a new version in Page history. Links from Jira tickets and other pages keep working.
Comments stay where they are
Because the page is updated rather than replaced, the questions and answers your team left in the comments stay on it.
Videos that play in the page
A YouTube or Clevera video placed inside the article plays right in the Confluence page, next to the steps it explains.
How it works
From recording to Confluence space
in four steps.
An owner or admin connects your Confluence site once. Then anyone who can edit an article publishes it to a space.
- 1
Connect your Atlassian site
Sign in with Atlassian, pick the site and accept the permissions Clevera asks for. - 2
Clevera writes the page
From the recording, Clevera writes the article: headings, steps, callouts and screenshots. - 3
Choose the space
In Share, open Publish, pick a space such as Support or IT, and click Publish to Confluence. - 4
The page goes live
Clevera creates the page, attaches the screenshots and writes it, then links you straight to it.
See it in Clevera
Publishing to Confluence,
from the article’s Share window.
No copying between editors and no uploading screenshots into the page by hand. Pick a space and Clevera does the rest.
Choose the space
The list shows every space your Atlassian account can see, archived spaces left out. The page is created at the top level of the space; move it under a parent page in Confluence afterwards and later updates still find it, as long as it stays in the space.
Clevera remembers the space you picked last.
Update the page, keep its history
Clevera looks for a page with the same title in the space before it writes. Choose Update the existing article and the same page gets a new version, with comments kept. Edits made in Confluence since are overwritten, and you can restore them from Page history.
Confluence doesn’t allow two pages with the same title in one space, so a second copy needs a new title.
Confluence for the team, Bitbucket for the code
Atlassian teams often want the same guide in two places. Connect Bitbucket as well and publish the article to the repository as Markdown, from the same tab.
Filled in for you
What the Confluence page contains
and how callouts map to panels.
Clevera writes the page in Confluence’s own format. Here is what each part of the article becomes.
- SpaceYou choose
- Any space your account can add pages to. The page goes at the top level of the space and is created as the person who connected Confluence.
- Title and textSet for you
- The page title is the article’s title. Headings 1–6, bold, italic, underline, highlights, superscript, subscript, links and inline code all carry over.
- PanelsConverted for you
- Info, note, tip, success, warning and danger callouts become the matching Confluence panels. On a page with screenshots or a Clevera video, Confluence offers fewer panel types, so note becomes info, success becomes tip, warning becomes a yellow note and danger a red warning.
- Lists, tables and codeConverted for you
- Task lists keep ticked items, tables keep a header row and alignment, and code blocks keep their language. Numbered steps become a numbered list with each step’s title in bold.
- ScreenshotsUploaded for you
- Attached to the page as files named like
clevera-article-image-1234.png, shown with their caption underneath. Re-publishing adds a new version of each attachment. - Videos and tabsConverted for you
- YouTube and Clevera videos inside the article play in the page; a video file becomes a link. Tabs become a heading per tab, followed by its content.
Setup
Set up the Confluence integration
in about two minutes.
You need a Clevera workspace on Pro or Custom and Confluence Cloud on any plan. The Atlassian account you connect needs to add pages and attachments in the spaces you publish to. Publishing uses no credits.
- 1
Open Integrations
In Clevera, click your workspace name in the sidebar, choose Integrations, find Confluence and click Connect. - 2
Review the permissions
Atlassian asks to let Clevera view your profile, read spaces and pages, create and update pages, add attachments and keep access when you’re not using the app. - 3
Pick the site and accept
If your account has several Atlassian sites, choose the right one in the site menu, then click Accept. - 4
Publish an article
In the editor, click Share → Publish, click the Confluence tile, pick a space and click Publish to Confluence. - 5
Open it in Confluence
When you see “Published to Confluence.”, click Open in Confluence.
Confluence integration questions
No. Clevera publishes to Confluence Cloud, the sites at example.atlassian.net. Confluence Server and Data Center aren’t supported.
Not directly. Clevera creates the page at the top level of the space you pick. Move it under any parent page in Confluence afterwards; later updates still find it while it stays in the same space.
Yes. Updating writes a new version of the same page, so the address stays the same, the old version stays in Page history and comments are kept. Edits made directly in Confluence since the last publish are overwritten.
Usually permissions: the connected account can’t add pages or attachments in that space. Ask a space admin, or reconnect. Pages are also limited to 5 MB of content; split a very long article in two.
A Clevera workspace connects to one Confluence site. To switch, disconnect and connect again, choosing the other site. The picker lists up to 2,000 spaces.
No. Clevera renews the sign-in in the background. You only reconnect if someone removes Clevera’s access in your Atlassian account.
Publishing to Confluence is part of the Pro and Custom plans and uses no credits. See pricing, or read how Clevera compares to Confluence as a customer help center.
The page your space is missing, in minutes.
Record the process. Clevera writes it up and publishes it to Confluence, screenshots attached.