|
|
||
|---|---|---|
| .github/workflows | ||
| src | ||
| .gitignore | ||
| esbuild.config.mjs | ||
| LICENSE | ||
| main.js | ||
| manifest.json | ||
| package-lock.json | ||
| package.json | ||
| README.ja.md | ||
| README.md | ||
| README.zh-TW.md | ||
| styles.css | ||
| tsconfig.json | ||
Nodian
An Obsidian plugin that automatically syncs bidirectional relations in YAML frontmatter.
When you add a wikilink to a property in one file, the plugin writes a backlink in the target file's corresponding property — and removes it when you delete the link.
Example
Person.md Mail.md
───────── ─────────
tags: [Person] tags: [Mail]
Mail: [[hello@example]] → Person: [[Alice]] ← auto-generated
Features
- Auto sync — add or remove a link in one file, the other side updates instantly
- Relation pairs — define which properties are paired (e.g.
Mail ↔ Person,Artist ↔ Songs) - Tag-based matching — each pair requires tags; sync only fires when both property and tag match
- Display names — optionally use the
titleproperty as display text in backlinks - New file support — creating a file from a wikilink auto-adds tags and backlinks
- Full sync — one click from the ribbon icon, settings, or Command Palette
- Localized — English, Japanese, Traditional Chinese
- Mobile support — phone-optimized card UI for managing pairs
Works well with Obsidian Bases
Nodian can connect different Bases through typed YAML relations.
For example, you can have one Base filtered by #Person and another Base filtered by #Mail. When a Person note links to a Mail note through the Mail property, Nodian automatically writes the reverse Person property in the Mail note.
Because every relation pair requires tags on both sides, the same property name can safely be used in different Bases without triggering the wrong relation.
Install
With BRAT (recommended)
- Install BRAT from Community Plugins
- BRAT → Add Beta Plugin →
AkiSantin/Nodian
Manual
Copy main.js, manifest.json, and styles.css to:
<vault>/.obsidian/plugins/nodian/
Restart Obsidian → Settings → Community Plugins → Enable Nodian.
Getting Started
Step 1: Set up your first pair
Open any .md file and add a wikilink to a YAML property:
---
tags: [Person]
Mail: "[[hello@example]]"
---
Right-click the property name → select Configure bidirectional relation.
In the modal, set the counterpart property (e.g. Person) and tags, then press Save.
Step 2: Verify
Open hello@example.md — you should see:
---
tags: [Mail]
Person: "[[Alice]]"
---
That's it. From now on, any file's Mail property will automatically sync with the target file's Person property.
Step 3: Run full sync (existing vaults)
If your vault already has existing relations, run a one-time full sync in any of these ways:
- Click the sync icon in the left ribbon
- Settings → Nodian → Run full sync
- Command Palette (
Cmd/Ctrl+P) → Sync all bidirectional relations
This scans every file and backfills any missing backlinks.
Usage Guide
Adding a link
Add a wikilink to any paired property. The backlink appears in the target file automatically.
# You type this in Artist.md:
Songs: "[[Blue Sky]]"
# Plugin auto-generates this in Blue Sky.md:
Artist: "[[Artist Name]]"
Removing a link
Delete the wikilink from the property. The backlink in the target file is removed automatically.
Multiple links
A property can hold multiple wikilinks:
Songs:
- "[[Blue Sky]]"
- "[[Red Moon]]"
- "[[Green Field]]"
Each target file gets its own backlink. Removing one link only affects that specific target.
Self-relations
A property can be paired with itself:
Related ↔ Related
Adding Related: [[B]] in A.md will add Related: [[A]] in B.md.
Display names
By default, backlinks use the plain filename: [[my-artist-id]].
To use the title property as display text, enable Use title as display name in Settings. Backlinks will appear as [[my-artist-id|Some Artist Name]] (using the value of the source file's title frontmatter property). Only the title property is used — aliases are not checked.
Toggling this setting does not retroactively update existing backlinks. After changing it, run a full sync to update all backlinks across the vault.
New file creation
If you link to a file that doesn't exist yet:
Mail: "[[new-contact]]"
When new-contact.md is created (e.g. by clicking the link in Obsidian), the plugin will:
- Add the appropriate tag to the new file
- Write the backlink automatically
On mobile
On phones, Nodian uses a native-style card UI:
- Tap a property icon → Edit bidirectional relation opens a screen that lists the active pair and the other pairs for that property as cards
- The + button opens a dedicated add screen with autocomplete for tags and properties
- Settings → Relation pairs shows the same cards with edit / delete actions
The desktop layout is unchanged.
Tags
Every relation pair has two tags — Tag A and Tag B — that correspond to Property A and Property B. Tags are required, not optional.
How tags work
The plugin only syncs when both conditions are met:
- The source file has a property that matches a pair's property name
- The source file's tag matches that pair's corresponding tag
This prevents wrong-target sync. For example, if both Release files and Song files have an Artist property, the tag ensures each pair only fires for the correct file type — a Release-tagged file uses the Artist ↔ Release pair, while a Song-tagged file uses the Artist ↔ Song pair.
Automatic tag assignment
- When you set up a pair through the context menu, the source file's tag is used automatically.
- When a new file is created from a wikilink, the plugin auto-assigns the appropriate tag from the pair definition.
Settings
Go to Settings → Nodian.
Relation pairs
Add, edit, or remove property pairs. Each pair defines two property names and two tags that are bidirectionally linked.
| Setting | Default | Description |
|---|---|---|
| Auto sync | ON | Sync backlinks automatically when editing |
| Use title as display name | OFF | Use the title property as display text in backlinks. Run a full sync after changing. |
| Show ribbon sync button | ON | Show a button in the left ribbon for running a full sync |
| Debug mode | OFF | Log detailed info to the developer console (Cmd/Ctrl+Option+I, filter by [YBR]) |
Pair Examples
Each pair also has Tag A and Tag B configured alongside the properties in Settings. The tables below show the property pairings only — tags are assigned through the settings or context menu when you create each pair.
A music vault:
| Property A | ↔ | Property B |
|---|---|---|
| Artist | ↔ | Release |
| Artist | ↔ | Tracks |
| Composer | ↔ | Works |
| Label | ↔ | Releases |
| Related | ↔ | Related |
A company/CRM vault:
| Property A | ↔ | Property B |
|---|---|---|
| ↔ | Person | |
| ↔ | Domain | |
| ↔ | Account | |
| Service | ↔ | Account |
Important Notes
- Back up your vault before first use. This plugin modifies YAML frontmatter directly. While it only touches properties defined in your pairs, unexpected formatting changes are possible if you have complex custom YAML.
- Deleting a file does not remove backlinks pointing to it — those become unresolved links (by design, to prevent accidental data loss).
- Renaming a file is handled by Obsidian's built-in link updater — the plugin doesn't need to do anything extra.
- Duplicate pairs (e.g.
A ↔ BandB ↔ A) are redundant — one pair covers both directions. - Duplicate basenames — files with the same name in different folders may cause incorrect sync targets. Use unique filenames to avoid ambiguity.
- System properties (
title,aliases,tags,cssclasses,publish, etc.) cannot be used as relation properties.
License
MIT