Google Sheets Form Responses to Teams Digest

Overview

On a daily schedule this cloud flow reads the response rows from a Google Form's linked Google Sheet, identifies the responses it hasn't reported yet, summarizes them (a count, an average rating, and a per-response line), posts the digest to a Microsoft Teams channel, emails the same digest to a distribution address, and then stamps each reported row as processed so it isn't counted again. It turns a Google Form response sheet into a recurring, self-deduplicating team readout — no manual copy/paste and no double-reporting.

Use Case

Teams that collect feedback, intake requests, or survey answers through a Google Form often end up with a response sheet nobody watches. This flow gives Operations and Marketing a hands-off daily summary in the channel they already live in (Teams) plus an email for stakeholders who aren't in that channel. Because it marks rows processed, each response is reported exactly once, and the run is idempotent — if it's off for a day, the next run catches everything new.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
Google Sheets	shared_googlesheet	GetItems PatchItem
Microsoft Teams	shared_teams	PostMessageToConversation
Office 365 Outlook	shared_office365	SendEmailV2

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.

Point at your response sheet

Set flowlibs_GSheetId / flowlibs_GSheetTab to your Google Form response sheet and tab.

Rating column

Set flowlibs_RatingColumn to your form's rating-question header; leave as-is if you have no rating and the average simply reports 0.

Processed marker

Add a Processed column to the sheet, or set flowlibs_ProcessedColumn to an existing marker column.

Cadence

Change the Run Daily Form Scan recurrence for a different cadence (e.g. hourly).

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.

@equals(empty(item()?[variables('varProcessedColumn')]), true)

@greater(length(trim(coalesce(string(items('Aggregate_New_Responses')?[variables('varRatingColumn')]),''))), 0)

@if(greater(variables('varRatingCount'),0), div(variables('varRatingSum'), variables('varRatingCount')), 0)

@setProperty(items('Mark_Rows_Processed'), variables('varProcessedColumn'), variables('varProcessedValue'))

@items('Mark_Rows_Processed')?['__PowerAppsId__']

Customize & download