Can I route different NPS score ranges to different Notion databases?

Yes, set up separate Notion action steps in each filter path. Point Promoters to a case study database and Detractors to a support ticket database for different workflows.

What happens if someone submits the same Typeform twice?

Zapier treats each submission as a new trigger, creating duplicate Notion entries. Add a lookup step to check for existing entries by email address if this is common.

How do I handle NPS responses in different languages?

Typeform passes the raw text to Notion unchanged. Add a Formatter step with language detection, or create separate forms per language with different Zap workflows.

Can I automatically assign Detractor responses to specific team members?

Yes, use a rotating assignment formula in the assignee field mapping. Create a lookup table in Notion or use modulo math based on response count to distribute evenly.

Beginner~8 min setupProductivity & FormsVerified April 2026

How to Route Typeform NPS Responses to Notion with Zapier

Automatically send NPS survey responses from Typeform to a Notion database with score-based tagging and follow-up task assignment.

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

Teams collecting under 500 NPS responses monthly who need immediate score-based routing without coding

Not ideal for

High-volume feedback collection over 1000 responses monthly or teams needing complex response analysis

Sync type

real-time

Use case type

notification

Real-World Example

💡

A 25-person B2B SaaS company sends quarterly NPS surveys to 800 customers and gets 200 responses each time. Before automation, their customer success manager manually reviewed each response in Typeform, copied Detractor feedback to a spreadsheet, and often missed following up on negative scores for days. Now Detractor responses (scores 0-6) automatically create high-priority Notion tasks assigned to CS team members within 2 minutes of submission.

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 at least one NPS survey form created

Notion workspace with a database set up for customer feedback tracking

Notion database with columns for NPS score (Number), comments (Rich text), and customer type tags (Select)

Admin access to both Typeform and Notion for API connections

At least one test response in your Typeform for field mapping

Field Mapping

Map these fields between your apps.

Field	API Name	Description
Required
NPS Score	`rating_scale_value`	Numeric score 0-10 from Typeform rating question, maps to Notion Number field
Respondent Email	`email_field`	Customer email address for follow-up, maps to Notion Email field
Customer Type Tag	`calculated_segment`	Promoter/Passive/Detractor based on score range, maps to Notion Select field
Follow-up Status	`priority_level`	Urgency level for customer success team, maps to Notion Select field
Response Date	`submitted_at`	Timestamp when survey was completed, maps to Notion Date field

1 optional field▸ show

Feedback Comment long_text_response Written feedback from respondent, maps to Notion Rich Text field

Step-by-Step Setup

Dashboard > Make a Zap > Trigger

Connect Typeform to Zapier

Link your Typeform account so Zapier can detect new NPS survey responses. You'll need your Typeform personal token for authentication.

1Click 'Make a Zap' from the Zapier dashboard
2Search for 'Typeform' in the trigger app field
3Select 'New Entry' as your trigger event
4Click 'Sign in to Typeform' and authorize access

✓ What you should see: Green checkmark appears next to Typeform with 'Connected' status

Trigger Setup > Choose Form

Select your NPS survey form

Choose which Typeform contains your NPS question. Zapier will pull the form structure to map response data.

1Click the 'Form' dropdown in the trigger setup
2Select your NPS survey from the list
3Click 'Continue' to proceed to testing

✓ What you should see: Form name displays in the dropdown with question count showing

⚠

Common mistake — Make sure your NPS question is set to 'Rating' field type in Typeform — Opinion Scale won't work with score-based filtering

Trigger Setup > Test

Test the Typeform trigger

Zapier pulls a recent survey response to map field data. If no responses exist, you'll need to submit a test response first.

1Click 'Test trigger' button
2Review the sample response data that appears
3Verify the NPS score field shows a number 0-10
4Click 'Continue with selected record'

✓ What you should see: Sample response shows with NPS score, comment text, and submission timestamp

⚠

Common mistake — If no test data appears, submit a response to your Typeform first — Zapier needs at least one entry to map fields

Zapier

▶ Turn on & test

executed

✓

Notion

✓

Typeform

🔔 notification

received

Action Setup > Choose App

Add Notion as action app

Connect your Notion workspace where the feedback database lives. Zapier needs page-level permissions to create database entries.

1Click the '+' button to add an action step
2Search for 'Notion' in the action app field
3Select 'Create Database Item' as the action
4Click 'Sign in to Notion' and grant access

✓ What you should see: Notion appears as connected action with green status indicator

Action Setup > Database Selection

Select feedback database

Choose the Notion database where NPS responses will be stored. This database should already have columns for score, comment, and tags.

1Click the 'Database' dropdown
2Select your customer feedback database
3Wait for Zapier to load the database schema
4Verify all required columns appear in the mapping section

✓ What you should see: Database properties load showing NPS Score, Comment, Customer Type, and Follow-up Status fields

⚠

Common mistake — Create your Notion database first with proper column types — Number for score, Rich Text for comments, Select for tags

Action Setup > Field Mapping

Map basic response fields

Connect Typeform response data to corresponding Notion database columns. Start with straightforward mappings before adding conditional logic.

1Click the NPS Score field and select the rating value from Typeform
2Map the comment field to your Notion Rich Text column
3Set the submission date to a Date property in Notion
4Add respondent email if collected in your form

✓ What you should see: Blue field tags appear showing Typeform data will populate each Notion column

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

Between Trigger and Action > Add Filter

Add score-based tagging with filters

Create conditional logic to tag responses as Promoter, Passive, or Detractor based on NPS score ranges. This requires Zapier's Formatter tool.

1Click '+ Add step' to insert a filter before Notion
2Choose 'Filter by Zapier' as the app
3Set condition: NPS Score is greater than or equal to 9
4Add a second path for scores 7-8 and a third for 0-6

✓ What you should see: Three filter paths appear: Promoter (9-10), Passive (7-8), Detractor (0-6)

⚠

Common mistake — Set up separate Zap paths for each score range — Zapier's conditional formatting gets messy with complex nested logic

Notion

trigger

filter

Condition

matches criteria?

yes — passes through

no — skipped

Typeform

notified

Promoter Path > Action Configuration

Configure Promoter path actions

Set up the Notion action for high-scoring responses. Tag as Promoter and assign low-priority follow-up tasks.

1In the Promoter filter path, map Customer Type to 'Promoter'
2Set Follow-up Status to 'Request Review'
3Set Priority to 'Low'
4Add 'Case Study Candidate' tag if score equals 10

✓ What you should see: Promoter path shows Notion action with appropriate tags and follow-up settings

Detractor Path > Action Configuration

Set up Detractor urgent follow-up

Configure high-priority actions for low NPS scores. These responses need immediate attention from customer success.

1In the Detractor path, set Customer Type to 'Detractor'
2Map Follow-up Status to 'Urgent - Contact Within 24h'
3Set Priority to 'High'
4Add assignee field mapping to customer success team member

✓ What you should see: Detractor entries will be flagged for urgent follow-up with team assignment

⚠

Common mistake — Don't auto-assign all Detractors to one person — they'll get overwhelmed. Rotate assignments or use a shared queue

Test Section > Run Test

Test the complete workflow

Run a full test with sample data to verify responses land in Notion with correct tags and assignments based on scores.

1Click 'Test action' on each filter path
2Check your Notion database for new test entries
3Verify tags match the score ranges correctly
4Confirm follow-up assignments are working

✓ What you should see: Test entries appear in Notion with proper Promoter/Passive/Detractor tags and follow-up settings

⚠

Common mistake — Test with actual NPS scores from your form, not Zapier's sample data — score ranges might not trigger the right filters

Action Settings > Error Handling

Configure error handling

Set up error notifications so failed responses don't get lost. Customer feedback is too valuable to drop silently.

1Click the gear icon on your Notion action
2Select 'Settings' from the dropdown
3Change error handling from 'Stop task' to 'Continue task'
4Add your email to error notification settings

✓ What you should see: Error handling shows 'Continue task' with email notifications enabled

Zap Management > Turn On

Turn on the Zap and monitor

Activate your workflow and watch the first few responses to catch any field mapping issues or filter problems early.

1Click the toggle switch to turn on your Zap
2Submit a test NPS response through your live form
3Check the Zapier Task History for successful runs
4Verify the response appears correctly in Notion

✓ What you should see: Zap shows 'On' status with successful task runs appearing in history

⚠

Common mistake — Monitor closely for the first 10-15 responses — Notion's API sometimes returns unexpected field validation errors that don't show up in testing

Drop this into a Zapier Code step.

Copy this template{{rating_scale_value | number}} >= 9 ? 'Promoter' : ({{rating_scale_value | number}} >= 7 ? 'Passive' : 'Detractor')

▸ Show code

{{rating_scale_value | number}} >= 9 ? 'Promoter' : ({{rating_scale_value | number}} >= 7 ? 'Passive' : 'Detractor')

... expand to see full code

{{rating_scale_value | number}} >= 9 ? 'Promoter' : ({{rating_scale_value | number}} >= 7 ? 'Passive' : 'Detractor')

Scaling Beyond 300+ NPS responses/month+ Records

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

Batch responses during off-peak hours

Send surveys Tuesday-Thursday to avoid weekend webhook delays. Zapier processes faster during business hours when Notion's API is less congested.

Use delay steps for burst protection

Add 30-second delays between filter steps during survey launches. This prevents hitting Notion's 3 req/sec rate limit when processing 20+ responses simultaneously.

Going live

Production Checklist

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

Set error handling to 'Continue task' not 'Stop task' to prevent workflow breaks

Applies when: Always

Test with actual NPS scores 0, 5, 8, and 10 to verify all filter paths work

Applies when: Always

Add email notifications for failed tasks to catch Notion API errors

Applies when: Always

Verify Notion database permissions allow Zapier to write new entries

Applies when: Always

Turn off auto-replay to prevent duplicate entries during Notion API hiccups

Applies when: High volume

Set up task usage alerts at 80% of your monthly limit

Applies when: High volume

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 you need the workflow running in 20 minutes without code. The multi-path filtering works well for NPS score ranges, and Notion's database structure maps cleanly to survey responses. Skip Zapier if you're processing 1000+ NPS responses monthly — the task usage gets expensive fast, and you'd save $80/month with Make's unlimited operations.

Cost

This workflow burns 3 tasks per response — one for the trigger, one for filtering, one for the Notion write. At 300 NPS responses monthly, that's 900 tasks total. Zapier's Professional plan at $49/month covers 2000 tasks, so you're fine. Make would handle the same volume for $9/month on their Core plan. N8n self-hosted is free but requires server management time.

Tradeoffs

Make handles conditional logic better with its visual branching — you can see all three score paths (Promoter/Passive/Detractor) on one canvas instead of separate filter steps. N8n has superior data transformation tools if you need to clean messy survey responses or calculate additional metrics. But Zapier's Typeform integration is more reliable — it catches webhook failures that Make sometimes drops, and customer feedback is too important to lose.

Notion's API rate limit hits at 3 requests per second, which sounds generous until you get a survey blast with 50+ responses in minutes. Zapier will queue them, but expect 10-15 minute delays during high volume. The NPS score field must be exactly 'Number' type in Notion — 'Formula' or 'Rollup' fields break the mapping. And Typeform's webhook sometimes sends duplicate payloads for long-form responses, so you'll see occasional duplicate Notion entries that need manual cleanup.

Ideas for what to build next

→
Add Slack notifications for Detractors — Create a second Zap path that posts urgent NPS scores under 6 to a customer success Slack channel with @here mentions.
→
Build follow-up email sequences — Connect your email platform to send thank-you notes to Promoters and schedule check-in calls for Detractors automatically.
→
Create NPS trend dashboard — Export Notion database to Google Sheets monthly and build charts tracking score trends by customer segment or time period.