In the file name I added ‘.PDF’, but every time the output PDF was corrupt and errored like this when trying to open: When testing this flow out I originally didn’t have the convert file action in place. Create file action creates corrupt PDF files The parse JSON action cleans this up and just leaves the body content of the page. Here’s the flow in it’s entirety: Issues & troubleshooting Formatting issues with the send an HTTP request to SharePointĪs mentioned above, when just using the send an HTTP request to SharePoint action, the output contains mark up that isn’t going to make sense within the PDF. This is reflected in the flow below with the condition step.ĭelete file action to remove the temporary HTML file. I set the default value of the choice column to be ‘Site Page’, so that the only pages that get converted are the ones I’m interested in. In my example I didn’t want all the site pages to be converted into PDF files, so I added a choice column to ‘tag’ all the pages that should be converted. A document library to store the output PDF files.

A OneDrive location to temporarily store the SharePoint page outputs.

A modern SharePoint site pages library (these come with every SharePoint site!).

There are several posts online that cover very topic this that I’ll reference at the end, but they didn’t quite do exactly what I wanted – so here’s my take on how to convert SharePoint pages into PDF files! What you’ll need Also part of the brief was that when the SharePoint page is updated, the corresponding PDF file also updates. The converted SharePoint pages didn’t need to be formatted as it was only the body content of a SharePoint page that was needed. Recently I got asked to come up with a way to turn SharePoint pages into PDF files for use in an offline scenario. In this post we step through how you can use Power Automate to convert modern SharePoint pages into PDF files and save them to a document library.

Turn web page into pdf