Notion property types

Canonical field map. This is what NotionApps stores after sync, what users can edit, and what stays read-only. Product help for formulas/rollups still has its own page; this page is the catalog.

What this is / when to use it

Every linked database property becomes a sheet field. The builder picker, inputs, and view components all use this map. If a property “is missing” or “won’t save,” start here, then Reload and sync.

Before you start

The database is shared with the NotionApps integration and has been synced at least once.

The map (`NotionFieldTypeToSheetFieldType`)

Notion property	Becomes in NotionApps	Typical component	Notes
Title	Text	Text / Heading	Required by Notion for a page.
Rich text	Text	Text or Long text
Email	Email	Text + validate email
Phone	Phone	Text + validate phone
URL	URL	Show URL / Button `OPEN_URL`
Number	Number	Number `SIMPLE` or `STEP`
Checkbox	Toggle	Toggle / Show toggle
Select	Options	Dropdown or Radio
Multi-select	Options	Multi-select
Status	Options	Dropdown or Radio
Date	Date	Date `DATE` / `TIME` / `DATE_TIME`
Created time	Date	View only	Not writable.
Last edited time	Date	View only	Not writable.
People	Text	View, or User input	Stored as a comma-separated string. Not a live Notion people widget.
Created by	Text	View	Not writable.
Last edited by	Text	View	Not writable.
Files	URL	Image / video / file / gallery	Uploads still work; the stored field type is URL.
Unique id	Text	Unique ID chip	Display / copy.
Formula	Text	View / Metric card	Read-only.
Rollup	Text	View / Metric card	Read-only. Nested rollups may not appear.
Relation	Reference	Reference `NONE` / `DIRECT` / `SELECTION`

Read vs write

Writable when the integration may update the page:

title, checkbox, date, email, files, multi_select, number, people, phone_number, relation, rich_text, select, status, url.

Not writable (display only): formula, rollup, created_time, last_edited_time, created_by, last_edited_by, unique_id (treat as display).

People is writable as text in this map. Prefer the User component when you mean an app user.

Nested formula / rollup / projection

A rollup that points at a relation’s formula may not appear in the builder. That is the “some rollup properties do not show up” case.
A rollup that returns an array may display as text, not a number. Metric cards need a numeric result.
Relation projections in the logic picker can show as disabled. See the troubleshooting page for relation logic.

Do not build a second “nested rollup” URL. Expand this section if you add more cases.

Build it

You do not “turn on” the map. After you add or rename a property in Notion:

Sync.
Confirm the property appears with the type above.
Bind a matching component. Do not bind an input to a read-only type.

What users see

They see components, not Notion type names. A people property looks like text unless you used a User picker. A unique id looks like a chip if you added one.

Limits and plans

Property count meters apply per plan. See Plans.
Changing a Notion type (select → status, files → url) can orphan builder components and cause save failed / NoFieldInSheet.
Two-way sync frequency is a plan meter; it does not change this map.

Example

A Deliveries database: Title, Status, Date, Files (attachments), People (client — stored as text), Relation to Scopes, Formula “days late”, Unique id.

In the app: Text title, Options status, Date, File upload, User (app user) or view-text for the Notion people string, Select Items for scopes, Metric/view for the formula, Unique ID chip. No input on the formula.

Fix problems

Symptom	Likely cause	What to do
People picker missing	Mapped as text	Use User input + Users database.
Files component gone after sync	Type changed in Notion	Restore files, or rebind.
Formula input does nothing	Read-only	Use view.
Builder cannot save	Component bound to a missing field	Save failed.

Reload and sync. Formulas & Rollups. Relations.