Skip to content
Docs menu

Databases in Notes

Notion-style databases in Venom Notes that stay plain markdown, with property types, views, filters, formulas and rollups, and an Obsidian Bases file on export.

View .md

A Notes database is a folder of notes plus a schema. Each row is an ordinary note: a full page you can write in, link to and find in search. Its values are in the note's frontmatter, so the same note opens in Obsidian with every value intact. The schema says what each property is (a status, a date, a relation to another database) and lists the database's views.

Where a database lives

  • Rows are the notes directly inside the database's folder. A note in a subfolder is not a row: it is a page inside a row. A note you create in the folder from the editor, or bring in with an import, shows up as a row.

  • Inline. Type / in a note and choose Create inline database. The database's folder is <this note's folder>/<database name>/, and the note shows it in a base block. Each database gets its own folder, so when "Untitled database" is taken the next one is "Untitled database 2", then 3. If the create fails, a toast says why.

    ```base
    database: 0193a1f2-…
    view: table
    ```
  • Full page at /globe/db/<id>.

  • Deleting a database deletes only the schema and views. Its notes stay where they are.

Property types

Type Stored in the note as Notes
Title the note's name Renaming the row renames the note, and the links to it are rewritten
Text, URL, email, phone a string URLs must start with http://, https:// or mailto:
Number a number Shown as a number, a percent (0.125 shows as 12.5%) or a currency
Select, status a string Options have colours. A status option belongs to a group: to do, in progress or done
Multi-select a list of strings
Date 2026-03-01, 2026-03-01T09:30, or 2026-03-01/2026-03-05 for a range "Include time" and "End date" are per property and per cell
Person a list of member ids Picked from the org's members
Checkbox true or false
Relation a list of [[wikilinks]] to rows of another database Optionally two-way
Files & links a list of URLs Uploads are not supported yet
Created time, created by, last edited time, last edited by nothing Read from the note
Formula nothing Worked out when read (below)
Rollup nothing Count, count values, sum, average, min, max, percent checked or show original, over a relation

A value that doesn't fit its type, for example text typed into a number in Obsidian, shows as empty. It stays in the note and is not overwritten until someone sets that cell.

Properties can be added, renamed, hidden, reordered and deleted from a column's header.

  • Renaming a property moves its frontmatter key in every row.
  • Deleting a property keeps its values in the notes.
  • Changing a type first shows which values change and how many become empty, then converts them on Convert. Text becomes options, and numbers stay numbers where they can.

Views

Each database has as many views as you like. Each view has its own filters, sorts, grouping, shown properties, column widths and text wrapping.

  • Table. Click a cell to edit it, as in Notion. A checkbox toggles in one click; links, emails and phone numbers open from the cell. The grid also works from the keyboard:

    • arrow keys, Tab, Home, End, Page Up and Page Down move the cursor;
    • Enter, or just typing, edits a cell, and Enter or Tab saves it (Tab moves right);
    • Escape cancels the edit or leaves the grid, and Delete clears the cell;
    • Space, Shift+Enter or the row's Open button opens the row;
    • ⌘C, ⌘X and ⌘V copy, cut and paste cells. A block of cells copied from a spreadsheet pastes into the grid from the cursor, one save per row. Options that don't exist yet are added.

    + New (or New in the toolbar) adds a row and puts the caret in its name. Drag a column's edge to resize it, or its header to move it. The header menu renames the property, changes its type, sorts, filters, hides or wraps the column, inserts a property left or right, duplicates the property with its values, or deletes it. The footer under each column has a calculation: count all, values, empty, unique, percent empty or not empty; sum, average, median, min, max and range for numbers; checked, unchecked and percent checked for checkboxes; earliest, latest and range for dates. It is worked out over the rows loaded so far (marked * while more are left to load). Only the rows on screen are drawn, and rows load 100 at a time as you scroll, so a table with thousands of rows stays smooth.

  • Board. Columns come from a select or status property, or any property under Group. Dragging a card to another column changes its value, + New at a column's foot adds a card there, and empty columns can be hidden.

  • List. One line per row.

  • Gallery. Cards with a cover: the first image in the note, a files or URL property, or none.

  • Calendar. A month, by a date property. A range shows on each of its days, and dragging a row to another day moves its date (and its end).

  • Timeline. A bar per row over a date property (a range is a long bar), on a scale of days, weeks or months, with a red line for today. Drag a bar to move it, or its left or right end to change the start or end. A row without a date gets one by clicking its track.

  • Chart. Vertical or horizontal bars, a line, a donut, or one big number, over the rows the view's filters keep. The X axis is a property (a select, status, person, checkbox or relation, or a date by day, week or month); the Y axis counts rows or sums or averages a number. Bars and lines can be split by a second property (stacked). Option colours carry over. Clicking a bar, point or slice lists its rows, and a row there opens it. A chart reads up to 5,000 rows. In an Obsidian export it stays a table with its chart settings kept for Notes.

Group works on tables and lists too: each group has a header with its count, collapses with ▸, and + adds a row in that group. Sub-items (in the view's ⋯ menu, for tables and lists) nests rows under a parent: Notes adds a "Parent item" relation to the database itself the first time. A row with sub-items has a ▸ to show them, and + on a row adds a sub-item under it.

View settings

The ⋯ in the toolbar opens one panel for the view. It has the view's name and these pages:

  • Layout: turn the view into another layout (table, board, list, gallery, calendar, timeline or chart), the chart's settings, Show vertical lines (tables), Show page icon, Wrap all content, Sub-items, Show by (a calendar's or timeline's date) and Open pages in.
  • Property visibility: show, hide and order the view's properties.
  • Filter, Sort and Group, the same editors as the toolbar's quick buttons.
  • Conditional colour: rules such as "Status is Done → green". A rule colours the whole row, or one property's cell. The first rule a row matches wins, and a rule missing its value is skipped.
  • Copy link to view: a /globe/db/<id>?v=<view> link that opens the database at this view.

Under Database settings are Edit properties (each property's menu) and Lock database.

Templates

New ▾ lists the database's templates. Clicking one makes a row from it, and Empty page makes a blank row. A template has a title pattern (Meeting {{date}}; also {{time}}, {{weekday}} and {{month}}), preset property values and a page body. Its ⋯ sets it as the default (used by New, + New and a board column's + New), edits, duplicates or deletes it, and + New template adds one. In a row's peek, Apply template ▾ fills the row's empty cells, and its page if that is empty, from a template. Templates are ordinary notes in the database's _templates folder (their preset values in frontmatter, plus globe_template: {title, default}), so an Obsidian export keeps them.

Automations

⚡ in the toolbar (or Automations in View settings) opens the database's automations. Each one has a trigger and up to ten actions, and starts off: switch it on in the list.

  • Triggers: a row is added; a property changes (to a value, if you give one: "Status changes to Done"); or a Button is pressed.
  • Actions: set a property on the row (a value, or today or now for a date); notify a member (a page comment on the row that @mentions them, so it reaches their bell); add a row to another database; create a Venom Tasks issue in a team, with a link back to the row. Text can use {{title}}, {{date}} and {{Property name}}.

Automations run on the server as part of the write that fires them, one after another. A change an automation makes never fires automations (so two automations can't loop), and an action that fails stops that automation, not the write. Activity lists the last runs: which automation, on which row, what it did or why it failed (kept 30 days). In the org vault only members with org:manage can change automations, and a locked database's automations can't be changed.

A Button property shows a button in every row. Its menu sets the label and the automation it runs (one whose trigger is "its button is pressed").

Editing cells

  • Select, multi-select and status open a picker: type to search, Enter picks the highlighted option or creates a new one, and Backspace removes the last chosen option. A status lists its options under To-do, In progress and Done. Drag an option to reorder it (or to move a status option to another group). Its ⋯ menu renames it, changes its colour or deletes it; a rename or delete is written to every row that holds the option.
  • Enter on a selected cell opens its editor: a text box, a picker or the calendar. Click + New and start typing at once: the keys you press before the new row's name opens are kept.
  • Copy and paste (Ctrl or Cmd with C, X and V) move a cell's value to another cell. Pasting into a cell of the same type keeps the value as it was; into another type it is read from the cell's text. A paste of text copied somewhere else, or of several cells from a spreadsheet, fills the cells from the cursor.
  • Date opens a calendar. End date makes it a range (the next two clicks set the start and end), Include time adds a time to the property, and the start and end can be typed. Clear empties it.
  • Person lists the organisation's members by name (the part of the email before the @, until a name is stored), with the email beside it, and Relation searches the related database's rows. Each pick saves at once.
  • Number cells show the property's format: number, percent or a currency.

Properties

+ at the end of the header row opens a searchable list of property types, each with its icon. Picking one adds the property at once, named after its type; click the header to rename it. A formula, rollup, relation or button opens its settings first. A header's menu edits a Select, Multi-select or Status property's options inline: the colour swatch beside an option opens its colours by name, a status option's group reads To-do, In progress or Done, and + Add an option adds one. Include time is off for a new date property, and a date shows its time only when the property includes it. A table with more rows than fit is only footed with "N of M loaded" while rows are still left to load, not when sub-items are only collapsed.

An error from a cell write shows above the table with a × and goes away on its own after ten seconds.

The database block

An inline database shows its title (click it to rename it) and an optional description. Its toolbar shows when the pointer or focus is in the database, or while a filter, sort or search is set. View tabs: + adds a view, a click on the open tab renames, duplicates or deletes it, and tabs drag to reorder. ↗ Open opens the database as a full page. The ⋯ menu adds a description, copies the database's link, duplicates it (same properties and views, a new empty folder beside it), locks it and deletes the block from the note (the database and its pages stay in the vault). A locked database keeps its views and properties as they are; rows can still be added and edited, and view changes such as a filter apply only on your screen until it is unlocked.

An inline table may run wider than the text column, into the page's spare width, and the block is not tinted or outlined when you click inside it. A database created in a note appears in the sidebar at once.

Opening a row

A row opens as the view's ⋯ menu says under Open pages in:

  • Side peek (the default): a panel on the right; drag its left edge to resize it.
  • Center peek: a dialog in the middle of the screen.
  • Full page: the note's own page. Under the title it shows the same editable property panel as the peek, in the same order, with coloured options, formatted dates and people by name, instead of the raw frontmatter.

A peek shows the row's title and every property, editable, and under them the row's page in the block editor, edited live with anyone else who has it open. Its header opens the row as a page, copies its link, switches between side and center, and steps to the previous or next row (↑ ↓, or k j). Escape closes it.

Filters and sorts

Filters are conditions joined by and or or, and groups of conditions nest up to three deep. The operators depend on the type:

  • text: is, is not, contains, does not contain, starts with, ends with;
  • numbers: =, ≠, >, ≥, <, ≤;
  • dates: is, before, after, on or before, on or after, within the past or next week or month;
  • statuses: is in group;
  • lists: contains, does not contain;
  • every type: is empty, is not empty.

A condition that is missing its value is ignored, as in Notion. Sorts apply in order, and empty values always go last. Selects and statuses sort in their options' order.

Formulas

A formula is worked out for each row. The language is small and safe: it is parsed by a parser Notes has of its own and never run as code.

prop("Price") * prop("Quantity")
if(prop("Due") < now(), "Overdue", "On track")
dateBetween(prop("Due"), today(), "days")
format(prop("Done") / prop("Total"), "percent")
prop("First") + " " + prop("Last")
  • Values: numbers, text in quotes, true, false, empty, and lists in [ ].

  • Properties: prop("Name"). Obsidian's styles work too: a bare name (price), note.price, note["Due date"], and file.name, file.folder, file.ctime, file.mtime and file.tags. Use formula.Other for another formula's value.

  • Operators: + - * / %, comparisons (== != < <= > >=), and/&&, or/|| and not/!. + joins text when either side is text. A date plus or minus a duration such as "7d" or "2 weeks" moves it, and dividing by zero gives empty.

  • Functions:

    • logic: if(cond, then, else), empty(x), not(x);
    • dates: now(), today(), date("2026-01-31"), dateAdd(d, n, unit), dateSubtract(d, n, unit), dateBetween(a, b, unit), formatDate(d, "MMM DD, YYYY");
    • numbers: format(n, "number"|"percent"|"currency", decimals), round(n, places), floor, ceil, abs, sqrt, pow, min, max, sum, toNumber;
    • text and lists: length, contains, concat, join, lower, upper, trim, replace, startsWith, endsWith.

    Date units are years, months, weeks, days, hours and minutes.

  • Methods: x.contains("y"), x.isEmpty(), x.lower(), x.toFixed(2), list.length, date.year, date.month and date.day.

A formula that can't be worked out shows #ERROR in its cell, with the reason on hover, for example expected a number, got "abc" (at 12). A formula that refers to itself is reported, not followed.

Obsidian Bases compatibility

Export. A database exports as <Name>.base, an Obsidian Bases file, which sits beside its folder of row notes. It holds:

  • filters: file.inFolder("<folder>");
  • formulas, written in Bases' style (prop("Price") becomes note.Price);
  • properties: the title's display name;
  • views, each with name, order, sort, groupBy, columnSize, image and filters. A condition is written as an expression: note.Status != "Done", note.tags.contains("web"), note.Due < date("2026-03-01").

Import. A .base file reads back as a database: from a vault zip, from the editor (a base block holding a .base file offers Make it a Notes database), or through the API.

  • A file Notes wrote comes back exactly as it was.
  • A file edited in Obsidian keeps the edits Bases can express: names, order, sorts, grouping, column widths, filters and formulas.
  • A file written in Obsidian is read for what it says. Property types are guessed from the values in its folder's notes. Filters that are a single comparison become editable conditions, and anything else stays as an expression that Notes evaluates.

Where Notes and Bases differ.

Obsidian Bases Notes
Rows every note the filters match, anywhere in the vault the notes directly in the database's folder. A top-level file.inFolder filter sets the folder; other top-level filters apply to every view
Property types types.json (text, number, date, checkbox, list) Notion's types, kept in the file under globe.properties
Board and calendar views not built in exported as a table grouped or sorted the same way, plus globe.type. Obsidian shows them as tables
Map views and row limits supported a map is read as a table, and the row limit is dropped. Notes says so when it imports the file
Options, colours, status groups, relations, rollups not in Bases stored under globe keys, which Obsidian does not use
Formula functions Bases' own Notes reads Bases' references and common methods. Notion's functions (dateBetween, format) don't run in Obsidian
not: filter groups supported a group of plain expressions under not becomes one expression. A nested group under not is left out, with a warning
Date ranges not supported start/end in one value, which Obsidian shows as text

API

Every endpoint is under /globe/api/databases and uses the console session, like the rest of the Notes API. Every call checks the add-on and the vault's scope: personal databases are their owner's, and org databases can be read by every member but changed only with org:manage.

GET /globe/api/databases?vault=me|org the vault's databases
POST /globe/api/databases {vault, name, folder?, schema?, views?}: create one. The folder defaults to the name
POST /globe/api/databases/import {vault, name, folder, yaml}: a .base file as a database
GET, PATCH, DELETE /globe/api/databases/:id read, change ({name?, description?, locked?, schema?, views?, renames?, copies?, automations?}) or delete it. renames moves a renamed property's frontmatter key, copies ({newId: sourceId}) fills a duplicated property with the source's values, and a renamed or deleted option is rewritten in its rows. A locked database answers 409 database_locked to schema and view changes
GET /globe/api/databases/:id/export the .base file
GET /globe/api/databases/:id/rows?view=&offset=&limit=&q= a page of rows: 100 by default, at most 500
POST /globe/api/databases/:id/rows {title, values?, template?}: a new row note; a template presets its title, values and body
POST /globe/api/databases/:id/rows/:noteId/template {template}: fill the row's empty cells, and its empty page, from a template
GET, POST /globe/api/databases/:id/templates the row templates, or a new one ({name, title?, values?, body?, isDefault?})
PATCH, DELETE /globe/api/databases/:id/templates/:templateId change a template (the same fields) or delete it. One template is the default at a time
PATCH /globe/api/databases/:id/rows/:noteId {values: {propertyId: value}}: write cells to the note's frontmatter
GET /globe/api/databases/:id/automations the last runs of the database's automations (the activity log). The automations themselves are saved with PATCH …/:id {automations}
POST /globe/api/databases/:id/rows/:noteId/button {property}: a Button property pressed on a row; runs its automation
POST /globe/api/databases/:id/retype {property, type, apply?}: preview a type change, or apply it
GET /globe/api/people the org's members, for the person picker

How a page of rows is worked out:

  • In Postgres ("mode": "sql"), when every filter and sort in the view is on a stored property, the title or the note's times. The rows are found by an index on the note's folder.
  • In memory ("mode": "memory"), when a view filters or sorts on a formula, a rollup, a relation or a Bases expression. This reads at most 10,000 rows.

Formula and rollup values come back in each row's computed, and their errors in errors.