Notion property types reference
Supported Notion property types and how they map to external fields
2sync supports 20 Notion property types for field mapping. Some are writable (2sync can update them), while others are read-only (set automatically by Notion). Understanding each type helps you configure accurate, reliable automations.
What Notion property types does 2sync support?
Every property type available in Notion is listed below with its sync behavior and recommended use cases.
What are the writable property types?
These properties can be updated by 2sync during a sync cycle.
| Property Type | Description | Best For |
|---|---|---|
| Title | Page title (required on every database) | Event names, task titles, contact names |
| Rich Text | Formatted text content | Descriptions, notes, email body |
| Number | Numeric values | Priority levels, counts |
| Select | Single choice dropdown | Calendar names, categories, status labels |
| Multi-select | Multiple choice tags | Labels, attendees list, categories |
| Status | Workflow status with groups | Task completion, sync state tracking |
| Date | Dates with optional start/end times | Event dates, due dates, birthdays |
| Checkbox | True/false toggle | Completion status, recurring event flag |
| URL | Web links | Meeting links, email permalinks |
| Email addresses | Contact emails, sender addresses | |
| Phone Number | Phone numbers | Contact phone fields |
| People | Notion workspace users | Assignees (limited to workspace members) |
| Files | File attachments | Attachment metadata |
| Relation | Links to rows in other databases | Attendees to contacts, tasks to projects |
Select properties work best for fields with a fixed set of values like calendar names or categories. 2sync automatically creates new options when it encounters values that do not exist yet.
What are the read-only property types?
Notion sets these automatically. 2sync can read them for one-way sync to external apps but cannot write to them.
| Property Type | Description | Use Case |
|---|---|---|
| Rollup | Aggregated data from related databases | Summarize linked records |
| Formula | Computed values from other properties | Combine fields for sync (e.g., full name) |
| Created Time | Timestamp when page was created | Reference only |
| Created By | User who created the page | Reference only |
| Last Edited Time | Timestamp of last modification | Reference only |
| Last Edited By | User who last modified the page | Reference only |
How to choose the right property type
For calendar names: Use Select. Each calendar becomes a dropdown option, keeping values consistent.
For event dates: Use Date with time enabled. 2sync maps start and end times automatically.
For attendees: Use Relation linked to a contacts database. 2sync matches attendees by email address.
For descriptions: Use Rich Text. Formatting from the external app is preserved where possible.
For completion tracking: Use Checkbox or Status. Checkbox is simpler; Status gives you grouped workflow stages.
Prefer Status over Checkbox for completion tracking when you need workflow stages like "Not Started," "In Progress," and "Done." Checkbox only supports checked/unchecked, while Status lets you group items by workflow stage in Notion views.
Why are some properties read-only?
Notion enforces read-only behavior on computed and auto-generated properties. Formula and Rollup values are calculated by Notion itself, so no external tool can write to them. Created Time and Created By are immutable records.
You can still use read-only properties in one-way sync from Notion to your external app. For example, map a Formula that combines first and last name to an event title.
For formulas that reference Relation or Rollup properties, the linked database must also be connected to 2sync. Without access, the formula returns empty values.
What are common mapping mistakes?
Using Text instead of Select for calendar names: Text fields allow freeform input, which leads to inconsistent values ("Work", "work", "Work Calendar"). Use Select so values are constrained to predefined options and 2sync can match them reliably.
Using People instead of Relation for attendees: People properties only reference Notion workspace members. External attendees (clients, partners) cannot be represented. Use a Relation to a Contacts database instead, which supports any email address.
Mapping a formula property as two-way: Formulas are computed by Notion and cannot be written to. If you map a formula, set the direction to one-way from Notion to the external app. Two-way mapping causes the external app's value to be ignored.
Related
- Sync direction for understanding how direction affects writable vs read-only behavior
- Relations for linking databases using Relation properties
- Default values for setting defaults on specific property types
- Google Calendar fields for which property types each calendar field supports
- Todoist fields for which property types each Todoist field supports
FAQ
Can I map a Formula property to an external field?
Yes, but only in the one-way direction from Notion to the external app. Formulas are computed by Notion and cannot be written to by 2sync or any other tool.
What happens if a Select option does not exist yet?
2sync creates the option automatically when it encounters a new value from the external app. The new option appears in your Select dropdown.
Which property type should I use for attendees?
Use a Relation property linked to a contacts database. 2sync matches attendees by email address and creates the relation automatically. This gives you a connected CRM-style setup.
Can I sync People properties with external contacts?
People properties only reference Notion workspace members, not external contacts. For external contacts, use a Relation to a contacts database or an Email property instead.
How can I set an item title with a Notion formula?
Map your Formula property to the title field and set the sync direction to one-way from Notion to the external app. Since formulas are read-only (computed by Notion), they can only push values outward. This is useful for combining fields like first and last name into a single calendar event title.