---
title: "Notion"
description: "Append accepted responses as pages in a Fillo-created Notion database."
group: "Deliver & operate"
order: 1
type: "integration"
parent: "integrations"
keywords:
  - "Notion"
  - "database"
  - "response destination"
  - "field mapping"
updated: "2026-07-21"
---

The Notion integration appends each accepted response as a page in a Fillo-created database.

## What syncs

Fillo creates the database under a page shared during the OAuth connection. Each response includes a title, submitted date, Fillo response ID, **Fillo Event** select, and one property per form field. Fillo Event is **Created** for the original accepted response and **Updated** for a later in-place edit. You can choose which field supplies the page title; otherwise Fillo uses the first non-empty formatted answer.

| Fillo field | Notion property | Notes |
| --- | --- | --- |
| Delivery event | Fillo Event | Select value: `Created` or `Updated` |
| Number, rating, linear scale | Number | Stored as a finite number |
| Calculated | Number | The server-computed value, rounded to the field's decimals; prefix and suffix are display-only and stay off the number |
| Select, dropdown | Select | Uses the visible option label |
| Checkbox | Checkbox | Boolean value |
| Date | Date | Uses the submitted calendar date |
| Email | Email | Capped to Notion's supported value shape |
| URL | URL | Written as a URL property |
| Phone | Phone number | Written as a phone property |
| Other field kinds | Rich text | Uses Fillo's formatted answer, capped at 2,000 characters |

File uploads, multi-selects, matrices, rankings, signatures, and custom values don't become specialized Notion property types — they're formatted into rich text. Files stay in the workspace's connected storage.

## Connect Notion

1. Open **Settings > Connections** and connect Notion.
2. Share the destination parent page with the Fillo integration during the Notion flow.
3. Open the form's **Settings > Response destinations**.
4. Enable **Notion**.
5. Optionally choose a **Notion title** field.
6. Submit a test response and open the generated database.

## Code-defined forms

Keep the form schema in code, sync and publish it, then create the destination in the dashboard. OAuth credentials and the selected Notion parent page stay workspace settings. Keep field IDs stable after the database property map is created.

## Delivery behavior and limits

Notion delivery is append-only: updating a Fillo response creates another page marked **Updated** instead of editing the first **Created** page. Existing databases gain the Fillo Event property automatically on their next delivery; an owner-created property named Event remains untouched. The Fillo response ID lets a failed creation retry detect a page that already committed, but external delivery is still at least once.

Notion API rate limits, access rules, archived pages, and workspace plan limits apply independently. The Fillo integration is available on every Fillo plan. Disabling it doesn't delete the database or pages already created.

## Troubleshooting FAQ

### Why can't Fillo create the database?

Reconnect Notion and share a page with the integration. A connection without an accessible parent page can't create a database.

### Why is a field rich text instead of a native property?

Only the field mappings in the table have direct Notion property types. Use the formatted text, or transform the response through Zapier or a webhook when the destination needs a different shape.

### Why did an update create another page?

The current integration is append-only. Group pages by Fillo Response ID when they represent the same response over time.

## Related

- [Delivery health and replay](/docs/delivery-health): Repair and replay a failing Notion destination.
- [Fields](/docs/fields): Check the stored value behind each property mapping.
- [Zapier](/docs/integrations/zapier): Transform the response before writing to another app.