Can I update existing Notion entries when someone modifies their registration?

Not directly with this setup. Typeform's 'New Entry' trigger only fires for brand new submissions. You'd need a separate Zap using webhooks to catch form updates, or manually sync changes between platforms.

What happens if my Notion database is full or hits a limit?

Notion doesn't have hard database limits, but if your workspace hits storage limits, the Zap will fail with a write error. Check your Notion plan's storage allowance and upgrade if you're approaching limits.

How do I handle registrations that come in after my event capacity is full?

Add a filter step in Zapier that checks your current attendee count in Notion before creating new entries. If you're at capacity, route new registrations to a waitlist database instead of your main attendee list.

Can I automatically send confirmation emails when registrations are logged?

Yes, add a third step using [Gmail](/apps/gmail/) or your email platform to send confirmations. Use the mapped email field from step 2 and include event details. This creates a complete registration and confirmation flow.

Why are some registrations not appearing in my Notion database?

Check your Zap history for failed runs. Common causes are mismatched select field values, required fields left unmapped, or Notion API timeouts during high-traffic periods. Failed tasks show specific error messages in your Zapier dashboard.

Beginner~8 min setupProductivity & FormsVerified April 2026

How to Log Typeform Signups to Notion with Zapier

Automatically create detailed attendee records in Notion whenever someone registers for your event through Typeform.

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

Zapier

Also on:Make N8n Power-automate Pipedream

Best for

Event organizers who need automated attendee tracking without coding skills

Not ideal for

High-volume events with 1000+ daily registrations or complex conditional logic

Sync type

polling

Use case type

import

Real-World Example

💡

A 25-person marketing agency runs quarterly client events and uses this automation to track 50-80 attendees per event. Before Zapier, their event coordinator manually copied registration details from Typeform into a spreadsheet, spending 2-3 hours per event and occasionally missing dietary restrictions or accessibility needs. Now registrations flow automatically into Notion where the team can filter by dietary needs for catering orders and track check-in status during the event.

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

Before You Start

Make sure you have everything ready.

Active Typeform account with an event registration form already created

Notion workspace with a database set up for attendee tracking

Zapier account (free tier works for basic volume)

Database properties in Notion for name, email, dietary needs, t-shirt size, and check-in status

At least one test submission in your Typeform for mapping setup

Field Mapping

Map these fields between your apps.

Field	API Name	Description
Required
Attendee Name	`answers.0.field.title`	Full name from Typeform name field, maps to Notion title property
Email Address	`answers.1.email`	Email for event communications, maps to Notion email property
Registration Date	`submitted_at`	When form was submitted, maps to Notion date property
Check-in Status	`static_value`	Default 'Not Checked In' status, updated manually at event

3 optional fields▸ show

Dietary Restrictions	`answers.2.choice.label`	Dietary preferences from Typeform multiple choice, maps to Notion select property
T-shirt Size	`answers.3.choice.label`	Apparel size selection, maps to Notion select with S/M/L/XL options
Workshop Preference	`answers.4.choices.labels`	Selected workshop sessions from multi-select field

Step-by-Step Setup

Dashboard > Create Zap > Typeform > New Entry

Create New Zap

Start building your automation by creating a new Zap. This sets up the foundation for connecting Typeform responses to your Notion database.

1Click 'Create Zap' from your Zapier dashboard
2Select 'Typeform' as your trigger app
3Choose 'New Entry' as the trigger event

✓ What you should see: You should see Typeform selected with 'New Entry' trigger displayed in the first step of your Zap.

Trigger > Typeform > Account Connection

Connect Typeform Account

Authenticate your Typeform account so Zapier can access your event registration form. You'll need your Typeform credentials to establish this connection.

1Click 'Sign in to Typeform'
2Enter your Typeform email and password
3Click 'Allow' to grant Zapier permissions
4Select your event registration form from the dropdown

✓ What you should see: A green 'Connected' badge appears next to Typeform, and your form shows up in the selection dropdown.

⚠

Common mistake — Don't select a test form - pick your actual event registration form or the field mapping won't match your real data structure.

Zapier settings

Connection

Choose a connection…Add

click Add

Notion

Authorize Zapier

popup window

✓

Connected

green checkmark

Trigger > Test

Test Typeform Trigger

Pull in a sample registration from your form to see what data Zapier receives. This shows you the exact field names and structure for mapping to Notion.

1Click 'Test trigger' button
2Wait for Zapier to fetch recent responses
3Review the sample data that appears
4Click 'Continue with selected record'

✓ What you should see: You should see a sample response with fields like Name, Email, Dietary Restrictions, T-shirt Size, and any custom questions you added.

⚠

Common mistake — If no test data appears, submit a test registration through your live form first - Zapier needs at least one response to pull sample data.

Zapier

▶ Turn on & test

executed

✓

Notion

✓

Typeform

🔔 notification

received

Action > + > Notion > Create Database Item

Add Notion Action

Set up Notion as your action app to receive the registration data. This creates the connection that will add new database entries for each signup.

1Click the '+' button to add an action step
2Search for and select 'Notion'
3Choose 'Create Database Item' as the action event
4Click 'Continue'

✓ What you should see: Notion appears as step 2 in your Zap with 'Create Database Item' selected as the action.

Action > Notion > Account Connection

Connect Notion Account

Authenticate with Notion and grant Zapier access to your workspace. The integration needs permission to read your database structure and write new entries.

1Click 'Sign in to Notion'
2Select the workspace containing your event database
3Click 'Allow access' to grant permissions
4Choose your attendee database from the dropdown

✓ What you should see: Notion shows 'Connected' status and your event attendee database appears in the selection menu.

⚠

Common mistake — Make sure you select a database, not a page - Zapier can only write to Notion databases with defined properties, not regular pages.

Action > Set up action > Database Properties > Name

Map Attendee Name Field

Connect the registrant's name from Typeform to your Notion database. This ensures each new entry shows who registered for your event.

1Find the 'Name' property in your Notion database fields
2Click the field mapping dropdown
3Select the name field from your Typeform data
4Verify the mapping shows the sample name

✓ What you should see: The Name field shows mapped data from your Typeform, displaying the test registrant's name.

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

Action > Set up action > Database Properties > Email

Map Email and Contact Info

Set up email mapping so you can contact attendees about event updates. This creates your primary communication channel for registered participants.

1Locate the 'Email' property field
2Map it to the email field from Typeform
3Add phone number mapping if you collect that data
4Map any additional contact fields you need

✓ What you should see: Email field displays the test data from your sample Typeform response.

⚠

Common mistake — Double-check the email mapping uses the actual email field, not a text field that happens to contain an email address.

Action > Set up action > Database Properties > Custom Fields

Map Event-Specific Details

Connect dietary preferences, t-shirt sizes, and other event logistics from your form. This captures the operational data you need for catering and swag ordering.

1Map 'Dietary Restrictions' to your Typeform dietary field
2Connect 'T-shirt Size' to the corresponding form question
3Map any workshop preferences or session selections
4Set accessibility needs if you collect that information

✓ What you should see: All event logistics fields show properly mapped data from your test form submission.

⚠

Common mistake — If you're using select/dropdown properties in Notion, the Typeform values must exactly match your Notion options or the zap will error.

Action > Set up action > Database Properties > Check-in Status

Set Check-in Status Default

Configure the check-in status to default to 'Not Checked In' for new registrations. This gives you a field to update when attendees arrive at your event.

1Find your 'Check-in Status' property
2Select 'Custom' from the dropdown instead of mapping
3Type 'Not Checked In' as the default value
4Verify this matches your Notion status options

✓ What you should see: Check-in Status field shows 'Not Checked In' as a static value, not mapped from Typeform.

⚠

Common mistake — The status text must match exactly what you have in Notion's select property options, including capitalization and spacing.

Action > Set up action > Database Properties > Registration Date

Add Registration Timestamp

Include when the person registered so you can track signup patterns and follow up appropriately. This helps with event planning and communication timing.

1Map your 'Registration Date' property
2Select 'Submitted At' from the Typeform data
3Verify the timestamp format matches your needs
4Confirm the timezone displays correctly

✓ What you should see: Registration Date shows the timestamp from when the test form was submitted.

Action > Test action

Test the Complete Integration

Run a full test to make sure data flows correctly from Typeform to Notion. This validates your field mapping and catches any configuration issues before going live.

1Click 'Test action' at the bottom of the setup
2Wait for Zapier to create the test record
3Open your Notion database to verify the entry appeared
4Check that all fields populated correctly

✓ What you should see: A new row appears in your Notion database with all the mapped information from your test Typeform submission.

⚠

Common mistake — If the test creates a duplicate entry, delete it from Notion before publishing - the test uses real data and creates actual database records.

Zap Editor > Publish

Publish Your Zap

Turn on your automation so it starts processing real event registrations. Once published, every new Typeform submission automatically creates a Notion database entry.

1Click 'Publish Zap' in the top right
2Give your Zap a descriptive name like 'Event Registration to Notion'
3Confirm you want to turn it on
4Monitor the dashboard for successful runs

✓ What you should see: Your Zap shows as 'On' in your dashboard and begins processing new Typeform submissions automatically.

Drop this into a Zapier Code step.

JavaScript — Code Step{{formatDate(submitted_at, 'YYYY-MM-DD HH:mm', 'America/New_York')}}

▸ Show code

{{formatDate(submitted_at, 'YYYY-MM-DD HH:mm', 'America/New_York')}}

... expand to see full code

{{formatDate(submitted_at, 'YYYY-MM-DD HH:mm', 'America/New_York')}}

Scaling Beyond 200+ registrations/day+ Records

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

Switch to Make for cost efficiency

At high volume, Make's operations-based pricing beats Zapier's task-based model. You'll save 40-60% on monthly automation costs while getting better error handling for database writes.

Add duplicate prevention filters

High-volume events can trigger multiple runs for the same submission. Add a lookup step to check if the Typeform response ID already exists in your Notion database before creating new entries.

Monitor API rate limits

Notion's API limits writes to 3 requests per second. If you hit registration spikes, add a delay step or consider batching entries to avoid rate limit errors that could lose registration data.

Going live

Production Checklist

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

Test the complete flow with a real form submission, not just sample data

Applies when: Always

Verify select field values in Notion exactly match Typeform dropdown options

Applies when: Always

Set up email notifications for failed Zaps to catch broken registrations

Applies when: Always

Add a filter to prevent duplicate entries based on Typeform response ID

Applies when: High volume

Configure proper timezone handling for registration timestamps

Applies when: Always

Test field mapping with edge cases like special characters in names

Applies when: Enterprise

Troubleshooting

Common errors and how to fix them.

Frequently Asked Questions

Common questions about this workflow.

Analysis

VerdictWhy Zapier for this workflow

Use Zapier for this if your team needs a reliable, no-code way to track event registrations without manual data entry. Setup takes about 15 minutes and new signups appear in Notion within 2-3 minutes. The guided interface makes field mapping straightforward even for non-technical event coordinators. Skip Zapier if you're running high-volume events with 1000+ registrations per day - Make handles that volume more cost-effectively.

Cost

This workflow uses 1 task per registration. At 100 signups per month, that's 100 tasks total, fitting comfortably in Zapier's free tier (750 tasks/month). For 500 registrations monthly, you'll need the Starter plan at $19.99/month. Make would cost $9/month for the same volume, and n8n is free if you self-host. Zapier costs more but saves setup time.

Tradeoffs

Make offers better error handling for this use case - it can retry failed database writes and has more granular filters for duplicate prevention. N8n gives you custom JavaScript nodes to transform registration data before it hits Notion, useful for complex event logistics. But Zapier's pre-built Notion integration handles the most common field types without custom code, and the visual editor makes troubleshooting easier when registrations aren't flowing correctly.

Notion's API can be finicky with select field values - if someone types 'Medium' instead of selecting 'M' for t-shirt size, your Zap will fail. Test your form thoroughly with various input styles before your event launch. Registration timestamps come through in UTC, which might confuse your team if you're planning a local event. The Typeform trigger polls every 2-5 minutes on paid plans, so don't expect instant updates during busy registration periods.

Ideas for what to build next

→
Add automated confirmation emails — Set up a follow-up action to send personalized confirmation emails with event details immediately after logging registrations to Notion.
→
Create check-in status updates — Build a separate Zap that updates the check-in status in Notion when you scan QR codes or mark attendees present using a mobile form during your event.
→
Set up waitlist management — Add conditional logic to route registrations to a waitlist database when your main event reaches capacity, with automatic promotion when spots open up.