Productivity

Notion Database Property Map from Workspace Inventory (No Invented Row Counts)

Turn a Notion workspace inventory into a database property map only. No invented row counts, formula results, or integration tokens beyond the inventory.

0.0
0Reviews
P
September 14, 2026

Prompt

Act as a Notion workspace database cartographer who only uses a pasted workspace inventory. You write a database property map the inventory already supports. You do not invent row counts, formula results, relation targets, or integration tokens not in Inputs. This is not a Notion billing estimate and not a migration guarantee.
You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs.

Inputs:
- Notion workspace inventory I lock (database stubs, property cues, relation notes): [Inventory]
- Notion / API version notes I lock: [Version]
- Workspace or page label I may quote (or UNKNOWN): [Workspace]
- Required database names I may quote (or UNKNOWN): [SpecNames]
- Database titles already present (or UNKNOWN): [DbTitles]
- Property cues already present (or UNKNOWN): [PropCues]
- Relation and rollup notes already present (or UNKNOWN): [RelationNotes]
- Words I must not use: [Banned]
- What I must never invent (row counts, formula results, relation targets, tokens): [Never]
- Output format: [Format]
- Language: [Lang]

Generate:
1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, DbTitles, PropCues, RelationNotes, Lang. Forbidden: invented row counts, formula results, relation targets, integration tokens. Banner: not a Notion billing estimate; not a migration guarantee.
2. Database property map table: one row per Inventory database stub or property cue. Missing RelationNotes write NOT IN INPUTS. Use Notion databases, properties, relations, and rollups language when Inventory supports it. Never print row-count or formula-result VALUES not in Inventory.
3. Spec name set: only names in SpecNames. Unnamed databases stay NOT IN INPUTS. Never invent integration-token VALUES not in Inventory.
4. Version lock: print Version. Refuse Notion API features newer than Version if Version is named.
5. Refuse list: inventing row counts, inventing formula results, inventing relation targets, inventing integration tokens.
6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format.

Constraints:
- Map from Inventory only. No invented row-count VALUES. Teach Notion database property mapping, not a generic Airtable or Coda swap.
- Honor Version. No emojis.

Instructions

Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.

Generated Output

This image was generated using the prompt above.

Notion Database Property Map from Workspace Inventory (No Invented Row Counts) - Result

Examples

Example Input

Inventory: database Harbor Quay Tasks as pasted property cue Status select as pasted relation notes links to Projects as pasted; database River Ops Projects as pasted property cue Owner person as pasted. Row invent NONE. Formula invent NONE.
Version: Notion API 2022-06-28 as pasted (do not invent unreleased AI property writer)
Workspace: Harbor Quay Ops wiki as pasted
SpecNames: Tasks as pasted; Projects as pasted. IntegrationToken UNKNOWN.
DbTitles: Tasks as pasted; Projects as pasted. Meetings UNKNOWN.
PropCues: Status select as pasted; Owner person as pasted. Due date UNKNOWN.
RelationNotes: links to Projects as pasted. rollup task count NOT IN INPUTS.
Banned: guaranteed sync, row invent, formula invent, token invent
Never: invent row counts, invent formula results, invent relation targets, invent integration tokens
Format: ledger + table + specs + version + refuse + compliance
Lang: English

Example Output

1. Ledger. Inventory: database Harbor Quay Tasks property cue Status select relation notes links to Projects; database River Ops Projects property cue Owner person. Row invent NONE. Formula invent NONE. Version Notion API 2022-06-28. Workspace Harbor Quay Ops wiki. SpecNames Tasks; Projects; IntegrationToken UNKNOWN. DbTitles Tasks; Projects; Meetings UNKNOWN. PropCues Status select; Owner person; Due date UNKNOWN. RelationNotes links to Projects; rollup task count NOT IN INPUTS. Lang English. Banner: not a Notion billing estimate; not a migration guarantee. Forbidden: invented row counts, formula results, relation targets, integration tokens, guaranteed sync, row invent, formula invent, token invent.

2. Database property map.
1. Harbor Quay Tasks | DbTitles Tasks as pasted | PropCues Status select as pasted | RelationNotes links to Projects as pasted | rows NONE | formula NONE | Notion database property map only.
2. River Ops Projects | DbTitles Projects as pasted | PropCues Owner person as pasted | RelationNotes beyond links to Projects NOT IN INPUTS | rows NONE | formula NONE.
IntegrationToken UNKNOWN so write IntegrationToken NOT IN INPUTS. Meetings not invented beyond DbTitles.

3. Spec name set. Tasks; Projects as SpecNames. IntegrationToken UNKNOWN so write IntegrationToken NOT IN INPUTS. No row-count VALUES beyond Inventory. No third database invented.

4. Version lock. Notion API 2022-06-28 as pasted. Unreleased AI property writer not used. Template packs NOT IN INPUTS.

5. Refuse. Row invent: refused. Formula invent: refused. Relation invent: refused. Token invent: refused. Guaranteed sync: refused.

6. Compliance. Banned hits none. Format ledger+table+specs+version+refuse+compliance. Gaps: IntegrationToken decision, Meetings DbTitles, Due date PropCues, rollup task count RelationNotes, template packs list if any.

Missing-data policy: if a field was blank, write NOT IN INPUTS rather than guessing. Lock any tool version named in Inputs; if unnamed, write unknown. No invented testimonials, star ratings, or press logos. If legal, clinical, insurance, HR, education-plan, or veterinary content appears, add a one-line not-advice and de-identify banner. Quote banned-word hits and cut them. End with a gaps list of five bullets the user still owes you. Character and byte caps in the job are hard; print counts when relevant. Refuse to backfill DOIs, exam dumps, PHI, PII, or compensation promises not in Inputs.

Reviews (0)

Please login to leave a review.
Loading reviews...