Publish to Confluencewithout opening Confluence
Turn the notes you just took into a published page, add a decision to the end of a living document, or pull a page into your work session so the next agent writes with it in hand.
One page out, one page in,
and two ways to add to one
Confluence is where a decision goes to be found again, which makes it the tool people skip when they are busy. These four rows remove the trip: the page is written from what you selected and filed in the space you pick, and the pull works the other way for the times you need the page as context rather than as a destination.
Reads, into your session
- Pull page: fetch a page into the active Memory session
- The space and page pickers list your 20 most recently modified pages
- A pull makes no AI call, so it costs nothing
Writes, into the tool
- Create page: publish what you selected into a space, under a parent if you want
- Append to page: add to the end of an existing page, leaving the rest untouched
- Comment on page: a plain footer comment, which can never alter the page
- Every write picks its target before the model runs
Connect Confluence in about two minutes
It is the same Atlassian card as Jira. If you have already connected Jira, Confluence is already on.
Create an API token
At id.atlassian.com, open Security, then API tokens. The same token covers Jira and Confluence: one credential, one card in Khint.
Turn Atlassian on in Khint's Integrations page
Your Atlassian email, the token, and your site (mycorp.atlassian.net). The token goes into your operating system's keychain.
Turn on the rows you want
Create page and Append to page are on by default. Pull page and Comment on page are a checkbox away on the same card.
Publish from the palette
Select your notes anywhere, hit Cmd+Shift+K, choose Create page, then pick the space. Khint writes the page and logs it to your active session.
Once connected, Knowledge can index your Confluence pages locally so agents search them without a pull, and a workflow can end on a Confluence write alongside a Jira and a Slack one, all from the same running text.
What it is allowed to do
Confluence pages are shared documents, and an append is the one operation that can destroy someone else's work. These are the rules it follows.
It never rewrites what is already on the page
An append copies the existing page through untouched and escapes only the new paragraph. Macros, tables and layouts survive byte for byte, because nothing parses or reinterprets the body that was already there.
A concurrent edit fails the write, it does not win it
Confluence has no partial update, so an append is a read then a write at version+1. That version number is an optimistic lock: if a colleague saved while you were writing, the write fails and tells you, rather than overwriting them.
When it cannot be sure, it refuses
A response missing a version, a title or the page body is not guessed at. The write is refused. A guessed version silently clobbers an edit, and a blank title wipes the page's own.
No model ever rewrites an existing page
Deliberately out of scope: section-scoped replacement, heading pickers, and any flow where a model regenerates page content. Confluence storage round-tripped through a model loses macros and layouts.
Comments cannot corrupt anything
Comment on page is a pure POST of a footer comment. It never reads or rewrites the page, which makes it the safe way to put something on a document you do not own.
Your credentials, your permissions
The token lives in your keychain and the calls go from your Mac to your site. Khint reaches exactly the spaces your account can already open.
The other integrations
All integrations
Common questions about Confluence and Khint
Do I connect Confluence separately from Jira?
No. Both live behind one Atlassian card in Khint and one API token. Connecting either connects both, and the palette then shows a Jira section and a Confluence section with their own rows, each of which you can hide.
Is appending to a page safe if someone else is editing it?
Yes, in the sense that it will not overwrite them. Confluence offers no append and no partial update, so Khint reads the page and writes it back one version up. That version acts as a lock: if the page moved while you were writing, the write fails with a clear message instead of replacing their edit. Retry and it appends to the new version.
Will it reformat or break my existing page?
No. The existing storage markup is copied through raw and only your new content is escaped. Nothing parses or regenerates the body that was already there, so macros, tables, layouts and attachments come out unchanged. Khint deliberately does not offer any flow where a model rewrites existing page content.
Can I file the page under a parent rather than at the top of a space?
Yes. Create page asks for the space and then, optionally, a parent page, and the picker lists the 20 most recently modified pages of that space so you rarely have to go looking for an id.
Does Khint keep a copy of my Confluence pages?
Only if you switch Knowledge on for Confluence, and then only on your own Mac, in a local full-text index that never reaches our servers. Without it, a page exists in Khint just as long as the Memory session you pulled it into, which is also local.
Write the page while the meeting is still fresh
Free with 300 credits a month. No credit card. macOS 13+ or Windows 10 22H2+.