Convert Word to PDF

(1) Share

Report

Posted on by MC-02040828-0

Subject: Word Online "Convert Document to PDF" returns 404 Not Found in flat SharePoint folder

Body:
I am seeking help with a persistent "Not Found" error in a Power Automate flow. I am currently testing a simple conversion in a flat directory (no sub-folders) before moving to a more complex nested structure, but the Word Online connector fails to resolve the file.

The Setup:

Trigger: Manual button with a text input for batch naming.
Get files (properties only): Pointed at a specific test folder containing two files: one .docx and one .pdf.
Filter Query: FSObjType eq 0 (used to ensure only files enter the loop).
Apply to each: Iterates through the outputs of the "Get files" step.
Condition: A check to ensure FilenameWithExtension ends with .docx.
Action: "Convert Word Document to PDF" (Word Online Business connector).

The Problem:
The "Get files" step successfully identifies the target .docx file (verified in the execution logs). However, the "Convert Word Document to PDF" action fails with a "Not Found" error. Even though there are no sub-folders in this test, the connector cannot locate the document.

Technical Details & Attempted Fixes:

Pathing: I have tried passing the {Identifier} chip, the ID (integer), and the {FullPath}.
Formatting: I have tried prepending a leading forward slash to the path using concat('/', items('Apply_to_each')?['{FullPath}']).
Raw Input Inspection: The raw inputs for the failed "Convert" action show a valid absolute path: "/TestFolder/TargetFile.docx".
Loop Behavior: The "Get files" output confirms only the .docx is being passed to the conversion branch due to the filters, yet the 404 persists.
Connections: I have deleted and recreated the Word Online Business connection and the action card to refresh the metadata.

Despite the path being correct and the file being visible to the SharePoint connector in the preceding step, the Word Online connector refuses to resolve it. Has anyone encountered this where the Word Online API fails on a file that the SharePoint "Get files" action clearly sees in a standard flat folder?

Categories:

Building flows

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Suggested answer

frago 226 on at

Like
a
(0)

Report
Copy link

Link copied!
Hi @MC-02040828-0

It sounds like a common quirk with the Word Online Business connector: it doesn’t always accept the {FullPath} or ID directly from “Get files (properties only)”—it specifically requires the file content instead of just the metadata. That’s why the 404 appears even though SharePoint can see the file.

Here’s a straightforward fix:

After your “Apply to each” / condition, add a “Get file content using path” (SharePoint) action.

Path: items('Apply_to_each')?['{Path}'] or {Identifier}.

Feed the output of that action (the file content) into the “Convert Word Document to PDF” action.

In the Word Online action, use the File Content field instead of File Identifier or Path.

This usually resolves the 404 because Word Online needs the actual file bytes, not just a pointer from “Get files.”

Optional tip: If you plan to expand to nested folders, keep using {Identifier} from “Get files” but always get the content first before conversion.

------------------------------------------------------------

If this solved your issue, please mark it as ✅ Accepted Answer.
If it helped, feel free to give it a 🩷 Like!

Best regards,
Piotr

Was this reply helpful? Yes No
MC-02040828-0 4 on at

Like
a
(0)

Report
Copy link

Link copied!

Thank you, Piotr, for your reply. In the end I did get it working with this solution:

Covert Word Documents to PDF requires three fields - Location, Document Library, and File.

The "File" field was the problem, I had tried inserting various chips such as "Identifier" and "Path" / "Full Path" but finally the one that worked was "DriveItemID"

Also relevant was the fact that converting Word to PDF from within a PA flow turned out to not be the best approach. I used a PowerShell script to batch convert the 69 files (this is a three-times-a-year task for me) from Word to PDF, so my PA flow doesn't need to check for DOCX or convert it to PDF anymore.

Was this reply helpful? Yes No