SharePoint Online workflows built with Power Automate can capture form submissions in a list, route records for approval, and use approved information to prepare documents. This approach is useful for SharePoint site owners, operations teams, and makers who want to automate a business process such as supplier onboarding. Dougie Wood [MVP] demonstrates a supplier onboarding example that connects a Microsoft Form, a SharePoint list, and a Power Automate flow.
A workflow is a sequence of steps that starts with a trigger and then runs actions. In the supplier example, an external supplier submits a form; Power Automate gets the full response and creates an item in a SharePoint list. An approval step can then route that item to a reviewer, after which the process can update its status and produce an onboarding document.
The approach separates data collection from the structured record the operations team needs to work with. Microsoft Forms responses can be viewed in Forms and extracted through Excel natively, while the flow copies selected response fields into SharePoint. Once the information is in a list, the team can use the item as the record for review and follow-up.
The demonstrated process also outlines generating a Word onboarding pack from captured information, converting it to PDF, saving it in a SharePoint document library, and emailing it to the supplier. That is a broader process than the basic form-to-list flow: each stage needs to be configured to match the organization’s fields, review rules, and document template.
This pattern is aimed at people who manage SharePoint lists or build business process automation with Power Automate. The example begins with a Microsoft Form, a SharePoint site and list, and a Power Automate connection to the relevant services. The form fields and list columns should be planned together so that responses have matching destinations.
For an external form, the demonstrated Microsoft Forms setup uses the Anyone can respond option, allowing people outside the Microsoft 365 tenant to use a shared link. That setting is relevant when suppliers are not licensed users in the tenant. Microsoft Forms is described in the demonstration as included in business licenses.
Microsoft Forms can collect information with different question types, support sections and branching logic, and provide a preview for computer and mobile layouts. The example keeps its form and SharePoint list simple, using company name as the field to map. A real process may need additional list columns and corresponding response fields.
After the decision, the workflow can be designed to update the list item and continue the onboarding process. Dougie Wood’s example describes producing a document from the approved information, saving a PDF in a library, and emailing it to the supplier. Test the complete path with representative submissions before relying on it for live requests.
Microsoft Forms provides a straightforward route for collecting external responses, but the demonstration points out that the native form experience has fewer options than a dedicated form tool. Plumsail Forms is shown connected to a SharePoint list, with SharePoint fields available in the form and controls for features such as signatures and data tables. It is a third-party alternative, not a requirement for the Forms-to-list flow.
Approval duration also matters. The demonstration warns that a flow can stall and fail if it takes longer than about a month to complete. If a business approval can remain open longer, the process may need to be divided into multiple flows, for example with a later flow triggered when the SharePoint item is updated.
Before deploying a workflow, check that each form response maps to the intended list column, that the approval type reflects who must decide, and that the process can finish within the flow’s practical duration. The video also discusses retiring classic SharePoint workflows; organizations maintaining older processes should assess migration to Power Automate or another supported approach.
Create a flow triggered by Microsoft Forms’ “When a new response is submitted” event. Add “Get response details,” then use SharePoint’s “Create item” action to map response fields to list columns.
Yes. Set the form’s Collect responses option to “Anyone can respond” and share its link with the external respondents.
The demonstrated flow uses “Start and wait for an approval.” Its options include first-to-respond and everyone-must-approve patterns, custom responses, and sequential approval.
A flow that remains in progress longer than about a month may stall and fail. One alternative is to split the process into multiple flows, with a later flow starting when an item is updated.