Convert PDF to Word in Power Automate
What this action does
PDF4me Convert PDF to Word transforms PDF documents into fully editable Microsoft Word (.docx) files inside your Power Automate flow. Preserves layout, tables, images, fonts, and hyperlinks. Choose Draft mode for fast native-PDF conversion (1 API call per file) or High mode with AI OCR for scanned documents in 8+ languages (2 API calls per page). Replace manual SmallPDF, iLovePDF, or Adobe Acrobat uploads with a single automated action that chains directly into SharePoint, Outlook, Teams, Dynamics 365, and any Microsoft 365 workflow.
Authenticating Your API Request
Every PDF4me action in Power Automate requires a valid PDF4me connection. Create one with your API key the first time and Power Automate reuses it across all PDF4me actions in your flows.
Important Facts You Should Not Miss
.docx format with MIME type application/vnd.openxmlformats-officedocument.wordprocessingml.document, fully compatible with Word 2007+, Word for Web, Word for Mac, Microsoft 365, Google Docs, and LibreOffice.
Map File Content and File Name from a prior step, choose Quality Type (Draft for native PDFs, High for scanned), and run, the editable DOCX is returned in the output.
Parameters
Required: File Content, File Name, and Quality Type must all be provided. The action cannot convert without a binary source PDF and a quality selection.
| Parameter | Required | What it does | Example |
|---|---|---|---|
| File Content | Yes | Binary content of the source PDF file. Map from any prior action that returns file bytes: SharePoint Get file content, OneDrive Get file content, Outlook email attachment, Forms file upload, HTTP Request, or Get file content using path. | File Content (binary) |
| File Name | Yes | Filename of the source PDF including the .pdf extension. Used for identification during processing and to derive the default output filename (replacing .pdf with .docx). Map dynamically from prior step variables. | contract-2026.pdf |
| Quality Type | Yes | Conversion quality mode. Draft for native born-digital PDFs (1 API call per file, fast and cost-efficient). High for scanned PDFs, image-based PDFs, or complex multi-column layouts (2 API calls per page with OCR and layout reconstruction). | Draft |
Quality Type Options
DraftDefault, fast, 1 API call per fileHighAccurate, 2 API calls per page with OCROutput Fields
| Field | Type | What it contains |
|---|---|---|
File Content | Binary | Converted DOCX file as binary content. Map directly into downstream actions: SharePoint Create file, OneDrive Create file, Outlook Send an email attachment, Teams Post a message with attachment, or Word Online (Business) for editing. |
File Name | String | Output filename of the generated Word document (e.g. contract-2026.docx). Derived from the input File Name with the .pdf extension replaced by .docx. Use directly as the filename in SharePoint or OneDrive Create file actions. |
Quick Setup
- In your Power Automate flow, click + New step and search for PDF4me.
- Select the Convert PDF to Word action from the PDF4me Connect connector.
- Choose your PDF4me connection or click Add new connection with your API key.
- Map File Content to the binary output of a previous action: typically
Get file content(SharePoint),Get file content using path(OneDrive), Outlook email attachment, or HTTP Response body. - Set File Name dynamically from the prior step (must include
.pdfextension): e.g.triggerOutputs()?['body/Name']. - Choose Quality Type:
- Draft for native PDFs (Word exports, browser print, BI reports): fast and cost-efficient.
- High for scanned PDFs, photographed pages, or multi-column layouts, applies OCR + AI reconstruction.
- Save the flow and test with a sample PDF.
- Connect the output File Content to your next action: SharePoint Create file, OneDrive Create file, Outlook attach to email, Teams post with attachment, or Word Online for inline editing.
Workflow Examples
Workflow ExamplesCommon Power Automate flow patterns using Convert PDF to Word.
- An Outlook trigger fires when an email arrives from a known counterparty domain with a PDF contract attachment.
- Convert PDF to Word runs with Quality Type = Draft (counterparty contracts are typically native PDFs).
- The resulting DOCX is uploaded to a SharePoint "Contracts In Review" library with the original filename pattern.
- A Microsoft Teams Adaptive Card notifies the legal team with a link to the editable Word file, they redline directly in Word Online with Track Changes enabled.
- A Dataverse row captures the contract metadata (counterparty, received date, reviewer assigned) for the contract lifecycle dashboard.
- A SharePoint trigger fires when a new scanned PDF lands in a "Legacy Documents to Digitize" library.
- Convert PDF to Word runs with Quality Type = High (scanned source, OCR required).
- The OCR-extracted DOCX contains fully selectable, searchable text, paragraphs, tables, and headings are reconstructed from the scanned image.
- The DOCX is uploaded to the "Digitized Archive" SharePoint library, where SharePoint's built-in indexing makes it full-text searchable across the entire organization.
- An email notification confirms successful digitization to the records-management team with the original scan filename and conversion timestamp.
- A scheduled flow runs nightly over a "Source PDFs" SharePoint library containing template-source reports from third-party tools.
- For each new PDF, Convert PDF to Word runs with Quality Type = Draft to produce an editable DOCX template.
- A second action runs Find and Replace on the DOCX to swap static placeholders with mail merge field markers (e.g.
{{CustomerName}},{{InvoiceTotal}}). - The template-ready DOCX is filed in a "Templates" SharePoint library, organized by report category, ready for downstream Word mail-merge or document-generation flows.
- A Power BI dashboard tracks template-creation throughput; legal and finance teams reuse the templates without rebuilding from scratch each quarter.