How to Route NPS Survey Responses to Notion with Power Automate

My flows > + New flow > Automated cloud flow

Create automated cloud flow

Navigate to make.powerautomate.com and sign in with your Microsoft account. Click 'My flows' in the left sidebar, then '+ New flow'. Select 'Automated cloud flow' from the dropdown menu. Name your flow 'NPS to Notion Router' and search for Typeform in the trigger selection.

1. 1Click 'My flows' in the left navigation
2. 2Select '+ New flow' button
3. 3Choose 'Automated cloud flow'
4. 4Enter 'NPS to Notion Router' as flow name
5. 5Search 'Typeform' in trigger picker

Typeform Trigger > Sign in > Form Selection

Configure Typeform trigger

Click 'Sign in' to connect your Typeform account. Enter your Typeform credentials and authorize Power Automate access. Select your NPS survey from the 'Form' dropdown - you'll see all your published forms listed. The trigger will fire instantly when someone submits a response.

1. 1Click 'Sign in' button in Typeform connector
2. 2Enter Typeform username and password
3. 3Click 'Allow access' on authorization screen
4. 4Select your NPS survey from Form dropdown

New step > Notion > Create a database item

Add Notion connection

Click '+ New step' below the Typeform trigger. Search for 'Notion' and select 'Create a database item'. Click 'Sign in' to connect your Notion workspace. You'll need to authorize Power Automate in the Notion integration settings. Select the specific database where you store customer feedback.

1. 1Click '+ New step' button
2. 2Type 'Notion' in the search box
3. 3Select 'Create a database item' action
4. 4Click 'Sign in' for Notion authentication
5. 5Choose your feedback database from dropdown

Notion Action > Property Fields > Dynamic Content

Map basic response fields

Click in the 'Name' property field and select 'Response ID' from the dynamic content popup. For the email property, choose 'Hidden field: email' if you collect it, or 'Calculated: email' if using logic jumps. Map the submission date to your timestamp property using 'Submitted at' from Typeform data.

1. 1Click in Name property field
2. 2Select 'Response ID' from dynamic content
3. 3Click in Email property field
4. 4Choose email field from Typeform data
5. 5Map 'Submitted at' to date property

New step > Control > Condition

Add conditional logic for NPS scoring

Click '+ New step' and search for 'Condition'. This creates an if/else branch for score categorization. Set the left value to your NPS score field from Typeform dynamic content. Choose 'is greater than or equal to' and enter '9' for the promoter threshold. This condition will separate promoters from passive/detractors.

1. 1Click '+ New step' after Notion action
2. 2Search and select 'Condition' from Control
3. 3Set left value to NPS score field
4. 4Choose 'is greater than or equal to'
5. 5Enter '9' in the right value box

Yes branch > Add an action > Notion > Update a database item

Configure promoter actions

In the 'Yes' branch, add another Notion action to update the database item. Click 'Add an action' and choose 'Update a database item'. Select the same database and use the Response ID to identify the record. Set the NPS Category property to 'Promoter' and Priority to 'Low' since promoters need less urgent follow-up.

1. 1Click 'Add an action' in Yes branch
2. 2Select 'Update a database item' from Notion
3. 3Choose same feedback database
4. 4Set Page ID to Response ID from step 4
5. 5Enter 'Promoter' in NPS Category field

No branch > Add an action > Control > Condition

Add passive/detractor logic

In the 'No' branch, add another condition to separate passive (7-8) from detractors (0-6). Click 'Add an action' and insert a new Condition control. Set it to check if the score is greater than or equal to 7. This creates a nested condition for precise categorization of non-promoter responses.

1. 1Click 'Add an action' in No branch
2. 2Select 'Condition' from Control actions
3. 3Set left value to NPS score field
4. 4Choose 'is greater than or equal to'
5. 5Enter '7' for passive threshold

Nested branches > Notion > Update a database item

Configure passive and detractor updates

In the nested Yes branch, add a Notion update action and tag responses as 'Passive' with 'Medium' priority. In the nested No branch, tag as 'Detractor' with 'High' priority and set an assignee for immediate follow-up. Use your customer success manager's Notion user ID in the assigned property.

1. 1Add Notion update action to nested Yes branch
2. 2Set NPS Category to 'Passive' and Priority to 'Medium'
3. 3Add Notion update action to nested No branch
4. 4Set NPS Category to 'Detractor' and Priority to 'High'
5. 5Assign detractors to CS team member

New step > Notion > Create a database item

Add follow-up task creation

After the conditional logic, add a final step to create follow-up tasks. Click '+ New step' outside all condition blocks and add another Notion 'Create a database item' action. Point this to your tasks database and create a task with the response details, assigned person, and due date based on priority level.

1. 1Click '+ New step' after all condition blocks
2. 2Add 'Create a database item' for tasks database
3. 3Map customer details to task description
4. 4Set due date based on priority
5. 5Assign task to appropriate team member

Top toolbar > Save > Test > Manually

Test and activate flow

Click 'Save' in the top toolbar to save your flow configuration. Then click 'Test' and choose 'Manually' to test with a sample response. Submit a test NPS response in Typeform to trigger the flow. Check your Notion database to verify the response appears with correct tagging and that follow-up tasks are created properly.

1. 1Click 'Save' button in top toolbar
2. 2Select 'Test' from toolbar options
3. 3Choose 'Manually' test option
4. 4Submit test response in your Typeform
5. 5Verify data appears correctly in Notion

Use this Power Fx expression in the Priority field to automatically calculate urgency based on NPS score without nested conditions. Paste this in the Priority property mapping instead of using multiple condition blocks.

if(
  variables('nps_score') >= 9,
  'Low',

if(
  variables('nps_score') >= 9,
  'Low',
  if(
    variables('nps_score') >= 7,
    'Medium',
    'High'
  )
)