Pro User
  • All of Microsoft
  • My Role
    • All in My Role
    • Pro User
    • Administrator
  • Focus
    • All in Focus
    • Microsoft Ignite 2026
    • Microsoft Copilot
    • All about AI
    • M365 Admin
    • What's Hot
    • M365 Release
Timespan
explore our new search
SharePoint Online: build workflows with Power Automate
SharePoint Online

SharePoint Online: build workflows with Power Automate

by HubSite 365 about Dougie Wood [MVP]

Connect form submissions to SharePoint lists, route items for approval, and use the approved data to prepare supplier documents.

Key insights

  • A Microsoft Forms submission can trigger a flow that retrieves response details and creates a SharePoint list item.
  • The SharePoint list needs columns that match the information collected by the form.
  • Power Automate's Start and wait for an approval action offers several approval patterns, including First to respond.
  • Long approval processes may need to be split across flows because a flow can stall if it runs longer than about a month.
  • For supplier-facing forms, Microsoft Forms can be set to Anyone can respond; Plumsail Forms is shown as an alternative with more form controls.

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.

What it does

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.

Who it is for and what you need

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.

How it works

  1. Create the form. In Microsoft Forms, create a form for the information you need. For supplier submissions, open Collect responses and set access to Anyone can respond if outside respondents need to use it. Share its link with respondents.
  2. Prepare the SharePoint list. Create a list on the relevant SharePoint site, then add columns for the information you plan to capture. In the example, the list is named Suppliers List and includes a Company Name text column.
  3. Create the flow and choose its trigger. In Power Automate, create a flow using the Microsoft Forms trigger When a new response is submitted. Select the form that should start the process.
  4. Retrieve the response. Add the Forms action Get response details. Select the same form and use the trigger’s dynamic Response ID as the response identifier. The trigger starts the flow; this action fetches the submitted answers.
  5. Create the SharePoint item. Add the SharePoint action Create item, select the site and list, and map each list column to its matching response field using dynamic content. Save the flow and submit a test response to check the mapping.
  6. Add an approval if the process needs review. Use Start and wait for an approval. Choose an approval type that fits the decision process; options shown include Approve/Reject – First to respond, an everyone-must-approve option, custom responses, and sequential approval.

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.

Limitations and alternatives

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.

Sources

Frequently asked questions

How do I send Microsoft Forms responses to a SharePoint list?

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.

Can external users submit a Microsoft Form for a SharePoint workflow?

Yes. Set the form’s Collect responses option to “Anyone can respond” and share its link with the external respondents.

Which approval action can I use in Power Automate?

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.

What if a SharePoint approval takes more than a month?

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.