SurveyMonkey Response to Notion Research Log

Overview

This flow turns every new SurveyMonkey research/UX survey response into a structured entry in a Notion research database and posts the notable ones to a Microsoft Teams research channel. It captures the participant, their segment, the study tag, and the key quotes (answer payload) so the team builds a searchable research repository automatically.

Why it matters: Research insight is usually trapped in raw survey exports. Auto-logging each response to Notion — tagged by study and segment — turns scattered responses into a queryable knowledge base, while the Teams alert surfaces high-signal feedback the moment it arrives.

Status: Built and deployed to the solution in the Off state. Going live requires only authorizing the three connections and setting the environment variable values (no logic changes).

Use Case

A UX/research team runs ongoing surveys in SurveyMonkey. They want every response recorded in their Notion research database (tagged by study and participant segment), and they want responses that mention a watched keyword (e.g. 'cancel', 'bug', 'churn') pushed to their Teams research channel in real time so nothing important is missed.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
SurveyMonkey	shared_surveymonkey	OnNewResponseAddedSurvey GetSurvey
Notion	shared_notionip	CreateaPage
Microsoft Teams	shared_teams	PostMessageToConversation

Note — All connections are referenced as solution connection references; the flow is portable between environments as long as a connection is mapped at import time.

Customization Guide

Almost every realistic variant of this flow can be implemented by changing environment variable values. A few cases require small edits inside the flow definition — those are called out explicitly below.

Map real quote questions

Replace the serialized varKeyQuotes payload with specific open-text answers from triggerOutputs()?['body/pages'] (or carry a verbatim quote in a custom field) for cleaner Notion rows.

Score-based notability

Swap the keyword check for a rating threshold by carrying the score on custom_value and comparing with @greaterOrEquals(int(...), threshold).

Segment tagging

Populate the SurveyMonkey collector custom_value with the respondent's segment so the Notion Segment select is meaningful.

Multiple studies

Duplicate the flow per study (each with its own flowlibs_SurveyMonkeySurveyId + flowlibs_ResearchStudyTag) or make the study tag dynamic from a survey field.

Key Expressions

The flow is intentionally light on Power Fx / WDL gymnastics — the heaviest expressions are the branch-name concatenation and the approval outcome check. They are listed below in the order they appear in the flow.

@trim(concat(coalesce(triggerOutputs()?['body/first_name'],''),' ',coalesce(triggerOutputs()?['body/last_name'],'')))

@coalesce(triggerOutputs()?['body/custom_value'],'Unsegmented')

@string(coalesce(triggerOutputs()?['body/pages'],json('[]')))

@contains(toLower(variables('varKeyQuotes')), toLower(variables('varNotableKeyword')))

@if(empty(variables('varParticipantName')), concat('Survey Response ', triggerOutputs()?['body/id']), variables('varParticipantName'))

Customize & download