Notion
Create a page using the destination’s actual property schema. Supply an integration token and either a current Data Source ID or a legacy single-source Database ID. The integration needs read and insert access to that destination.
A current data source uses Notion API version 2025-09-03. Legacy database IDs use 2022-06-28 for compatibility. No database-picker UI or automatic property creation is claimed.
Map one form_field=Property Name per line. An explicit map is an allowlist. With no map, existing property names are matched first exactly, then by a unique case-insensitive match. The title property is discovered, and a mapped name correctly becomes title content rather than replacing it with rich text.
Supported types: title, rich text, number, checkbox, email, phone, URL, select, status, multi-select, date, and relations/people supplied as IDs. Computed and unsupported properties produce a configuration error. Long text is split into supported rich-text property chunks; page-body blocks are not created.
Schema metadata is cached for two minutes. HTTP/authentication/validation errors are recorded. Transient failures can be retried through the action queue; see delivery behavior.
Mapping example
Create corresponding properties in the destination and configure:
NAME=Name
EMAIL=Email
SCORE=Score
CONSENT=Consent
INTERESTS=Interests
Use Title for Name, Email for Email, Number for Score, Checkbox for Consent, and Multi-select for Interests. A normal form field named NAME can supply the title without corrupting its property type.
Settings
| Setting | Purpose |
|---|---|
| Integration token | Token authorized to read the destination and insert pages |
| Database ID | Legacy single-source destination; optional when Data Source ID is supplied |
| Data source ID | Current destination; takes precedence over Database ID |
| Field mapping | Optional allowlist of form fields and destination property names |
| Run in the background | Queue using the saved submission; otherwise execute immediately |
Troubleshooting
- Share the destination with the integration and grant read/insert capabilities.
- Use a data source ID for databases containing multiple data sources.
- Property names in an explicit map must exist. Core Forms does not create properties.
- Use numeric values for Number, true/false or 1/0 for Checkbox, and ISO dates for Date.
- Use IDs when mapping relations or people. Computed properties cannot be written.
- Schema changes can take up to two minutes to leave the local metadata cache.
- Review the action log for authentication, mapping, or provider failures before retrying.