SurveyMonkey Employee Pulse to HR Action

Overview

This solution turns SurveyMonkey employee pulse surveys into timely HR action while protecting anonymity. It is built as two cloud flows in one solution sharing a single anonymized Dataverse table:

- Flow A — Employee Pulse Response Intake and HR Alert (event-driven): on each new pulse response it stores an anonymized record (team, score, date only — no respondent identity) in Dataverse and alerts HR in Teams when the score is below the engagement threshold. - Flow B — Manager Pulse Summary Scheduled Digest (scheduled weekly): reads the anonymized responses, enforces an anonymity floor, and posts an aggregated per-team summary to the managers' Teams channel.

Why it matters: Employee sentiment data is only valuable if it reaches managers fast — without exposing individuals. Aggregated, threshold-driven alerts drive action while preserving trust. The flows deliberately never read or store respondent name/email.

Status: Built and verified (Flow Checker 0 errors / 0 warnings on both flows). Both flows ship Off — going live requires only authorizing the connections and setting the environment variable values.

Use Case

An HR team running pulse surveys (eNPS / engagement) wants per-team trends and early warnings on declining engagement, with anonymity guaranteed. HR is alerted in real time when a team's score drops below a threshold, and managers receive a weekly anonymized summary — all without ever seeing individual responses.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
SurveyMonkey	shared_surveymonkey	OnNewResponseAddedSurvey GetSurvey
Microsoft Dataverse	shared_commondataserviceforapps	CreateRecord ListRecords
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 the real score and team at go-live

Replace the demo stand-ins: read the eNPS/engagement rating question from triggerOutputs()?['body/pages'], and the team from a survey question or a second SurveyMonkey invite parameter passed in custom_value.

Driver questions

Break out engagement drivers (manager, workload, recognition) into separate columns/scores per team.

Trend over time

Add a Power BI report over flowlibs_pulseresponse to chart eNPS by quarter.

Action plans

On a below-threshold alert, also create a manager action-plan task (Planner/To-Do).

Separate audiences

Point the HR alert and the manager summary at different Teams channels by adding a second group/channel env-var pair.

Delivery channel

Swap or add Outlook SendEmailV2 to email managers their summary in addition to the Teams post.

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.

@{guid()}

@parameters('EnvVar_DefaultTeamName')

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

less(@variables('varScore'), @variables('varThreshold'))

createdon ge @{addDays(utcNow(),-7)}

@length(coalesce(body('List_Recent_Pulse_Responses')?['value'],createArray()))

greaterOrEquals(@outputs('Compose_Response_Count'), @variables('varMinResponses'))

Customize & download