Can I filter applications before they reach Notion?

Yes, add a filter module between Typeform and Notion to screen applications. You can filter by keywords in cover letters, experience level, or required vs optional questions completed.

What happens if someone submits the same application twice?

Make processes each Typeform submission separately, creating duplicate Notion pages. Add a filter checking for existing email addresses in your database or use Notion's API to search before creating.

How do I handle file uploads larger than Notion's limit?

Typeform allows 10MB uploads but Notion caps files at 5MB. Add a filter checking file size and either reject large files or store them in [Google Drive](/apps/google-drive/) first, then link to Drive in Notion.

Can I update existing candidate records instead of creating new ones?

Switch the Notion module from 'Create Database Item' to 'Update Database Item' and add a search step first. This requires the candidate's Notion page ID, which you can get by searching for their email address.

Will this work with Typeform's logic jumps and hidden fields?

Make captures all submitted responses including conditional fields and hidden values. Map hidden fields like UTM parameters using the 'hidden' object in Typeform's webhook data structure.

Beginner~12 min setupProductivity & FormsVerified April 2026

How to Build a Job Application Tracker from Typeform to Notion with Make

Automatically create Notion database entries with candidate details when new job applications are submitted through Typeform.

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

HR teams processing 20+ job applications monthly who need real-time candidate tracking in Notion.

Not ideal for

Companies hiring less than 5 people annually or those wanting applicant data in spreadsheets instead of databases.

Sync type

real-time

Use case type

import

Real-World Example

💡

A 25-person SaaS startup uses this to automatically populate their hiring database whenever someone applies through their careers page. Before automation, their HR coordinator manually copied candidate details from Typeform into Notion 2-3 times per week, often losing track of weekend applications. Now every application creates a candidate page within 30 seconds, and their hiring manager reviews new applicants daily without missing anyone.

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.

Active Typeform account with a job application form already created

Notion workspace with a database set up for candidate tracking

Make account (free tier works for basic setups)

Admin access to both Typeform and Notion for authorization

Your Notion database should have properties for Name, Email, Resume, and Status at minimum

Field Mapping

Map these fields between your apps.

Field	API Name	Description
Required
Candidate Name	`answers[0].text`	Full name response from Typeform name question, becomes the page title in Notion
Email Address	`answers[1].email`	Email field from Typeform, maps to Email property in Notion for communication tracking
Position Applied	`hidden.job_title`	Hidden field in Typeform indicating which role the candidate is applying for
Application Date	`submitted_at`	Timestamp when the form was submitted, formatted for Notion date property

3 optional fields▸ show

Resume File	`answers[2].file_url`	File upload URL from Typeform, stored as link in Notion resume property
Cover Letter	`answers[3].text`	Long text response containing candidate's cover letter or motivation
Experience Level	`answers[4].choice.label`	Multiple choice response for years of experience or seniority level

Step-by-Step Setup

Dashboard > Create scenario > Typeform

Create New Scenario

Start a fresh Make scenario that will watch for new Typeform submissions. This becomes your trigger point for the entire hiring workflow.

1Click 'Create a new scenario' from your Make dashboard
2Click the large '+' circle in the center
3Type 'Typeform' in the search box
4Select 'Typeform' from the results

✓ What you should see: You'll see the Typeform module selector with trigger and action options listed.

Typeform > Triggers > Watch Responses

Set Typeform Trigger

Configure the trigger to fire when candidates submit your job application form. This watches for new responses in real-time via webhook.

1Click 'Watch Responses' from the trigger list
2Click 'Create a connection' if this is your first Typeform setup
3Authorize Make to access your Typeform account
4Select your job application form from the dropdown

✓ What you should see: The module shows your form title and a green 'Webhook successfully registered' message.

⚠

Common mistake — Don't pick 'Get Responses' — that only runs on schedule, not real-time when candidates apply.

Make

click +

search apps

Notion

Set Typeform Trigger

Notion

module added

Scenario > Run once > Module data

Test Typeform Connection

Verify the trigger works by submitting a test application. This also shows you the exact field structure for mapping to Notion later.

1Click 'OK' to save the Typeform trigger
2Open your Typeform in another tab and submit a test application
3Return to Make and click 'Run once'
4Click the small bubble on the Typeform module to view the captured data

✓ What you should see: You should see the test submission data including answers, timestamps, and respondent details in a JSON structure.

Make

▶ Run once

executed

✓

Notion

✓

Typeform

🔔 notification

received

Typeform > + > Notion > Create Database Item

Add Notion Module

Connect Notion as the destination where candidate profiles will be created. This module will receive data from Typeform and structure it for your hiring database.

1Click the '+' button to the right of the Typeform module
2Search for 'Notion' in the app selector
3Select 'Notion' from the results
4Choose 'Create a Database Item' from the action list

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

⚠

Common mistake — Skip 'Update Database Item' — you're creating new candidate records, not modifying existing ones.

Notion > Create connection > Authorize

Connect to Notion

Authenticate with Notion and grant Make access to your hiring database. The connection needs write permissions to create candidate pages.

1Click 'Create a connection' in the Notion module
2Click 'Authorize' to open Notion's permission dialog
3Select your hiring workspace from the dropdown
4Check the box next to your job applications database
5Click 'Allow access' to complete the connection

✓ What you should see: Make shows 'Connection verified' and your database appears in the Database dropdown.

⚠

Common mistake — Make sure you select the correct workspace if you have multiple — the database won't appear in the wrong workspace.

Notion > Create Database Item > Database

Select Target Database

Choose which Notion database will store your candidate applications. This should be your hiring pipeline tracker with columns for candidate details.

1Click the Database dropdown in the Notion module
2Select your job applications database from the list
3Wait for the property fields to load below

✓ What you should see: Property fields like Name, Email, Status appear below the database selection, matching your Notion database structure.

Notion > Properties > Name > Typeform data

Map Candidate Name

Connect the candidate's name from Typeform to the Name property in Notion. This becomes the page title for each candidate record.

1Click in the 'Name' field under Properties
2Click the Typeform data tab in the mapping panel
3Scroll to find the name question response
4Click to select the name field from your form

✓ What you should see: The Name field shows the Typeform field reference like {{1.answers[0].text}} representing the candidate's name input.

⚠

Common mistake — If you have separate first/last name fields, you'll need to concatenate them using the 'Text' function in the mapping panel.

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 > Properties > Email

Map Email Address

Connect the candidate's email from Typeform to your Email property in Notion. This field is crucial for communication tracking throughout the hiring process.

1Click in the Email property field
2Select the email question response from the Typeform data panel
3Verify the field shows the correct Typeform email reference

✓ What you should see: The Email field displays the mapped Typeform email value, typically shown as {{1.answers[X].email}} where X is your email question position.

Notion > Properties > Resume

Map Resume Link

Connect any file upload or URL field from Typeform to track candidate resumes. This gives your hiring team immediate access to application materials.

1Click in the Resume or File property field in Notion
2Look for file upload responses in the Typeform data
3Select the file URL field from the form submission
4If using a URL question, map that text response instead

✓ What you should see: The resume field shows the file URL reference from Typeform, displayed as {{1.answers[X].file_url}} or similar.

⚠

Common mistake — Typeform file uploads provide URLs, not direct file attachments — Notion will store the link, not embed the file.

Notion > Properties > [Field name]

Map Additional Form Responses

Connect remaining Typeform questions to corresponding Notion properties. Include cover letter, experience level, or any custom questions relevant to your hiring process.

1Map each remaining Typeform question to the appropriate Notion property
2Use the dropdown to select text, number, or select properties as needed
3Leave any Notion fields you don't want populated blank

✓ What you should see: All relevant Notion properties show mapped Typeform field references, creating a complete candidate profile structure.

⚠

Common mistake — Don't map every single Typeform field — only include data your hiring team actually needs in Notion.

Notion > Properties > Status

Set Initial Pipeline Status

Configure new applications to start at the beginning of your hiring pipeline. This ensures consistent tracking as candidates progress through stages.

1Find the Status or Stage property in your Notion mapping
2Click the dropdown or text field for this property
3Enter your initial status like 'New Application' or 'Under Review'
4Make sure this matches an option in your Notion database

✓ What you should see: The Status field shows your chosen initial value that will be applied to all new candidate records.

⚠

Common mistake — The status value must exactly match an existing option in your Notion select property — typos will cause creation errors.

Scenario > Run once > Notion database

Test Complete Workflow

Run the full scenario to verify candidate data flows correctly from Typeform into your Notion hiring database. This confirms your field mapping works end-to-end.

1Click 'OK' to save all Notion module settings
2Submit another test application through your Typeform
3Click 'Run once' in Make to process the new submission
4Check your Notion database for the new candidate page
5Verify all mapped fields populated correctly

✓ What you should see: A new candidate page appears in Notion with name, email, resume link, and other mapped details from the Typeform submission.

⚠

Common mistake — If the test fails, check that all your Notion property names exactly match the database structure — case sensitivity matters.

Drop this into a Make custom function.

JavaScript — Custom Function{{ifempty(1.answers[2].file_url; "No resume provided")}}

▸ Show code

{{ifempty(1.answers[2].file_url; "No resume provided")}}

... expand to see full code

{{ifempty(1.answers[2].file_url; "No resume provided")}}

Scaling Beyond 100+ applications/day+ Records

If your volume exceeds 100+ applications/day records, apply these adjustments.

Add Rate Limit Protection

Insert a 2-second sleep module between Typeform and Notion to prevent hitting Notion's 3 requests/second limit. High application volume during job posting announcements can overwhelm the API.

Batch Process Applications

Switch from webhook trigger to scheduled polling every 5 minutes. Process multiple applications in a single scenario run using Make's aggregator to reduce total operations consumed.

Split Processing by Job Type

Create separate scenarios for different job categories if you're hiring for multiple roles simultaneously. This prevents one high-volume position from creating bottlenecks for other role applications.

Going live

Production Checklist

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

Set error handling to 'Break' not 'Ignore' so failed candidate imports don't go unnoticed

Applies when: Always

Add email notification when scenario errors to catch Notion API failures quickly

Applies when: Always

Test with a real job application containing special characters in names and cover letters

Applies when: Always

Verify file upload limits match between Typeform and Notion (10MB vs 5MB respectively)

Applies when: Always

Configure scenario to run every minute instead of instant webhook if processing 100+ applications daily

Applies when: High volume

Set up duplicate detection filter based on email address to prevent double entries

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 candidate tracking and have complex form structures. Make handles Typeform's webhook system better than most platforms and gives you granular control over data transformation. The visual interface makes it easy to map multiple form fields to different Notion properties. Pick Zapier instead only if you're connecting simple forms with under 5 fields — their Typeform integration is more plug-and-play for basic setups.

Cost

This workflow consumes 2 operations per application — one for the Typeform trigger, one for Notion page creation. At 50 applications/month, that's 100 operations monthly. Make's free tier gives you 1,000 operations, so you're covered until you hit 500+ applications monthly. The Pro plan at $9/month handles 10,000 operations. Zapier charges $20/month for the same volume since they count each field mapping as a separate task. Make saves you $11 monthly on identical functionality.

Tradeoffs

Zapier's Typeform trigger captures hidden fields like UTM parameters automatically, which Make requires manual configuration to access. N8N offers better error handling with built-in retry logic when Notion's API is slow. But Make wins on the Notion side — their database item creation handles all property types including relations and rollups that trip up other platforms. The visual mapping interface also makes field debugging much faster when applications aren't flowing correctly.

Notion's API rate limit is 3 requests per second, which you'll hit if multiple candidates apply simultaneously. Add a 1-second delay between the Typeform trigger and Notion action to prevent 429 errors during busy application periods. Typeform webhooks occasionally deliver duplicate submissions within seconds of each other — add a filter checking for submission timestamps to avoid creating duplicate candidate records. Large resume files in Typeform sometimes take 30+ seconds to process, causing the webhook to timeout before Make receives the complete data.

Ideas for what to build next

→
Add Slack Notifications — Send hiring team alerts in Slack when senior-level candidates apply by adding filters for experience level and a Slack module after Notion.
→
Create Interview Scheduling — Connect Calendly or Acuity to automatically send scheduling links to qualified candidates based on their Notion status updates.
→
Build Application Analytics — Add Google Sheets logging to track application volume, source attribution, and conversion rates from your different job posting channels.