SurveyMonkey Low-Response Reminder Nudge

Overview

This flow lifts SurveyMonkey survey completion rates without manual chasing. On a daily schedule it reads a survey's response count, computes the response rate as a percentage of a configurable target, and routes accordingly: if the rate is below the reminder threshold it emails a reminder (with the survey link) to the non-responder distribution list and posts a "below target" notice to a Teams channel; if the rate is critically low it additionally escalates to the survey owner by email. Every run finishes by posting a response-rate report to Teams.

Why it matters: Low response rates undermine survey validity. Automated, timed nudges recover completions and keep the team informed of progress — no one has to open SurveyMonkey to check.

Status: Built as a FlowLibs demo. Ships Off; going live requires only connection authorization and setting the environment-variable values.

Use Case

A Marketing or Operations team running a survey with a target response count wants automatic reminders to non-responders and an escalation path to the owner when the survey is pacing badly — plus a daily readout of where the response rate stands.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
SurveyMonkey	shared_surveymonkey	GetSurvey
Office 365 Outlook	shared_office365	SendEmailV2
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.

Tune thresholds

Adjust varTargetResponseCount, varReminderThresholdPct, and varEscalationThresholdPct (keep the escalation threshold below the reminder threshold).

Cap reminders

Add a Dataverse ledger to record how many nudges each survey has had and skip once a cap is reached, avoiding reminder fatigue.

Deadline gate

Add a varDeadlineDate and only nudge while utcNow() is before the deadline.

Multiple surveys

Wrap the read/decision in an Apply to each over a list of survey ids (one env var per survey, or a JSON array).

Channel

Swap the Teams post for an Adaptive Card, or add SMS via Twilio for mobile audiences.

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.

@int(coalesce(body('Get_Survey_Details')?['response_count'],0))

@if(equals(variables('varTargetResponseCount'),0),0,div(mul(outputs('Compose_Current_Responses'),100),variables('varTargetResponseCount')))

less(outputs('Compose_Response_Rate_Pct'), variables('varReminderThresholdPct'))

less(outputs('Compose_Response_Rate_Pct'), variables('varEscalationThresholdPct'))

@{body('Get_Survey_Details')?['collect_url']}

Customize & download