Send summarized bookmarks to Notion or Obsidian

What you keep should end up where you work, with the summary already written.

September 21, 2026·6 min read

Two things go wrong with most bookmark exports. The first is that they export everything, so your notes app inherits the pile. The second is that they export links, so what arrives is a column of URLs you still have to open. The route below fixes both: decide first, and send the summary with the save.

Why summarize before you export

A bookmark is a pointer. On its own it tells you nothing you can search for, sort by, or read in a table. A bookmark is worse than most, because the post is often one sentence reacting to a quoted post, and the quoted post is where the substance is. Export the link and you have exported the reaction.

What you want to arrive at the destination is three things: what the save says, why it is worth keeping, and where it came from. ZeroMark produces the first two before you ever see the card. It reads the post, the quoted post, the pictures, and the full text of a long post that truncates at the fold, and writes a summary and a reason. Those ride along on the export, so a row in Notion or a note in Obsidian is readable on arrival.

Step one: get the bookmarks read

1. Open ZeroMark and continue with . One authorization signs you in, connects your bookmarks, and starts the first sync.
2. Wait for the sync. A few hundred saves take minutes; the app checks again roughly hourly and whenever you open it, so new bookmarks keep landing without you doing anything.
3. Open Browse. Each save has a summary above the post and a line saying why it is in front of you. If a summary is still being written the card says so.

Nothing is exported yet, and that is deliberate. The next step is the one most tools skip.

Step two: decide, so only keeps travel

Go through the queue with one key per save. Done keeps it: the save goes into Living Memory and, if Notion is connected, becomes a row there. Let go removes it from the queue. Snooze brings it back in a week. A backlog of hundreds is an afternoon at this pace, because you are deciding from a summary rather than reading the post.

This is why the export is worth having. A Notion database of a thousand undecided bookmarks is a thousand rows you will filter once and never open. A database of the two hundred you kept, each with a summary, is something you will actually query.

Step three, Notion: a database that fills itself

1. Open the Memory tab and press Connect Notion.
2. On Notion's consent screen, pick the page your saves should live under. The connection is scoped to what you pick; nothing else in your workspace is visible to the app.
3. You land back in Memory with a Notion chip that links straight to the new database.

The database is created with these columns:

Two details worth knowing. Everything you had already kept before connecting is backfilled into the database, with Kept set to the day you actually decided it rather than today, so the history is true. And disconnecting Notion leaves the pages where they are: the database is yours, and disconnecting is not a request to delete it.

Once connected, there is no export step. Mark a save done and the row appears. Build whatever views you like on top: a board by Field, a table sorted by Kept, a filter on Author for the voices you keep coming back to.

Step three, Obsidian: markdown notes for a vault

Obsidian has no inbox to push into, so the route is a file. In the Memory tab, press Download for Obsidian. You get one markdown file, named with the date, containing your Living Memory notes. These are not one note per bookmark. They are the notes the app writes from what you kept, grouped by idea, each citing the saves it came from, and they are the shape a vault wants:

• Frontmatter on each note: a stable id, a type, aliases to search for, and the date it last changed.
• The page: a synthesis of what the kept saves say, with numbered citations.
• Your thoughts, if you wrote any on the note in the app.
• Held and No longer held: the claims the note currently makes, each with its source numbers and the date it has been held since, and the claims it used to make with the dates they were dropped, so an old fact reads as old instead of as current.
• Open tensions: real disagreements between the sources, when there are any.
• Linked notes as [[wiki links]], so Obsidian draws the graph.
• Sources: the handle and the link for every save the note came from.

Drop the file into your vault. Obsidian reads it as is, and the wiki links show up in the graph as links between the notes in the file. If you want each note as its own file, the file separates notes with a horizontal rule, so any note-splitting plugin cuts it cleanly on that line. Download again next month and you get the current state of every note, including what is no longer held, which is the part a plain bookmark export can never give you.

What to check after the first run

Doing it without ZeroMark

The honest alternative is three tools. Export your bookmarks with a browser extension to CSV or JSON, knowing the export stops at the retrieval ceiling for large collections. Run each link through a summarizer, which for hundreds of links means either a script or a paid tool that accepts a list. Then import the CSV into Notion or convert it to markdown for Obsidian, and accept that what arrives is every save, undecided, with a summary of the reaction rather than the quoted post it reacts to.

It works. It is also most of a weekend, and it produces the pile in a new place. The reason to decide first and export second is not tidiness. It is that the destination is only useful if what lands there is what you meant to keep.

Read next

• How to export your X bookmarks
• How to organize your X bookmarks
• Marqly vs Readwise vs ZeroMark: which to pick