New Lead Auto-Capture from Forms Submission

Overview

The New Lead Auto-Capture from Forms Submission flow is a beginner-level cloud flow that bridges Microsoft Forms and Salesforce. Whenever a configured form is submitted — for example a webinar sign-up, contact-us form, or gated content request — the flow retrieves the response, maps the answers onto Salesforce Lead fields, and creates a new Lead record automatically.

The flow is delivered as a solution-aware component inside the FlowLibsNewLeadAutoCaptureFromForms Dataverse solution. The Microsoft Form ID, Salesforce lead source, and default lead status are all controlled through environment variables so the same package can be redeployed against different forms or Salesforce orgs without editing the flow.

Use Case

Sales and marketing teams typically rely on web forms (Microsoft Forms, gated content pages, event sign-ups) to capture inbound interest, but those responses often sit in a spreadsheet or inbox until someone manually copies them into the CRM. That delay costs deals — speed-to-lead is one of the strongest predictors of conversion.

This flow closes that gap. Every form submission becomes a Lead in Salesforce within seconds, tagged with a configurable Lead Source so marketing attribution stays clean, and routed into the team's normal lead workflow (assignment rules, alerts, cadences) without any manual data entry.

The flow is ideal for teams that:

• Sales teams running webinar, demo-request, or contact-us forms that need to land in Salesforce
• Marketing teams that need accurate Lead Source attribution from gated-content campaigns
• Operations teams looking to eliminate manual copy-paste between Forms responses and the CRM
• Small businesses standardizing inbound lead capture without a paid marketing automation platform

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.

Point at a different Microsoft Form

Update the flowlibs_FormId environment variable to the ID of any Microsoft Form you want to capture leads from. No flow edit required — re-run a solution upgrade or set the value in the target environment.

Change Lead Source per campaign

Set flowlibs_LeadSource to the campaign-specific value (e.g., Webinar - Q2, Contact Us, Whitepaper Download) so Salesforce reports can attribute revenue back to the right inbound channel.

Map additional Salesforce Lead fields

Edit the Create Salesforce Lead action to add any custom fields the form collects (e.g., Industry, Company Size, Job Title). Use the corresponding response field from Get response details as the value.

Add a duplicate-check step

Insert a Salesforce Get records action filtered on Email before Create record, then wrap the create in a Condition to skip when a matching Lead already exists — useful when one person re-submits the same form.

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.

concat(outputs('Get_response_details')?['body/r1234'], ' ', outputs('Get_response_details')?['body/r5678'])

variables('varLeadSource')