The Typeform Notion integration: setup, field mapping and fixes

Typeform's Free plan article lists the features and integrations that are paid-only, and Notion is not on that list, so the native integration appears to be available on every plan. The practical limit is volume: the free plan collects 10 responses a month across all forms, and Basic 100. Check the Connect panel in your own account, since Typeform notes that it runs pricing experiments.

The bigger restriction is regional. Typeform's help centre says the Notion integration isn't available on accounts that host data in its EU Data Center. If your account is there, Zapier, Make or a webhook are your options.

It creates one new row per response. It doesn't update an existing row (say, to mark a returning lead), doesn't write into pages that aren't Table databases, and doesn't support Board, List, Calendar, Gallery or Timeline databases, or databases with multiple data sources. If your team works from a board, create the database as a table, point the integration at it, and add a board view to that same database afterwards.

There's also no built-in repair when the connection breaks. Typeform's help article says that if the Notion token expires or is deleted, the Webhooks panel shows a 401 "API token is invalid" error, and the only fix is to delete the integration and set it up from scratch. Responses submitted while it was broken stay in Typeform's Results; you'd copy them over by export.

Use an automation tool when you need anything the native integration doesn't do: a board-first database, a filter (only send leads over a budget), a lookup before creating the row, or an update to an existing row.

Create a Zap with Typeform's New Entry trigger and Notion's Create Data Source Item action, pick the database, and map each property to a Typeform answer. Zapier's free plan allows 100 tasks a month and two-step Zaps, and neither Typeform nor Notion is marked as a premium app, so a basic Typeform-to-Notion Zap runs free up to about 100 responses a month. Adding a filter or formatter step makes it a multi-step Zap, which needs Pro ($19.99 a month billed yearly, $29.99 monthly, for 750 tasks).

Zapier also offers Update Data Source Item, which is the route if you want a second form to update a row the first form created.

In Make, a scenario starts with a Typeform module that watches responses and ends with a Notion module that creates a database item. Make's free plan includes 1,000 credits a month and each module action uses a credit, so a two-module scenario covers several hundred responses a month; note the free plan's 15-minute minimum interval between scheduled runs. The paid Make plan starts at $9 a month for 5,000 credits. Make is the cheaper option at volume and better for branching, but its editor takes longer to learn than Zapier's.

Give the title property something human: the respondent's name, company or ticket subject, so the table reads like a list of people rather than timestamps. Add a Status property you fill by hand (New, In review, Done) instead of asking the form for it, and keep form-fed properties separate from team-managed ones so nobody overwrites a submitted answer.

Add a created time property for sorting; it fills itself. For campaigns, store utm_source and utm_campaign from hidden fields in Select properties so you can group by them. Our UTM builder at /tools/utm-builder makes tagged links for that.

Zunoform has a native Notion integration on the Pro plan ($14.99 a month). You connect Notion, choose which pages Zunoform can access, and pick the database. Mapping works by name rather than through a mapping screen: each answer goes into the database property named like the question (capitals and extra spaces are ignored), converted to that property's type (text, number, select, multi-select, date, email, phone, URL or checkbox). Hidden fields such as utm_source fill same-named properties too. The title property can have any name; it gets the form name and submission date unless a question shares its name.

The page body also lists every answer as "Question: answer", so anything without a matching property is still kept, including file uploads and property types the Notion API can't write, such as people, relation, status and formula. New select options are added if the connection can edit the database, and if Notion rejects a value the page is saved without that property instead of failing. Typeform's native integration is the better choice if you want to pick question-to-column pairs by hand, or to write file uploads into a Files property. Moving across is quick: our importer rebuilds a Typeform form from its link.