Why use Make's 15-minute polling instead of instant webhooks?

Webhooks cost extra operations and require webhook URL management. Polling works fine for feedback collection since 15-minute delays don't hurt response workflows.

Can this handle multiple NPS surveys from the same Typeform account?

Yes, but you need separate scenarios for each survey. Make's Typeform trigger only watches one form per scenario, so clone your scenario for additional surveys.

What happens if someone submits the same NPS survey twice?

Make processes each submission separately and creates duplicate Notion records. Add a filter checking for existing email addresses if you want to prevent duplicates.

How do I handle partial survey responses where NPS score is missing?

The filter in step 4 blocks incomplete responses. If you want to capture partials, modify the filter to 'Score is empty' and route those to a separate Notion database.

Beginner~12 min setupProductivity & FormsVerified April 2026

How to Route NPS Survey Responses to Notion with Make

Automatically route Typeform NPS responses to Notion, tag by score range, and create follow-up tasks.

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 wanting automatic NPS categorization and task assignment without writing custom scoring logic.

Not ideal for

High-volume feedback collection over 1,000 responses monthly or scenarios requiring instant response processing.

Sync type

polling

Use case type

import

Real-World Example

💡

A 25-person B2B SaaS company sends NPS surveys after each customer onboarding call. Before automation, their success team checked Typeform manually twice daily and missed negative feedback for 4-8 hours. Now detractor responses automatically create high-priority follow-up tasks in their Notion CRM within 15 minutes, while promoters get tagged for case study outreach.

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 an NPS survey already created and collecting responses

Notion workspace with a database containing Score, Category, Assignee, and Status properties

Make account with available operations (starts at 1,000/month free)

Admin access to both Typeform and Notion accounts for API connections

At least one test NPS response in Typeform to verify the automation works

Field Mapping

Map these fields between your apps.

Field	API Name	Description
Required
Respondent Email	`respondent_email`	Email address from Typeform submission, maps to Notion title/name property
NPS Score	`nps_score`	Numeric rating 0-10 from NPS question, used for categorization logic
Submitted Date	`submitted_at`	Timestamp when survey was completed, converts to Notion date property
NPS Category	`calculated_category`	Computed field showing Promoter/Passive/Detractor based on score range

2 optional fields▸ show

Response Text	`text_response`	Open-ended feedback comments, maps to Notion rich text property
Customer Segment	`hidden_customer_type`	Hidden field in Typeform containing customer tier or segment info

Step-by-Step Setup

Dashboard > Create scenario > Typeform > Watch Responses

Create new scenario in Make

Start a fresh scenario to handle incoming NPS survey responses. This will be your main automation pipeline for processing feedback.

1Click 'Create a new scenario' on your Make dashboard
2Click the + button to add your first module
3Search for 'Typeform' in the app list
4Select 'Watch Responses' trigger

✓ What you should see: You should see a Typeform module with 'Watch Responses' selected as your trigger.

Typeform module > Connection > Add

Connect your Typeform account

Authenticate with Typeform to access your survey responses. Make needs permission to watch for new submissions on your NPS form.

1Click 'Add' next to Connection
2Enter your connection name (e.g., 'NPS Survey Account')
3Click 'Continue' to open Typeform authorization
4Allow Make access to your Typeform account

✓ What you should see: Green checkmark appears next to your connection name, showing successful authentication.

⚠

Common mistake — Make sure you're logged into the Typeform account that owns your NPS survey before authorizing.

Make settings

Connection

Choose a connection…Add

click Add

Notion

Authorize Make

popup window

✓

Connected

green checkmark

Typeform module > Form dropdown

Select your NPS survey form

Choose the specific Typeform that contains your NPS survey. This tells Make which responses to monitor and route to Notion.

1Click the Form dropdown in the Typeform module
2Select your NPS survey from the list
3Leave 'Tag' and 'Since' fields empty for all responses
4Click 'OK' to save the trigger configuration

✓ What you should see: Your NPS survey form name appears in the Form field, and the module shows a green success indicator.

⚠

Common mistake — Don't select a test form by mistake — Make will route test responses to your production Notion database.

Scenario > + > Filter > Add condition

Add score range filter

Create a filter to categorize responses by NPS score before sending to Notion. This prevents processing responses without valid scores.

1Click the + button after your Typeform module
2Select 'Filter' from the tools menu
3Set condition: 'NPS Score' 'Is not empty'
4Click 'OK' to save the filter

✓ What you should see: A filter module appears between Typeform and your next module, showing the NPS score condition.

⚠

Common mistake — Make sure you're filtering on the actual NPS score field, not the overall rating — field names vary by survey setup.

Notion

trigger

filter

Condition

matches criteria?

yes — passes through

no — skipped

Typeform

notified

Filter > + > Notion > Create a Database Item

Add Notion connection

Connect to your Notion workspace where feedback will be stored. Make needs database write permissions to create new records.

1Click + after the filter module
2Search for 'Notion' and select it
3Choose 'Create a Database Item' action
4Click 'Add' to create a new Notion connection

✓ What you should see: Notion module appears with 'Create a Database Item' selected, ready for connection setup.

Notion module > Connection > Continue

Authenticate with Notion

Grant Make access to your Notion workspace. You'll need to select which pages Make can access during this step.

1Click 'Continue' in the connection dialog
2Select your Notion workspace from the list
3Choose the pages Make can access (include your feedback database)
4Click 'Allow access' to complete authentication

✓ What you should see: Connection shows 'Connected' status with your Notion workspace name displayed.

⚠

Common mistake — If you don't give Make access to your feedback database page, it won't appear in the database dropdown later.

Notion module > Database dropdown

Select feedback database

Choose the Notion database where NPS responses will be stored. This should be your customer feedback tracking database.

1Click the Database dropdown in the Notion module
2Select your customer feedback database
3Wait for field options to load
4Verify database properties appear below

✓ What you should see: Database name appears in the field, and you see property fields like Name, Score, Category ready for mapping.

⚠

Common mistake — Database loading can take 10-15 seconds — don't refresh the page if fields don't appear immediately.

Notion module > Database properties > Field mapping

Map basic response fields

Connect Typeform response data to your Notion database properties. Start with core fields like respondent email and submission date.

1Click in the Name/Title field and select 'Respondent Email' from Typeform
2Map 'Submitted At' from Typeform to your Date property
3Map 'NPS Score' to your Score number property
4Add any open-text feedback to a Text property

✓ What you should see: Field mappings show blue tags with Typeform data, indicating successful connections to Notion properties.

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 > Category property > fx > Formula

Add NPS category formula

Use Make's formula feature to automatically tag responses as Promoter, Passive, or Detractor based on score ranges.

1Click in your Category select property field
2Click the function icon (fx) to open formula builder
3Enter: if({{1.nps_score}} >= 9; "Promoter"; if({{1.nps_score}} >= 7; "Passive"; "Detractor"))
4Click 'OK' to save the formula

✓ What you should see: Category field shows the formula, which will automatically assign Promoter/Passive/Detractor based on score.

⚠

Common mistake — Replace '{{1.nps_score}}' with your actual NPS score field reference — the number may differ based on your scenario setup.

Notion module > Assignee/Status/Priority properties

Configure follow-up task creation

Set up automatic task assignment based on NPS category. Detractors get immediate follow-up, Promoters get thank-you tasks.

1Map your Assignee property to a team member for Detractor responses
2Set Status property to 'Needs Follow-up' for scores below 7
3Add Priority property mapping: High for Detractors, Medium for Passives, Low for Promoters
4Fill in any remaining required database properties

✓ What you should see: All required database properties show mapped values or formulas, with no red warning indicators.

⚠

Common mistake — Don't leave required Notion properties empty — the scenario will fail when it tries to create records.

Scenario bottom bar > Run once

Test the scenario

Run a test to verify your NPS routing works correctly. This will process a real Typeform response if available.

1Click 'Run once' at the bottom of the scenario
2Watch for the scenario to process (blue progress indicators)
3Check your Notion database for the new record
4Verify the category and task assignment are correct

✓ What you should see: Test completes successfully, showing green checkmarks on all modules, and new record appears in Notion with proper categorization.

⚠

Common mistake — If no recent Typeform responses exist, the test will show 'No data' — submit a test response first.

Make

▶ Run once

executed

✓

Notion

✓

Typeform

🔔 notification

received

Scenario header > Toggle ON > Schedule

Activate the scenario

Turn on automatic processing for all future NPS responses. Set the scheduling to check for new responses regularly.

1Click the 'OFF' toggle in the top-left to turn it 'ON'
2Set schedule to 'Every 15 minutes' for near real-time processing
3Click 'OK' to confirm the schedule
4Save the scenario with a descriptive name

✓ What you should see: Scenario shows 'ON' status with green indicator, and displays 'Every 15 minutes' as the schedule interval.

⚠

Common mistake — Don't set intervals shorter than 5 minutes — Typeform's API may not reflect new responses immediately.

Drop this into a Make custom function.

JavaScript — Custom Function{{if(1.nps_score >= 9; "Promoter"; if(1.nps_score >= 7; "Passive"; "Detractor"))}}

▸ Show code

{{if(1.nps_score >= 9; "Promoter"; if(1.nps_score >= 7; "Passive"; "Detractor"))}}

... expand to see full code

{{if(1.nps_score >= 9; "Promoter"; if(1.nps_score >= 7; "Passive"; "Detractor"))}}

Scaling Beyond 500+ responses/month+ Records

If your volume exceeds 500+ responses/month records, apply these adjustments.

Switch to webhook triggers

Replace polling with Typeform webhooks for instant processing. This eliminates the 15-minute delay and reduces operation usage by avoiding empty polling cycles.

Batch Notion writes

Use Make's aggregator tool to bundle multiple responses into single Notion API calls. This cuts operations in half but adds 5-10 minute processing delays.

Add rate limiting delays

Insert 2-3 second delays between Notion writes to avoid 429 errors. Notion's API caps at roughly 3 requests per second for database writes.

Going live

Production Checklist

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

Set error handling to 'Break' on the Notion module to catch missing required fields

Applies when: Always

Test with a Detractor score (0-6) to verify high-priority task creation works

Applies when: Always

Add a retry filter for Notion 502 errors with 30-second delay between attempts

Applies when: High volume

Verify your NPS question in Typeform uses the standard 0-10 scale, not 1-5

Applies when: Always

Set up Make's email notifications for scenario failures to catch API issues quickly

Applies when: Always

Check that Notion database permissions allow the connected integration to write records

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 the NPS categorization logic built into the workflow. Make's formula builder handles the Promoter/Passive/Detractor scoring without external scripts, and the visual router lets you send different response types to different Notion pages. Skip Make if you just want basic form-to-database sync — Zapier handles simple Typeform-to-Notion connections faster and uses fewer operations per response.

Cost

This workflow burns 2 operations per NPS response: one for the Typeform trigger, one for Notion record creation. At 200 responses monthly, that's 400 operations fitting comfortably in Make's free 1,000-operation tier. Zapier's free plan only covers 100 tasks monthly, so you'd need their $20 Starter plan. N8n self-hosted handles unlimited volume but requires server management — only worth it above 2,000+ responses monthly.

Tradeoffs

Zapier beats Make on Typeform integration depth — their trigger fires within 30 seconds versus Make's 15-minute polling minimum. N8n offers better Notion bulk operations if you're backfilling thousands of existing responses. But Make wins on the scoring logic complexity. Zapier's formatter can't handle nested if-then NPS categorization cleanly, and N8n requires custom JavaScript for the same logic Make handles in its visual formula builder.

You'll hit Notion's 2,000-character limit on long-form feedback responses — the API truncates without warning. Typeform's webhook data sometimes arrives before their API reflects it, causing duplicate processing if you switch from polling to webhooks mid-stream. Make's Typeform polling occasionally misses responses submitted in rapid succession (under 30 seconds apart) due to timestamp precision issues.

Ideas for what to build next

→
Add Slack notifications for Detractors — Send immediate alerts to your customer success channel when NPS scores drop below 7 for faster response times.
→
Create follow-up survey triggers — Automatically send targeted follow-up surveys to Promoters asking for referrals or case study participation.
→
Build NPS trend reporting — Route all responses to Google Sheets for monthly NPS tracking and segment analysis across customer types.