← Registry

Second brain daily capture

Every evening, turn flagged email, meetings and chats into linked notes in your drive.

By DamonVersion 10 installsUpdated Sep 30, 2026

Connects ToGmailGmailFireflies

What it does

Every evening at 18:00 the workflow reads the conventions in Brain/README.md, then captures the day's sources: emails you labeled Brain in Gmail, Fireflies transcripts from the last 24 hours, anything you dropped in Brain/Inbox/, and your chats with Damon (facts recalled from today's conversations, plus past threads on each topic in Brain/Maps/). Each source gets a note in Brain/Sources/; sources that already have one are skipped. It then creates or updates permanent notes in Brain/Notes/ (one idea per note, titled as a claim, each listing its sources) and adds them to topic maps in Brain/Maps/. It opens a chat thread with what changed.

It only reads Gmail and Fireflies, and only writes to Brain/. It never deletes notes.

What you need

  • Gmail and Fireflies connected.
  • A Brain label in Gmail for emails worth keeping.
  • A Brain/README.md in your drive with your conventions (ask Damon to create one).

Customize it

  • Auto-approve file.write for this workflow so the evening run doesn't wait on you.
  • Add Slack messages you've reacted to as another source.
  • Pair it with the Second brain weekly upkeep template to keep the notes tidy.

What It Does, Step by Step

  1. Step 1Trigger

    Runs every day at 6:00 PM (America/New_York)Runs every day at 18:00.

  2. Step 2Agent

    Maintain the second brain in the Brain folder of the drive. First read Brain/README.md and follow its conventions; if it is missing, use these: Brain/Inbox for quick captures, Brain/Sources for one note per source, Brain/Notes for permanent notes, Brain/Maps for topic maps. Capture today's sources: (1) Gmail emails labeled Brain from the last 24 hours; (2) Fireflies transcripts completed in the last 24 hours; (3) files in Brain/Inbox; (4) chats: recall memory facts from today's conversations, and search past chat threads for each topic that has a map in Brain/Maps. Skip any source that already has a note in Brain/Sources (match on date and title). For each new source write Brain/Sources/<YYYY-MM-DD>-<email|meeting|chat|inbox>-<title>.md with a short summary, the key points quoted or closely paraphrased, and a reference back to the original (sender and subject, meeting title, or chat thread). Move processed Inbox files into Brain/Sources. Then distill: for each idea, decision or fact worth keeping, update the existing note in Brain/Notes that covers it, or create Brain/Notes/<YYYYMMDDHHmm>-<claim-slug>.md titled as a full-sentence claim containing one idea in plain language and a Sources list naming each source with its date. When a new source supports an existing note, add it to that note's Sources rather than creating a new note. Add every new note to the maps it belongs in; create a map in Brain/Maps when three or more notes share a topic, with a one-paragraph summary of current thinking and the list of notes. Never invent facts, never delete a note. Report the sources captured, and the notes and maps you created and updated.

    UsesGmailFireflies
  3. Step 3Send a Message

    Open a thread titled "Second brain" with today's date. List the sources captured by type with counts, the new notes and updated notes with one line each, and any new maps. If nothing was captured, post one line saying so.

More from Damon

See All

WorkflowProductivity

Daily inbox digest

Every morning, summarize what landed in your inbox and flag what needs a reply.

Gmail

Damon

WorkflowSales

Monday pipeline review

Every Monday, list the deals that have gone quiet and suggest a next step for each.

HubSpot

Damon

WorkflowProductivity

Weekly status report

Every Friday, write the project status report from your project tool and offer to post it.

Linear

Damon