Can I update existing Notion rows instead of creating new ones?

Yes, use 'Update a Database Item' instead and add a filter to match on email or ID. You'll need a way to identify existing records first.

What happens if someone submits the same form twice?

Make creates duplicate rows in Notion. Add a filter using Notion's search function to check for existing entries before creating new ones.

Can I send responses to multiple Notion databases?

Use Make's router module after the Typeform trigger to split responses. Set up filters based on form answers to route to different databases.

How do I handle file uploads from Typeform?

Typeform file uploads become URLs. Map them to Notion's Files & Media property type, and Make will convert the links to embedded files automatically.

Beginner~12 min setupProductivity & FormsVerified April 2026

How to Send Typeform Responses to Notion Database with Make

Automatically create a new row in your Notion database every time someone submits a Typeform response, with fields mapped to database properties.

Steps and UI details are based on platform versions at time of writing — check each platform for the latest interface.

Make

Also on:Zapier N8n Power-automate Pipedream

Best for

Teams that need reliable field mapping between Typeform surveys and structured Notion databases with complex property types.

Not ideal for

Simple text-only forms where Zapier's pre-built template would be faster to configure.

Sync type

polling

Use case type

import

Real-World Example

💡

A 25-person marketing agency uses this to track client onboarding surveys in their Notion CRM. New clients fill out a detailed intake form covering project scope, timeline, and budget. Before automation, account managers manually copied 12+ fields from each response into their project database, taking 10 minutes per client and introducing typos. Now responses flow directly into Notion with proper formatting and trigger follow-up task creation.

What Will This Cost?

Drag the slider to your expected monthly volume.

Monthly workflow runs

/mo

505005K50K

Each platform counts differently — Zapier: 1 task per trigger. Make: 1 operation per module per record. n8n: 1 execution per run.

$30/mo if billed monthly

Pipedream

$29/mo

Basic plan

Prices shown for annual billing. Based on published pricing as of April 2026.

Estimated ROI

1000

min saved/mo

$583

labor value/mo

Free

no platform cost

Based on ~2 min manual effort per operation at $35/hr fully loaded labor cost.

Implementation

Skip the setup

Import this workflow directly into Make

Copy the pre-built Make blueprint and paste it straight into Make. All modules, filters, and field mappings are already configured — you just need to connect your accounts.

Before You Start

Make sure you have everything ready.

A Typeform account with at least one published form

A Notion workspace with admin access

A Notion database already created with the properties you want to populate

Make account (free tier works for basic usage)

Field Mapping

Map these fields between your apps.

Field	API Name	Description
Required
Client Name	`answers.textfield_name`	Maps to Notion title property - required field that identifies the client
Email Address	`answers.email`	Maps to Notion email property for contact information

4 optional fields▸ show

Project Type	`answers.multiple_choice_project`	Maps to Notion select property with predefined project categories
Budget Range	`answers.dropdown_budget`	Maps to Notion select property for budget classification
Timeline	`answers.date`	Maps to Notion date property for project deadline
Additional Requirements	`answers.textarea_requirements`	Maps to Notion rich text property for detailed project notes

Step-by-Step Setup

Scenarios > Create new scenario > +

Create new scenario in Make

Start a fresh automation scenario that will listen for new Typeform submissions. This becomes the foundation for your response-to-database workflow.

1Log into Make and click the orange 'Create a new scenario' button
2Click the large + icon in the center of the canvas
3Type 'Typeform' in the search box

✓ What you should see: You should see a list of Typeform modules including 'Watch Responses' at the top.

Typeform module > Connection > Add

Set up Typeform trigger

Connect your Typeform account and select which form responses to monitor. Make will check for new submissions every few minutes.

1Click 'Watch Responses' from the Typeform module list
2Click 'Add' next to the Connection field
3Follow the OAuth flow to connect your Typeform account
4Select your target form from the 'Form ID' dropdown

✓ What you should see: The module shows your form title and a green 'Connected' status indicator.

⚠

Common mistake — Don't pick 'Watch Form Responses (Legacy)' — it's deprecated and missing newer field types.

Make

click +

search apps

Notion

Set up Typeform trigger

Notion

module added

Typeform module > Settings

Configure response polling

Set how often Make checks for new responses and how many to process at once. This affects both speed and operation usage.

1Set 'Limit' to 10 (processes up to 10 new responses per run)
2Leave 'Since' blank to start monitoring from now
3Click 'OK' to save the trigger configuration

✓ What you should see: The Typeform module displays with your form name and shows 'Limit: 10' in small text below.

⚠

Common mistake — Setting limit above 50 can cause timeouts if your form has many fields or file uploads.

Typeform module > + > Notion > Create a Database Item

Add Notion module

Insert the Notion action that will create database records. Position it after the Typeform trigger to receive response data.

1Click the + icon to the right of your Typeform module
2Search for 'Notion' in the apps list
3Select 'Create a Database Item' from the available actions

✓ What you should see: A Notion module appears connected to your Typeform trigger with a line between them.

⚠

Common mistake — Don't choose 'Create a Page' — that makes regular pages, not database entries.

Notion module > Connection > Add

Connect Notion account

Link your Notion workspace so Make can write to your databases. You'll need admin access to the target database.

1Click 'Add' next to the Connection field in the Notion module
2Sign in to Notion and grant Make access to your workspace
3Select which pages/databases Make can access during the OAuth flow

✓ What you should see: The connection shows your Notion workspace name with a green checkmark.

⚠

Common mistake — If your target database doesn't appear later, you didn't grant access during this step — reconnect and select it.

Make settings

Connection

Choose a connection…Add

click Add

Notion

Authorize Make

popup window

✓

Connected

green checkmark

Notion module > Database ID

Select target database

Choose which Notion database will receive the form responses. Make pulls your database list from the workspace you connected.

1Click the 'Database ID' dropdown in the Notion module
2Find and select your target database from the list
3Wait for the Properties section to load below

✓ What you should see: The Properties section populates with your database columns like Name, Email, Created Date, etc.

⚠

Common mistake — Only databases with at least one property will appear in the dropdown list.

Notion module > Properties

Map form fields to database properties

Connect each Typeform question to the correct Notion database column. This determines where response data gets stored.

1Click in the first database property field (usually 'Name' or 'Title')
2Select the corresponding Typeform field from the dropdown (shows as 'answers: question_id')
3Repeat for each property you want to populate
4Leave unused properties blank

✓ What you should see: Each mapped property shows a pill with the Typeform field name, like 'answers: What is your name?'

⚠

Common mistake — Notion requires the title property (usually first column) to have a value — don't leave it unmapped.

Notion fields

Name

Status

Assignee

Due Date

Priority

available as variables:

1.props.Name

1.props.Status

1.props.Assignee

1.props.Due Date

1.props.Priority

Notion module > Properties > specific property fields

Handle different field types

Match Typeform field types to Notion property types correctly. Email fields go to email properties, dates to dates, etc.

1For email fields: map to Email properties in Notion
2For multiple choice: map to Select or Multi-select properties
3For dates: map to Date properties (Make converts formats automatically)
4For long text: map to Rich Text properties

✓ What you should see: The mapping shows appropriate data types without error indicators.

⚠

Common mistake — Mapping a multi-select Typeform field to a single Select property will only save the first choice.

Bottom toolbar > Run once

Test the workflow

Run a test to verify data flows correctly from Typeform to Notion. This catches mapping errors before going live.

1Click 'Run once' in the bottom toolbar
2Submit a test response to your Typeform (use a different browser/incognito)
3Watch the scenario execution in Make's interface
4Check your Notion database for the new row

✓ What you should see: Make shows green checkmarks on both modules and a new row appears in your Notion database with the test data.

⚠

Common mistake — The test might not find responses if you submitted them before setting up the trigger — submit fresh test data.

Make

▶ Run once

executed

✓

Notion

✓

Typeform

🔔 notification

received

Bottom toolbar > ON/OFF toggle

Enable automatic scheduling

Turn on the scenario to monitor for new responses continuously. Make will check your form every 15 minutes by default.

1Click the toggle switch in the bottom left to 'ON' position
2Verify the scenario shows 'Active' status
3Click 'Save' to preserve all your settings

✓ What you should see: The scenario displays 'Active' with a green indicator and shows the next scheduled run time.

⚠

Common mistake — Scenarios auto-pause after 7 days of no activity — reactivate if your form goes quiet then gets responses.

Drop this into a Make custom function.

Copy this template{{join(answers.multiple_choice_field; ", ")}}

▸ Show code

{{join(answers.multiple_choice_field; ", ")}}

... expand to see full code

{{join(answers.multiple_choice_field; ", ")}}

Scaling Beyond 200+ responses/day+ Records

If your volume exceeds 200+ responses/day records, apply these adjustments.

Increase processing limit

Change the limit from 10 to 100 responses per run. This reduces the number of operations and processes batches more efficiently.

Add error retry logic

Insert a filter after the Notion module to catch rate limit errors (429 status) and retry after 60 seconds. Notion caps API calls at 3 requests per second.

Consider database partitioning

Use Make's router to send responses to different Notion databases based on form fields like date or category. This prevents any single database from becoming unwieldy.

Going live

Production Checklist

Before you turn this on for real, confirm each item.

Test with actual form responses, not Make's sample data

Applies when: Always

Verify the title property mapping works - Notion silently fails without it

Applies when: Always

Set error handling to 'Break' to catch failed database writes

Applies when: Always

Check that multi-select fields map to Multi-select properties, not text

Applies when: Always

Increase the limit setting to 50+ if you expect response bursts

Applies when: High volume

Add a filter to skip test responses based on email domain or specific answers

Applies when: Always

Troubleshooting

Common errors and how to fix them.

Frequently Asked Questions

Common questions about this workflow.

Analysis

VerdictWhy Make for this workflow

Use Make for this if you need reliable field mapping and your Notion database has complex property types like relations, formulas, or multi-select fields. Make handles Notion's API quirks better than most platforms and gives you granular control over data transformation. The visual builder makes it easy to add filters or routing logic later. Skip Make if you're just mapping 3-4 basic text fields — Zapier's Typeform-Notion integration is faster to set up for simple cases.

Cost

This workflow costs 2 operations per response: one for the Typeform trigger, one for the Notion database creation. At 100 responses/month, that's 200 operations total. The Make Core plan at $9/month includes 10,000 operations, so you're well covered. Zapier's equivalent would cost $20/month for their Starter plan (750 tasks). N8n self-hosted is free but requires server management. Make wins on cost and ease of use here.

Tradeoffs

Zapier has a dedicated Typeform-Notion template that sets up in 3 minutes versus Make's 10-minute manual configuration. N8n offers better data transformation functions if you need to heavily modify responses before sending to Notion. But Make strikes the right balance — more flexible than Zapier's rigid templates, more user-friendly than N8n's code-heavy approach. The visual debugging is invaluable when field mapping goes wrong.

Notion's API is picky about data types and will silently reject records with type mismatches. Multi-select fields from Typeform come as arrays but Notion expects specific formatting. Make's automatic polling means a 15-minute delay between form submission and database entry — not truly real-time. If your form gets 100+ responses quickly, you'll need to increase the limit setting or responses get queued until the next run.

Ideas for what to build next

→
Add Slack notifications for high-priority responses — Use Make's router to send urgent survey responses (like support tickets) to a Slack channel while still saving to Notion.
→
Create follow-up email sequences — Connect the workflow to email tools like Gmail or Mailgun to send customized follow-ups based on specific survey answers.
→
Build response analytics dashboard — Route response data to Google Sheets or Airtable to create charts and reports that complement your Notion database.