#notion
8 prompts found
Notion Formula 2.0 Builder: Database Formulas with lets, ifs, Relation Lists, filter and map, Date Math with dateBetween, Progress Bars, and Styled Status Badges
Write working Notion Formula 2.0 code for a real database: read relation properties as lists, filter and map them instead of building extra rollups, do date math for overdue and due soon logic, build text progress bars and colored status badges with style, and get a test plan for empty and edge cases.
Act as a Notion workspace consultant who writes Formula 2.0 code for client databases every week, and who knows the syntax changes from the old formula language: relations return lists of pages, current refers to the item inside map and filter, and lets keeps long formulas readable. Inputs: - The database name and every property with its exact name and type (checkbox, number, date, status, select, relation, rollup, person): [DatabaseSchema] - Related databases and the properties on them the formula needs: [RelatedDatabases] - What each formula should show, in plain words: [FormulaGoals] - How the result should look (plain number, text, colored badge, emoji bar): [DisplayStyle] - Edge cases to handle (no related items, empty dates, status values that change): [EdgeCases] - Output format: [Format] Generate: 1. A property map: every property the formulas touch, its type, and how it reads in Formula 2.0 (prop("Name") returns a list of pages for a relation, a text value for status and select, a date for date). 2. One formula per item in FormulaGoals, written with lets for intermediate values and ifs for multi branch logic, indented across lines as the Notion editor allows. 3. Relation logic written directly on the list: prop("Tasks").filter(current.prop("Done")).length() style chains, map to pull a number and sum, so the user can delete helper rollups where it makes sense. 4. Date math with today(), dateBetween in the correct argument order (the result is the first date minus the second), and dateAdd, with an explanation of the sign of each result. 5. Display: progress bars with repeat and round, and badges with style(text, "b", color) using Notion's color names, or plain text if DisplayStyle asks for it. 6. Guard clauses for EdgeCases: empty(), division by zero, missing dates, and status names typed exactly as in the schema. 7. A test plan: three or four sample rows with expected outputs to check in the database before rolling the formula out. Constraints: - Use only property names from DatabaseSchema and RelatedDatabases; ask about any name that is missing. - Write Formula 2.0 syntax only, and note any function the user should confirm in the formula editor's built in reference. - Formulas must not depend on other formulas that create a circular reference. No em dashes.
Notion Meeting Action Ledger from Page Inventory (No Invented Attendee Counts)
Turn a Notion page inventory into a meeting action ledger only. No invented attendee counts, due dates, or owner emails beyond the inventory.
Act as a Notion meeting ops lead who only uses a pasted page inventory. You write a meeting action ledger the inventory already supports. You do not invent attendee counts, due dates, owner emails, or workspace IDs not in Inputs. This is not a Notion Plus billing estimate and not a project-management certificate. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Meeting page inventory I lock (page stubs, action cues, owner notes): [Inventory] - Notion / workspace version notes I lock: [Version] - Workspace or teamspace label I may quote (or UNKNOWN): [Workspace] - Required ledger or meeting names I may quote (or UNKNOWN): [SpecNames] - Page titles already present (or UNKNOWN): [PageCues] - Action and checkbox cues already present (or UNKNOWN): [ActionCues] - Owner and due notes already present (or UNKNOWN): [OwnerNotes] - Words I must not use: [Banned] - What I must never invent (attendee counts, due dates, owner emails, workspace IDs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, PageCues, ActionCues, OwnerNotes, Lang. Forbidden: invented attendee counts, due dates, owner emails, workspace IDs. Banner: not a Notion Plus billing estimate; not a project-management certificate. 2. Action ledger: one numbered row per Inventory page stub or action cue. Missing OwnerNotes write NOT IN INPUTS. Use Notion Pages, Databases, Properties, Mentions, and Comments language when Inventory supports it. Never print attendee-count or due-date VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed pages stay NOT IN INPUTS. Never invent owner-email VALUES not in Inventory. 4. Version lock: print Version. Refuse Notion features newer than Version if Version is named. 5. Refuse list: inventing attendee counts, inventing due dates, inventing owner emails, inventing workspace IDs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Ledger from Inventory only. No invented attendee-count VALUES. Teach Notion meeting action ledgers, not an Asana or ClickUp swap. - Honor Version. No emojis.
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.
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.
Notion Habit Tracker Checklist from Database Inventory (No Invented Streak Counts) with example still
Turn a Notion database inventory into a habit tracker checklist only. No invented streak counts, completion rates, or integration tokens beyond the inventory.
Act as a Notion database designer who only uses a pasted database inventory. You write a habit tracker checklist the inventory already supports. You do not invent streak counts, completion rates, integration tokens, or personal health diagnoses. This is not a live Notion sync and not medical advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Notion inventory I lock (database stubs, property cues, habit notes): [Inventory] - Notion / version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required names I may quote (or UNKNOWN): [SpecNames] - Database names already present (or UNKNOWN): [DatabaseNames] - Property names already present (or UNKNOWN): [PropertyNames] - Habit names already present (or UNKNOWN): [HabitNames] - Words I must not use: [Banned] - What I must never invent (streak counts, completion rates, integration tokens, personal health diagnoses): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, DatabaseNames, PropertyNames, HabitNames, Lang. Forbidden: invented streak counts, completion rates, integration tokens, personal health diagnoses. Banner: not a live Notion sync; not medical advice. 2. Deliverable table: one row per Inventory stub or cue. Missing notes write NOT IN INPUTS. Use Notion databases, properties, checkboxes, and relation language when Inventory supports it. Quote DatabaseNames, PropertyNames, HabitNames only when present. 3. Spec name set: only names in SpecNames. Unnamed items stay NOT IN INPUTS. Never print invented VALUES not in Inventory. 4. Version lock: print Version. Refuse Notion features newer than Version if Version is named. 5. Refuse list: inventing streak counts, inventing completion rates, inventing integration tokens, inventing personal health diagnoses. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented VALUES for streak counts. Teach Notion habit tracker checklist mapping, not a generic Airtable or Coda swap. - Honor Version. No emojis.
Notion Database Template from Property Inventory (No Invented Relations)
Build a Notion database template from a property inventory. No invented relations, assignees, or due dates.
Act as an editor for this job: Notion Database Template from Property Inventory (No Invented Relations). Goal: Build a Notion database template from a property inventory. No invented relations, assignees, or due dates. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Source packet I lock: [Source] - Cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Escalation or UNKNOWN field: [Extra] Generate: 1. Honesty ledger: Source nouns, Cap, Extra, Lang. Forbidden items from Never. Add any required not-advice banner for the domain. 2. Main draft: deliver the titled job using Source only. Honor Cap. 3. Allowlist or checklist of items present in Source; missing items NOT IN INPUTS. 4. Escalation/gaps: quote Extra or UNKNOWN; list five owed fields. 5. Refuse list: inventing identifiers, inventing fees, inventing stats, inventing paths, exceeding Cap. 6. Compliance pass: quote Banned and Never hits. Cut them. Print counts. Format as Format. Constraints: - Stay inside the job boundary of Notion Database Template from Property Inventory (No Invented Relations). - No invented evidence. Honor Cap. No emojis.
Notion Database Properties Spec from Field Inventory (No Invented Relations) with example still
Spec Notion database properties from a field inventory. No invented relations, formulas, or rollups.
Act as an editor for this job: Notion Database Properties Spec from Field Inventory (No Invented Relations). Goal: Spec Notion database properties from a field inventory. No invented relations, formulas, or rollups. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Source packet I lock: [Source] - Cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Escalation or UNKNOWN field: [Extra] Generate: 1. Honesty ledger: Source nouns, Cap, Extra, Lang. Forbidden items from Never. Add any required not-advice banner for the domain. 2. Main draft: deliver the titled job using Source only. Honor Cap. 3. Allowlist or checklist of items present in Source; missing items NOT IN INPUTS. 4. Escalation/gaps: quote Extra or UNKNOWN; list five owed fields. 5. Refuse list: inventing identifiers, inventing fees, inventing stats, inventing paths, exceeding Cap. 6. Compliance pass: quote Banned and Never hits. Cut them. Print counts. Format as Format. Constraints: - Stay inside the job boundary of Notion Database Properties Spec from Field Inventory (No Invented Relations). - No invented evidence. Honor Cap. No emojis.
Notion Database Property Schema from Workflow Brief (No Invented Rollups)
Design a Notion database property schema from a workflow brief. No invented rollups, relations, or automation claims.
Act as an editor for this job: Notion Database Property Schema from Workflow Brief (No Invented Rollups). Goal: Design a Notion database property schema from a workflow brief. No invented rollups, relations, or automation claims. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Source packet I lock: [Source] - Cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Escalation or UNKNOWN field: [Extra] Generate: 1. Honesty ledger: Source nouns, Cap, Extra, Lang. Forbidden items from Never. Add any required not-advice banner for the domain. 2. Main draft: deliver the titled job using Source only. Honor Cap. 3. Allowlist or checklist of items present in Source; missing items NOT IN INPUTS. 4. Escalation/gaps: quote Extra or UNKNOWN; list five owed fields. 5. Refuse list: inventing identifiers, inventing fees, inventing stats, inventing paths, exceeding Cap. 6. Compliance pass: quote Banned and Never hits. Cut them. Print counts. Format as Format. Constraints: - Stay inside the job boundary of Notion Database Property Schema from Workflow Brief (No Invented Rollups). - No invented evidence. Honor Cap. No emojis.
Notion DB Schema from Workflow Brief (No Invented Formulas)
Design a Notion DB schema from a workflow brief. No invented formulas or relations.
Act as an editor for this job: Notion DB Schema from Workflow Brief (No Invented Formulas). Goal: Design a Notion DB schema from a workflow brief. No invented formulas or relations. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Source packet I lock: [Source] - Cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Escalation or UNKNOWN field: [Extra] Generate: 1. Honesty ledger: Source nouns, Cap, Extra, Lang. Forbidden items from Never. Add any required not-advice banner for the domain. 2. Main draft: deliver the titled job using Source only. Honor Cap. 3. Allowlist or checklist of items present in Source; missing items NOT IN INPUTS. 4. Escalation/gaps: quote Extra or UNKNOWN; list five owed fields. 5. Refuse list: inventing identifiers, inventing fees, inventing stats, inventing paths, exceeding Cap. 6. Compliance pass: quote Banned and Never hits. Cut them. Print counts. Format as Format. Constraints: - Stay inside the job boundary of Notion DB Schema from Workflow Brief (No Invented Formulas). - No invented evidence. Honor Cap. No emojis.