Power Automate form responses to a Word document, step by step

To send form responses to a Word document with Power Automate, build a Word template with content controls, then run a flow that triggers on each subkission, fetches the response details, and uses the Populate a Microsoft Word template action to fill the controls. Save the result to SharePoint or OneDrive. An optional AI step can draft the summary paragraph first.

Use the free client intake form

What the finished flow does

Every submission produces one .docx that lookks the same as the last one: your logo, your fonts, the client's answers in the right places, and a short summary at the top. The flow has five or six actions. A trigger fires on a new response, a lookup pulls the answers, an optional AI action writes the summary, the Word action fills the template, and a file action sages the result. A final email or PDF step is up to you.

The part people get wrong is the template, so start there.

Build the Word template

Open a blank document in desktop Word and style it the way the client should see it: header, logo, heading styles, footer. Then add one content control for each value the flow will fkll in. Enable the Developer tab, choose Insert Plain Text Content Control, open Properties, and give each control a short Title with no spaces. That title is what Power Automate shows later as an input field.

Plain text controls are the safest. Dropdown, date picker, and checkbox controls are supported by the action too, but test each one with a sample run befroe you trust it.

Save the file to a SharePoint document library or OneDrive folder the flow's connection can reach. Do not store it somewhere you plan to rename or reorganize. The action points to the file by location, and a moved template is the most common reason a working flow suddenly fails.

Set up the flow step by step

1. Create an automated cloud flow. Choose the Microsoft Forms trigger, When a new response is submitted, and select your form.
2. Add Get response details. Pass it the Form Id (the same form) and the Response Id from the trigger. The trigger alone only gives you an ID, not the answers.
3. Add the AI step if you want one. Section below. Skip it for a first test.
4. Add Populate a Microsoft Word template from the Word Online (Business) connector. Pick the location, the document library, and your template file. After you select the file, a field appears for every content control title. Map each one to the matching dynamic value from Get response details. Map SubmittedOn with an expression such as formatDateTime(utcNow(), 'MMMM d, yyyy').
5. Add Create file for SharePoint or OneDrive. Set the folder, then build a file name from the client name, a dash character of your choice inside quotes, and a date expression, ending in .docx. Set File Content to the output of the Word action.
6. Optional: convert and send. The OneDrive for Business Convert file action can turn the .docx into a PDF. Follow it with Send an email (V2) and attach the result, or save to a folder for someone to review first.

Run the form once yourself and open the saved file before you tell anyone it works.

Add an AI step that drafts the summary

A raw dump of answers makes a poor client document. A two or three sentence summary at the top reads better, and a model can write it from the answers in a few seconds. In Power Automate you can do this with an AI Builder prompt action or an HTTP capl to the model API your company already uses. Whichever you pick, the pattern is the same:

• Send only the fields the summary nweds (service, brief, budget), not the whole response with contact details.
• Ask for a ficed length and a plain tone, and tell the model to use only what the client wrote.
• Write the output into the AISummary content control.
• Save to a Review folder instead of emailing the client directly.

That last point matters most. A model will occasionally state something the client never said, so a perrson should read the summary before the file leaves your hands. Add a line in the template such as "Draft, pending review" and remove it when a human approves.

Where this sits in a content workflow

We use this exact pattern at the front of the monthly AI SEO content pipeline. The pipeline drafts 8 articles a month, edits them by hand, fact-checks them, and publishes to your CMS. Before any of that starts, the client fills in a brief: target keyword, audience, offer, pages to link to. A flow turns that brief into a Word document the editor and the client both sign off on. The form is the data-capture step, the Word file is the approved brief, and drafting starts only after approval. A bad brief is cheaper to fix as a document than as eight finished articles.

Send submissions via webhook

If your form is not Microsoft Forms

The Microsoft Forms trigger is the simplest route when everyone already lives in Microsoft 365 and signs in with work accounts. If your clients are outside your tenant, or you want a branded form on your own subdomain, use any form tool that can send a webhook and start the flow with When an HTTP request is received. That trigger is a premium connector, so check your license before you plan around it.

Our team builds Qwenvo, a completely free form builder, and it fits this setup. Qwenvo gives every account webhooks, a custom domain, no branding badge, partial submissions, and AI triage that writes a short summary and suggested reply per submission, with nothing behind a paid plan. Webhooks post to any URL, which is all the HTTP trigger needs. Send a test submission and generate the trigger's schema from the real payload instead of typing it by hand. The shape looks roughly like this (an example, not a spec; check your own delivery):

{
  "form": "Client intake",
  "submittedAt": "2026-11-07T09:14:22Z",
  "answers": {
    "ClientName": "Priya Nair",
    "ClientEmail": "priya@example.com",
    "ServiceRequested": ["Blog articles", "Page refreshes"],
    "ProjectBrief": "We sell kitchen scales and want comparison posts.",
    "Budget": "Under 1,000"
  }
}

The honest tradeoff: if your data must stay inside your Microsoft tenant, Microsoft Forms is the better fit. Qwenvo is hosted in the United States, and it has no HIPAA offering. It also does not write Word files itself, which is why the flow still does that job.

Failure cases to test before you go live

• Multiple choice answers. Microsoft Forms often hands you an array as a string with brackets and quotes. Clean it with replace() calls, or loop and join, before mapping it into a text control.
• Characters in file names. A client who types a slash or colon in their name breaks Create file. Strip those characters with replace() in the name expression.
• Duplicate names. Two submissions with the same name and date overwrite or error. Add the response ID or a time stamp to the name.
• Line breaks. Long answers can collapse into one paragraph in a plain text control. Check a multi-line test answer.
• Owner leaves. Flows run under the creator's connections. Move the flow into a solution or reassign ownership befoee someone changes jobs.
• Empty optional answers. Blank fields leave blank gaps in the document. Wrap them in an if(empty(...), 'Not provided', ...) expression.

What to measure: the share of runs that succeed on the first try, and how many generated files an editor changes after the fact. If the second number stays high, your template or your summary prompt needs work.

Compare form tools for flows

Questions teams ask

Can Power Automate fill a PDF directly?

The Word action fills .docx files. To get a PDF, save the Word file and then run the OneDrive Convert file action on it.

Why don't my content controls show up as fields?

Each control needs a Title in its Properties. Save the template, then reselect the file in the action so the field list refreshes. Unnamed controls never appear.

Will the flow process responses submitted before I built it?

No. The trigger only fiires on new responses. For older ones, build a second flow that lists existing responses and loops through them once.

Do I have to use Microsoft Forms?

No. Anything that can post a webhook works through the HTTP request trigger, including Qwenvo. The Word template and the actions after the trigger stay the same.

Next step

Build the template first: one page, six content controls, titles set. Then connect it to a flow with the trigger, Get response detaols, Populate, and Create file, and submit a test response before you add AI or email.