How to Log Every Form Submission to Excel or SharePoint Automatically (Power Automate, Step by Step)

Most teams collect responses through Microsoft Forms and then do something oddly manual with them: someone opens the results, copies the new rows into a spreadsheet, and hopes they didn't miss one. It works, until the form gets busy or the person doing the copying is off.

In about 10 minutes you'll build a Power Automate flow that logs every form response to an Excel table or SharePoint list the moment it's submitted — one running record, always up to date, with nobody copying anything by hand.

This is the sixth in our build-along series of seven Power Automate guides — Flow 6, following Flow 1, Flow 3, Flow 4 and Flow 5. It reuses the "fetch the details" pattern from Flow 3, this time writing the result somewhere instead of turning it into a task.

What you'll need before you start

• A Microsoft 365 business account with Microsoft Forms and Power Automate (standard business plans include both).
• Either an Excel table (in a file stored on OneDrive/SharePoint) or a SharePoint list with columns matching your form's questions — pick one destination before you start.
• 10 minutes.

Time-saver: if you're using Excel, format your data range as a proper Table first (`Insert → Table`) — Power Automate's Excel connector only writes to tables, not plain cells.

The flow at a glance

In plain English: when a form is submitted → get response details → add a row to your Excel table or SharePoint list. Three steps, and the middle one is the same fetch pattern you've seen before — the trigger only tells you *that* something arrived, not *what* was in it.

Step 1 — Create the flow and add the trigger

• Go to make.powerautomate.com, sign in with your work account, and choose Create → Automated cloud flow.
• Name it something like *"Log form responses — [your form name]"*.
• Search for the trigger When a new response is submitted, choose it under the Microsoft Forms connector, and click Create.

• In the trigger's Form Id field, select your form from the dropdown.

Step 2 — Fetch the response details

• Click + New step, search Get response details, and choose it under Microsoft Forms.

• Set Form Id to the same form, and Response Id to the dynamic content `Response Id` from the trigger above it.

This is the step people skip and then wonder why every field downstream is blank — the trigger only fires the alarm, this step goes and reads what was actually submitted.

Step 3 — Write it to your table or list

If you're logging to Excel:

• Click + New step, search Add a row into a table, and choose it under Excel Online (Business).
• Set Location, Document Library and File to where your workbook lives, then Table to the table you formatted earlier.
• A field appears for every column in your table — map each one to the matching answer from Get response details (dynamic content).

If you're logging to a SharePoint list:

• Click + New step, search Create item, and choose it under SharePoint.

• Set Site Address and List Name.

This trips people up: a freshly added Create item action looks like it only has a Title box. The list's real columns aren't missing - they're hidden under Advanced parameters until you click Show all.

• After you pick the site and list, only the Title field shows at first. Your own columns are tucked under Advanced parameters - click Show all to reveal them, then map each one to the matching answer from Get response details.

Either way, the mapping step is the same idea: one form question to one destination column.

Step 4 — Test it

• Submit a real (or test) response to your form.
• Open the flow's run history and check the run: a green tick on Get response details means the answers came through; a green tick on the Add a row/Create item step means it landed.

• Open your Excel table or SharePoint list and confirm the new row matches what you submitted.

If the row appears but fields are blank, the mapping in Step 3 is the first place to check — a field left on its default rather than mapped to dynamic content will always come through empty.

Common gotchas (and the fixes)

• "Add a row into a table" can't see your table. The range has to be a formatted Table, not just cells with headers — select your data and `Insert → Table` before building the flow.
• New form questions don't show up as fields. Power Automate reads the form's columns when you first add the action. Add or change a question, then remove and re-add the write step so it re-reads the current list.
• Duplicate rows appear. Usually a form set to allow multiple submissions per person combined with a flow that's been tested repeatedly on the same response — check your form's settings, and delete test rows before going live.
• A "choice" question logs as a strange code, not the text. Map the value field from the choice answer, not the raw object — Get response details usually exposes both.

Make it your own

• Add a Condition after Step 2 to only log responses that meet a threshold (e.g. a satisfaction score below 3), and route those into a separate escalation list.
• Combine this with Flow 3's pattern: log the row and create a Planner task in the same flow, so you get a permanent record and a to-do from a single submission.
• Add a Send an email (V2) confirmation step after the write, so whoever submitted the form gets a "we've got it" message.

You just built a flow that never misses a row

The pattern here — trigger, fetch the details, write them somewhere — is one you'll reuse constantly once you see it, because most business processes are really just "something happened, go get the specifics, record them." Master this once and half of your team's manual data entry becomes optional.

If you'd rather build this hands-on, for your own form, with a trainer in the room, that's exactly what our Power Automate Introduction course is for. Want it feeding a live Power BI report next? Power Automate Advanced picks up where this leaves off.

Next in the series: Flow 7 — Post a scheduled weekly digest automatically (the final flow).