Meeting ends,minutes are already published
The call wraps and the notes are a mess no one will read. Khint drafts the minutes with AI (attendees, decisions, action items, open questions) and publishes the Confluence page from one keyboard shortcut, on the notes you already typed.
Everyone agreed,
nobody wrote it down properly
Minutes are the easiest thing to skip and the first thing people ask for. The decisions live in your scratch notes; turning them into a shareable page means re-typing, adding headings, finding the right space, and remembering who owns what. So it slips a day, then it's stale, then someone relitigates a decision that was already made. Khint closes that gap: its Agents turn your raw notes into structured minutes, the Confluence integration publishes the page, and Memorykeeps the meeting's context attached to every draft.
One meeting, start to published page
A roadmap-sync call, step by step.
Start a session for the meeting
Before the call starts, open Memory and start a session: “Q3 roadmap sync”. Every Action you run from now on is logged and Khint keeps a compact running summary, so the minutes you draft later already share the meeting's context. How Memory works →
Connect Atlassian once
On Khint's Integrations page, paste your Atlassian email, an API token, and your cloud domain into the Atlassian card. From then on the palette shows a CONFLUENCE section, and any workflow can carry a Create Confluence page step. How integrations work →
Type the notes as they happen
During the call you jot the gist: “Attendees: PO, two devs, QA. Decided to cut the CSV export from the MVP. Action: Sam to spike server-side pagination by Fri. Open question: do we keep the legacy endpoint?” No headings, no Confluence markup, just what was said.
Run the minutes workflow
Select those lines and launch your workflow from the palette (Cmd+Shift+K). The first Agent rewrites the notes into structured minutes (attendees, decisions, action items with owners, open questions) and the final step is Create Confluence page. The first line becomes the page title; the rest becomes the body, wrapped into the format Confluence expects.
Share the link, keep the trail
The new page URL is the workflow's output. Paste it straight into the meeting thread so everyone has the minutes before they leave the call. The publish is also logged into your active session, so by the end of the hour your Memory session reads like a record: what was discussed, what you wrote up, where it lives.
The workflow is yours to shape
Up to five steps in series: AI Actions, then an integration write at the end.
Swap the drafting Actions for your own: your team's minutes template, a decision-log format, a translation step for a bilingual team. Or skip the hand-assembly: describe the flow in plain language and Khint's workflow generator builds the chain, reusing Actions you already have and slotting in the Confluence step when the integration is connected. The same machinery also files Jira issues and Linear tickets, so a sibling workflow can open the follow-up tickets right after it publishes the page.
No workflow? The palette publishes it too
For a one-off page you don't need a chain at all. With Atlassian connected, the palette's CONFLUENCE section carries a Create page row that runs a formatting Action on your selected notes and publishes the result in one move, alongside a Pull pagerow that brings an existing page into your Memory session, so the wiki stays in reach without leaving the app you're in. And when you want a longer working session, Khint ships an MCP server so Claude Desktop or Codex can read your meeting session directly (the notes, the drafts, the published page) without copy-paste.
Common questions
Can Khint publish a Confluence page from my meeting notes?
Yes, as a step you trigger, never in the background. Connect Atlassian with your email, an API token, and your cloud domain on Khint's Integrations page. Then either use the Create page row in the palette's CONFLUENCE section, or add a Create Confluence page step to a workflow and pin the space and parent page in the editor. When you run it on selected notes, the first line becomes the page title and the rest becomes the body, and the new page URL comes back as the result.
How do I get tidy minutes instead of a wall of bullet points?
An AI Action does the drafting first. You write an Action ("rewrite these notes as meeting minutes: attendees, decisions, action items with owners, open questions") and it runs on the selected text before the Confluence step publishes the result. The Action editor can Generate that prompt from a plain-language description and Improve it later, so you are not writing prompt boilerplate by hand.
Does the page keep the meeting's context?
If a Memory session is active, yes. Start a session for the meeting and everything you run is logged and compacted into a short summary that rides along with each AI Action, so the minutes draft already knows which project and discussion you were in without you re-explaining it. Sessions are stored locally in SQLite on your machine and are never synced to the cloud.
What does Khint send to the AI, and where do the page go?
Only the text you selected, plus (if a Memory session is active) the compacted session summary. Nothing else leaves your device silently. Your Atlassian email, API token, and cloud domain are kept in your OS keychain, the published page lands in the Confluence space you pinned, and every page Khint creates is logged into your local session history so you can trace what went out and when.
Try it on your next meeting
Free with 10 AI actions and 5 captures per day. No credit card. Type the notes, draft the minutes, get the page link back.