How to Turn Notion Meeting Notes into an Action Database
Action DBs invent due dates. Extract verbs from the notes. Leave Owner UNKNOWN when blank.
The matching generator is the Notion Meeting Notes to Action Database Schema prompt. Browse related cards in the PromptDig library (Browse more prompts). When a filled run survives, share the version you actually use (Share a prompt).
Extract actions only from the pasted notes
Turn pasted meeting notes into a Notion action database schema with properties and views. Never invent owners or due dates. Start by filling Inputs, not by asking the model to remember last week's run. If a field is blank, write NONE or NOT IN INPUTS and leave it blank through Generate. The card is built so the model cannot honestly invent a number, owner, URL, or command that you did not paste.
Paste these fields before you hit run:
Meeting notes paste: [Notes]
Property list I allow (or DEFAULT): [Props]
View names I allow: [Views]
Words I must not use: [Banned]
What I must never invent: [Never]
Output format: [Format]
Language: [Lang]
That inventory is the honesty ledger. Anything that does not appear there is forbidden in the draft. If you catch yourself adding a nice-to-have after the run, you are no longer using the card. You are ghostwriting. Put the extra fact in Inputs and run again.
Define properties without inventing people
Generate is numbered on purpose. Do not skip a step because the first paragraph looked done. The early steps exist to stop later prose from smuggling claims.
Walk the Generate list in order:
- Honesty ledger: Notes nouns, Props, Views, Lang. Forbidden: invent owners, invent due dates.
- Extract candidate actions quoted from Notes only.
- Database properties: Title, Status, Owner, Due, Source note. Owner/Due blank if missing -> UNKNOWN.
- Select options only from words in Notes or Props.
- Views: only Views named. Filters described without inventing people.
- Sample rows: one row per extracted action; missing fields UNKNOWN.
- Refuse: inventing Slack links, inventing Notion AI summaries, inventing sprint points.
- Compliance pass: Banned and Never. Format as Format.
If a step asks for a version lock, quote the version from Inputs in the output. If a step asks for a refuse list, keep the refuse list in the published artifact, not in a sidebar you delete. Reviewers should see what the model was not allowed to do.
Build views from the allowed names
Most failures are the same shape: a missing field gets a confident fill. A conversion rate appears. A Gradle task appears. A flash point appears. A caption appears on a job that asked for slide text only. Your review is to search the draft for numbers, names, and commands, then grep Inputs. No match means cut.
Honor the constraints as hard stops, not vibes:
- Schema from Notes only. Not a Jira import.
- Never invent owners or due dates.
- Keep UNKNOWN when blank.
- No emojis.
When the card says not legal advice, not certification, not an exam dump, or not a caption engine, that sentence belongs at the top of the output. Deleting it to look more finished is how you inherit risk.
Refuse invented Slack links and story points
Finish with the compliance pass the prompt already asks for. Quote the banned-word hits. Cut them. Print character counts when the job has a cap. Print word counts when the job has a budget. List gaps as gaps. Five missing facts are more useful than one smooth paragraph.
Tags on the card (notion meeting notes action database, notion action items schema, meeting notes to notion db) are a reminder of the job shape, not an invitation to wander into a neighboring cluster. If you need a different surface, open a different PromptDig card rather than stretching this one.
Fill the card, then run
Replace every bracket. Run on ChatGPT, Claude, or Gemini. Read the ledger first, then the artifact. If the model invents a commit, KPI, DOI, PEL, bid, or logo, discard the run. Tighten Inputs. Run again. Share the filled card that survived, not the first draft that sounded done.