Skip to content

Connections in Bases

Obsidian Bases is great at helping you manage a collection of notes. Smart Connections is great at telling you what is semantically related.

The Bases integration combines both:

Note

This integration is part of Connections Pro.

The Bases + Connections loop
  1. Open a .base file.
  2. Run "Add: Connections score bases column".
  3. Pick a reference note (or "Current/active file (dynamic)").
  4. Sort by the new score column to find the most relevant notes.
  5. Optional: add a list_connections column to see quick link trails per row.

Who this helps

Use this if you:


Quick start

Add a Connections score column

  1. Open any .base file.
  2. Open the command palette.
  3. Run:
    • Smart Connections Pro: Add: Connections score bases column
  4. Select the reference note you want to compare everything against.
  5. The Base refreshes and the new column appears (ready to sort).

Tip

If you do not see the command, make sure the active note is a .base file.
The command only appears when a Base is the current file.


Pick a reference point

After running the command, you choose what the score should be "relative to".

Use a fixed note

Pick a specific note when you want a stable lens, like:

This is ideal for planning dashboards because the meaning of the score stays consistent over time.

Use the current note

Choose Current/active file (dynamic) when you want the Base to behave like a custom Connections view:

Note

Like other bases functions that use the this.file property, for the dynamic option to work the base must be open in the sidebar.


Use Connections functions in Bases formulas

You can also build your own formula columns using the two Bases functions:

These functions appear in Bases formula autocomplete.

Example formula usage

Use the instance form when you want the formula to read naturally for each row:

Use the global form if you prefer explicit inputs:

Pair score with link trails

A score column is great for sorting, but it can be even more useful when you can jump into context immediately.

Add a list_connections column to show a small trail of related links beside each result.


Understanding the score

Each score is calculated using your configured Connections scoring algorithm.

A few practical rules:

  1. Treat the number as a relative signal, not an absolute grade.
  2. Score ranges vary by embedding model and vault content.
  3. If you hide or pin items in Connections, those signals can affect how results are ordered in the future (and your Base will reflect changes the next time it recalculates).
Tip

Bases is where you want the score to be actionable:

  • filter first (limit the candidate set)
  • then sort by score (rank inside the set)

Workflow recipes

These workflows are designed around common AI + PKM pain points: too much information, weak prioritization, and context switching.

1) Goal-driven prioritization

Use this when you have too many notes and not enough clarity.

  1. Create a Base for your project folder (or tag).
  2. Add a Connections score column.
  3. Choose your goal note as the reference.
  4. Sort descending by score.
  5. Review the top 10 and turn the best ones into next actions.

Outcome: you stop guessing what matters, and your "next work" list stays aligned with your actual goal.

2) Drafting with grounded references

Use this when you are writing and want your draft to stay anchored in your existing work.

  1. Make a Base of your reference notes (sources, excerpts, prior drafts).
  2. Add a score column referenced to your outline or current draft note.
  3. Sort descending.
  4. Keep the Base open while you write.
  5. Drag the top items into a "References" section as you go.

Outcome: faster drafting, fewer missed citations, fewer repeated ideas.

3) Research triage and reading order

Use this when you have a pile of reading and want a meaning-based sequence.

  1. Make a Base for your reading list folder.
  2. Add a score column referenced to your research question note.
  3. Sort descending.
  4. Start reading at the top.

Outcome: a ranked reading trail without manual tagging or re-organizing.

4) Compare against multiple anchors

Use this when you are balancing tradeoffs: multiple goals, multiple audiences, or multiple projects.

  1. Add one score column per anchor note (Goal A, Goal B, Draft, Constraints).
  2. Sort by one column, then scan the others to see tradeoffs.
  3. Filter to the notes that score well across the lenses you care about.

Outcome: better prioritization when "relevance" is multidimensional.

5) Build AI-ready context packs

Use this when you want better AI outputs without prompt bloat.

  1. Add a score column referenced to the question note (or the draft).
  2. Sort descending.
  3. Select the top 5 to 15 notes.
  4. Copy links (or send them to Smart Context) and remove noise.
  5. Paste that bundle into your AI chat with: "Use only this context."

Outcome: better grounding, less hallucination risk, less time collecting context.

6) Custom Connections view for a narrow domain

Use this when the global Connections view is too broad.

  1. Create a Base filtered to a narrow set (one folder, one tag, one project).
  2. Add a score column using "Current/active file (dynamic)".
  3. Dock the Base so it stays visible.
  4. Browse notes normally.

Outcome: you get a "Connections view" that only considers your chosen subset.