Confluence · v1.0.0 · Planned
VaultNote
for Obsidian
Publish selected Markdown notes into Confluence — links, backlinks and all — without hand-converting anything.
- Markdown import
- Wiki-link resolution
- Selective publish
- Update in place
The gap it closes
A large amount of genuinely useful knowledge is written in Markdown vaults and never reaches the team wiki, because moving it means hand-converting every note and re-creating every internal link.
The existing bridges point the wrong way or stop at the boundary: they cover Jira rather than Confluence, or they export a note as flat text and drop the link graph that gave it its structure. What arrives is a wall of prose nobody can navigate.
VaultNote treats the links as the point. Notes that reference each other arrive as Confluence pages that link to each other.
How it works
Three steps, then it runs itself.
- 01
Choose what to publish
Select the notes or folders that should become team knowledge. Nothing is published implicitly — a private vault stays private by default.
- 02
Links are resolved, not flattened
Internal wiki-links between published notes become real Confluence page links. A link to a note you did not publish renders as plain text rather than a broken link.
- 03
Re-publish updates in place
Publishing the same note again updates the existing page and leaves its Confluence history intact, instead of creating a second copy.
How it behaves
The decisions that matter.
-
Publishing is always explicit
There is no “sync everything” mode. A vault contains personal notes, and the safe default is that nothing leaves it unless you chose it.
-
Re-publishing never forks a page
Notes are tracked to the page they created, so the second publish is an update with proper version history — not a near-duplicate for the team to trip over.
-
An unpublished link degrades gracefully
Links pointing at notes you kept private become plain text. They never become dead links, and they never leak the private note’s title into a URL.
-
Markdown is converted, never executed
Content is parsed and mapped to Confluence’s own format with embedded scripting stripped, so importing a note cannot introduce active content into your wiki.
Where it runs, and what it reaches
Nothing leaves Atlassian.
This app declares no external network access at all. It runs on Atlassian’s own infrastructure and talks to nothing outside it — there is no third-party service in the path to review.
Runs on
Atlassian Forge (runs on Atlassian’s own infrastructure)
Your credentials live in
Forge encrypted secret storage, inside your own installation
Surfaces it adds
Confluence global page, Space settings page
Pricing
Priced per user, billed by Atlassian.
Every paid plan starts with a free 30-day evaluation, arranged by Atlassian. Atlassian collects the payment, handles invoicing and tax, and is the merchant of record — so this app appears on the Atlassian bill you already pay, not a separate one from me. Sites of ten users or fewer pay one flat monthly rate.
Evaluation
Free
Up to 10 users
$8/month
11–100 users
$0.80/user/mo
101+ users
$0.55/user/mo
Indicative pricing for an app that is not listed yet. The rate on the Marketplace listing is the one that applies.
Documentation & data handling
Everything it touches, stated plainly.
Installing & getting started
- Install VaultNote from the Atlassian Marketplace into your Confluence site and review the permissions listed here.
- Open Settings → Apps → VaultNote and work through the three steps above.
- Your evaluation runs for 30 days with everything switched on, so it can prove itself before you pay for it.
- Stuck? Email [email protected] — one business day response.
Permissions, and why each one
read:confluence-content.all- Find whether a note has already been published, so a re-publish updates that page instead of duplicating it.
write:confluence-content- Create and update the published pages — the core function of the app.
storage:app- Remember which note maps to which page, so updates land in the right place.
What is stored, and where
- Nothing leaves Atlassian. The app has no external egress at all — content moves from your upload into Confluence and stops there.
- The only stored record is the mapping between a published note and the Confluence page it created, held in your own installation’s storage.
- Published content lives in Confluence under your space permissions, exactly like a page written by hand.
- Uninstalling removes the mapping. Pages you published remain yours.
Technical detail
- Version
- 1.0.0
- Platform
- Atlassian Forge
- Runtime
- Node.js 22 — Forge runtime
- Products
- Confluence
- Modules
- Confluence global page, Space settings page
- External connections
- None
- Billing
- Paid through the Atlassian Marketplace
- Support
- [email protected]
- Support SLA
- One business day
- Publisher
- Builds By Luke, Canada
Questions people ask.
Does it sync continuously?
No. Publishing is a deliberate action. Continuous sync of a personal vault into a team wiki is a privacy accident waiting to happen.
What happens to links pointing at notes I did not publish?
They render as plain text. Nothing breaks, and the private note is not exposed.
Will re-publishing overwrite someone’s edits in Confluence?
It creates a new version of the page, so Confluence’s page history holds every prior version and you can compare or restore normally.
VaultNote is on its way.
It is on the build list for the Atlassian Marketplace. If you want it sooner — or want it to do one specific thing — that is genuinely useful to hear.