Form Submission to SQL Logger

Overview

FlowLibs - Form Submission to SQL Logger is a beginner-level Power Automate cloud flow that demonstrates the most common SQL Server integration pattern: capturing form submissions and logging them directly to a SQL database. When a Microsoft Form is submitted, the flow retrieves the response details and inserts a new row into a SQL Server table with the submitter's email, submission date, and response ID.

This is the first SQL Server connector flow in the FlowLibs library and serves as the foundational pattern for all SQL Server demos.

Use Case

Organizations often need to capture structured data from end users (feedback, requests, registrations) and route it into a central SQL database for reporting, analysis, or downstream processing. This flow eliminates manual data entry by automatically writing each form submission to SQL in real time.

Common scenarios: customer feedback logging, event registration tracking, IT support request intake, employee survey data capture, and any form-to-database pipeline.

The flow is ideal for teams that:

• Customer feedback logging
• Event registration tracking
• IT support request intake
• Employee survey data capture
• Any form-to-database pipeline

Flow Architecture

Environment Variables

Connectors & Connections

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.

Create the SQL table

Create a table in your SQL database with columns matching the form fields. Example: CREATE TABLE [dbo].[FormSubmissions] ( Id INT IDENTITY(1,1) PRIMARY KEY, SubmitterEmail NVARCHAR(255), SubmittedDate DATETIME2, ResponseId NVARCHAR(50) );

Create the Microsoft Form

Create a form in Microsoft Forms with your desired questions (e.g. Name, Email, Feedback). Copy the Form ID from the URL after id= and use it for the flowlibs_FormSubmissionFormId environment variable.

Configure environment variables

Update the four environment variable current values in the solution: flowlibs_FormSubmissionFormId (your Form ID), flowlibs_SqlServerName (your SQL Server hostname), flowlibs_SqlDatabaseName (your database name), and flowlibs_SqlTableName (your table name, e.g. [dbo].[FormSubmissions]).

Update the SQL column mapping

Open the Insert Form Response Into SQL action in the designer. The default mapping sends SubmitterEmail, SubmittedDate, and ResponseId. To add form question fields, click into the action's item/row parameters, add new fields matching your SQL column names, and map each to the corresponding form response field using dynamic content from Get Response Details (answers are keyed by question ID, e.g. body/rXXXXXXXXXX).

Authorize connections

Update both connection references (Microsoft Forms and SQL Server) with authorized connections for your tenant.

Turn the flow on

Toggle the flow from Off to On. Submit a test form response to verify a new row appears in your SQL table.

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.

@parameters('flowlibs_FormSubmissionFormId')

@triggerOutputs()?['body/resourceData/responseId']

@outputs('Get_Response_Details')?['body/responder']

@outputs('Get_Response_Details')?['body/submitDate']

@variables('varSqlServer')