What happens if someone submits the form twice?

Make will create duplicate Notion records unless you add a filter to check for existing emails first. Add a Notion search module before the create module to prevent duplicates.

Can I track partial form submissions?

No, Typeform only sends completed submissions to Make. Partial responses that users abandon won't trigger your scenario or create Notion records.

How do I handle custom t-shirt size options?

Add all possible sizes to your Notion select field first, then ensure your Typeform question uses identical text. If someone picks an unlisted size, the entire record creation fails.

Will this work with Typeform's payment integration?

Yes, but only for completed payments. Failed or pending payments won't trigger the scenario since Typeform only sends webhook data for successfully submitted forms with confirmed payments.

Beginner~12 min setupProductivity & FormsVerified April 2026

How to Log Typeform Event Signups to Notion with Make

Automatically capture event registrations from Typeform and create detailed attendee records in your Notion database with check-in tracking.

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

Event organizers who need detailed attendee tracking in Notion with custom fields for dietary restrictions and merchandise sizes.

Not ideal for

High-volume events with 500+ daily registrations or teams that need instant registration notifications.

Sync type

polling

Use case type

import

Real-World Example

💡

A 25-person nonprofit runs quarterly fundraising dinners and uses this automation to track 150-200 attendees per event. Before automation, staff manually copied registration data from Typeform into spreadsheets, spending 3-4 hours per event and making typos that caused catering headaches. Now dietary restrictions and t-shirt sizes flow directly into their Notion event database for vendor coordination.

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 with event registration questions including name, email, dietary needs, and t-shirt size

A Notion workspace where you can create new databases

At least one test form submission to enable field mapping

Make account with available operations (free tier includes 1,000/month)

Field Mapping

Map these fields between your apps.

Field	API Name	Description
Required
Attendee Name	`title`	Full name from Typeform's name question, mapped to Notion's title property
Email Address	`email`	Contact email for event communications, must be valid email format in Notion

4 optional fields▸ show

Dietary Restrictions	`dietary_select`	Multiple choice selection from Typeform mapped to Notion select field with matching options
T-shirt Size	`tshirt_select`	Size selection for event merchandise, requires exact match between form and database options
Check-in Status	`checkin_checkbox`	Boolean field defaulted to false, manually updated to true when attendee arrives at event
Registration Date	`submitted_at`	Timestamp from Typeform submission, automatically formatted as Notion date property

Step-by-Step Setup

Notion > Add Page > Database

Create your Notion database

Set up a database with columns for attendee tracking. You need fields for name, email, dietary preferences, t-shirt size, and check-in status before connecting to Make.

1Create a new page in Notion and add a database
2Add columns: Name (Title), Email (Email), Dietary (Select), T-shirt Size (Select), Check-in (Checkbox)
3Set default values for Select fields with your event options
4Copy the database URL from your browser

✓ What you should see: A Notion database with 5 columns ready for event attendee data.

Make > Scenarios > + > Notion

Connect Notion to Make

Make needs permission to write to your Notion workspace. You'll authenticate once and select which pages Make can access.

1Go to Make.com and click Create a new scenario
2Click the + button and search for 'Notion'
3Select 'Create a Database Item' module
4Click 'Create a connection' and sign in to Notion
5Grant access to the workspace containing your event database

✓ What you should see: Green 'Connected' status next to Notion with your workspace name showing.

⚠

Common mistake — Don't pick 'Update a Database Item' — that's for editing existing records, not creating new ones.

Notion Module > Database > Properties

Configure the Notion module

Tell Make which database to write to and map the structure. Make needs to understand your database schema before connecting the trigger.

1Select your event database from the Database dropdown
2Click 'Add item' for each property you want to populate
3Leave the values empty for now — you'll map them after adding Typeform
4Click OK to save the module configuration

✓ What you should see: The Notion module shows your database name and empty field mappings ready for data.

Make > Add Trigger > Typeform > Watch Responses

Add Typeform trigger

The trigger watches for new form submissions and starts your scenario. Make will poll Typeform every 15 minutes on the free plan.

1Click the clock icon to the left of your Notion module
2Search for 'Typeform' and select it
3Choose 'Watch Responses' as your trigger type
4Click 'Create a connection' and sign in to Typeform

✓ What you should see: Typeform trigger added with a connection established to your account.

⚠

Common mistake — Skip 'New Response' trigger — it only fires once per form, not once per submission.

Make

click +

search apps

Notion

Add Typeform trigger

Notion

module added

Typeform Module > Form Selection

Select your event form

Choose which Typeform will feed data to Notion. Make needs to analyze your form structure to map fields correctly.

1Select your event registration form from the Form dropdown
2Leave UID empty to capture all responses
3Set 'Limit' to 1 for testing
4Click OK to save the trigger

✓ What you should see: Your form name appears in the trigger module with response fields ready to map.

Typeform Module > Right-click > Run this module only

Test the Typeform connection

Make needs sample data to understand your form structure. This pulls your most recent form submission to use for field mapping.

1Right-click the Typeform module and select 'Run this module only'
2Wait for the green success indicator
3Click on the white bubble above the module to see the data
4Verify you can see form responses with answers

✓ What you should see: A data bubble showing form fields like 'Name', 'Email', and your custom questions with sample answers.

⚠

Common mistake — If no data appears, submit a test response to your form first — Make needs at least one submission to map fields.

Make

▶ Run once

executed

✓

Notion

✓

Typeform

🔔 notification

received

Notion Module > Properties > Field Mapping

Map attendee name and email

Connect your form's name and email fields to Notion. These are usually the first two questions in event registration forms.

1Click back into the Notion module to edit it
2Click the Name property field and select the name answer from Typeform data
3Click the Email property field and select the email answer from Typeform data
4Verify the field mappings show dynamic values, not static text

✓ What you should see: Name and Email fields in Notion show mapped values like '1. Name' and '2. Email' from your form.

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 > Additional Fields

Map dietary preferences and t-shirt size

Connect your form's multiple choice questions to Notion's select fields. The values must match exactly between Typeform and Notion options.

1Map the Dietary property to your dietary restrictions question answer
2Map the T-shirt Size property to your t-shirt size question answer
3Set Check-in property to 'false' as a default value
4Click OK to save all mappings

✓ What you should see: All five Notion properties show mapped values or defaults, with select fields connected to form answers.

⚠

Common mistake — If select field values don't match exactly, Notion will reject the record — check your option text in both apps.

Make > Run once

Test the complete scenario

Run the full workflow to verify data flows correctly from Typeform to Notion. This catches mapping errors before going live.

1Click 'Run once' at the bottom of the scenario
2Watch both modules execute with green checkmarks
3Check your Notion database for a new record
4Verify all fields populated correctly with form data

✓ What you should see: A new row in your Notion database with the test attendee's information properly formatted.

⚠

Common mistake — If the run fails with a 400 error, your Typeform option values don't match your Notion select options exactly.

Make > Scenario Controls > ON/OFF Toggle

Turn on the scenario

Activate automatic processing so new registrations create Notion records without manual intervention. The scenario will check for new submissions every 15 minutes.

1Toggle the 'ON' switch in the bottom left corner
2Click 'Save' to confirm your scenario configuration
3Submit a test registration through your live form
4Wait 15 minutes and verify the new record appears in Notion

✓ What you should see: The scenario shows 'ON' status and processes new form submissions automatically every 15 minutes.

Drop this into a Make custom function.

JavaScript — Custom Function{{if(contains(lower(dietary_restrictions); "vegan"); "Vegan"; if(contains(lower(dietary_restrictions); "vegetarian"); "Vegetarian"; "None"))}}

▸ Show code

{{if(contains(lower(dietary_restrictions); "vegan"); "Vegan"; if(contains(lower(dietary_restrictions); "vegetarian"); "Vegetarian"; "None"))}}

... expand to see full code

{{if(contains(lower(dietary_restrictions); "vegan"); "Vegan"; if(contains(lower(dietary_restrictions); "vegetarian"); "Vegetarian"; "None"))}}

Scaling Beyond 300+ registrations/day+ Records

If your volume exceeds 300+ registrations/day records, apply these adjustments.

Switch to Typeform webhooks

Replace Make's polling trigger with Typeform's webhook module to get instant notifications instead of waiting 15 minutes. Configure the webhook in your Typeform settings to point to Make's webhook URL.

Add duplicate detection

Insert a Notion search module before creating records to check if an attendee with the same email already exists. This prevents webhook retry failures from creating multiple records for the same person.

Batch process with delay

Add a 2-second delay between Notion record creations to stay under their API rate limit. For bulk imports, use Make's iterator to process responses in chunks of 100 records with pause modules.

Going live

Production Checklist

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

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

Applies when: Always

Verify Typeform select options exactly match Notion database select field values

Applies when: Always

Set scenario error handling to 'Break' to stop processing on mapping failures

Applies when: Always

Add email filter to prevent duplicate records if Typeform sends the same response twice

Applies when: High volume

Configure Make to send error notifications to your event management team

Applies when: Always

Test scenario with international characters in names if you expect global attendees

Applies when: Enterprise

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 real-time attendee tracking in Notion and your registration volume stays under 500 signups per month. Make handles Notion's complex database structure better than basic tools, and the visual builder makes field mapping obvious when you're juggling multiple form questions. Skip Make for simple email-only captures — Zapier does basic form-to-database syncing faster and cheaper.

Tradeoffs

This workflow burns 2 operations per registration: one for the Typeform trigger and one for Notion record creation. At 100 events per month, that's 200 operations total, fitting comfortably in Make's free 1,000-operation limit. Zapier's free tier only covers 100 tasks monthly, so you'd hit the wall at 50 registrations. N8N self-hosted is free but requires server management — overkill unless you're processing 1,000+ signups monthly.

Zapier beats Make on trigger speed — new Typeform submissions fire within 30 seconds versus Make's 15-minute polling interval. N8N offers better data transformation tools if you need to clean up form responses or merge duplicate attendees before creating Notion records. But Make wins on Notion integration depth — it handles select fields, relations, and formulas that trip up other platforms.

You'll hit Notion's API rate limit at 3 requests per second if you batch-import historical responses. Make doesn't queue operations intelligently, so bulk imports fail with 429 errors. Typeform's webhook delivery can duplicate responses if their system hiccups — add a filter to check for existing records by email before creating new ones. Notion's select field matching is case-sensitive and whitespace-sensitive, so 'Vegetarian ' with a trailing space breaks the sync silently.

Ideas for what to build next

→
Add Slack notifications for VIP attendees — Create a filter that checks for VIP status in registration responses and sends team notifications to a dedicated Slack channel for special handling.
→
Sync check-in status to Google Sheets — Build a second scenario that watches your Notion database for check-in updates and logs attendance data to a Google Sheet for real-time event analytics.
→
Send confirmation emails via SendGrid — Add an email module that automatically sends personalized confirmation emails with event details and QR codes based on the registration data captured in Notion.