In this guide you’ll learn how to convert a SharePoint Wiki Page to PDF using a Power Automate. The Flow is triggered when a Wiki page is created in the ‘Site Pages’ folder, where it gets converted to PDF and written to a different MS SharePoint location. Our Flow actions also support the conversion of MS SharePoint Online pages.

Steps to convert your Wiki to PDF using Power Automate:

1. Create a flow in Power Automate
2. Define your action (Convert to PDF)
3. Create File (define were your file will be created)
4. Publish your workflow

It’s also important to note that in this specific example we are converting a SharePoint Wiki Page to PDF in SharePoint using Power Automate. If preferred, you can easily save the converted PDF file to another destination like Dropbox, Google Drive, OneDrive, or any platform supported by Power Automate. You can also extend our example by adding additional automation like sending the converted PDF as email.

On a high level perspective, the workflow will look as follows

Create the following steps in Power Automate:

1: Create a new flow

Create a new Flow and use the SharePoint Online trigger ‘When a file is created in a folder’. Fill out the URL for the site collection and select the relevant folder.

2: Convert HTML to PDF

Insert Muhimbi's ‘Convert HTML to PDF’ action and fill it out as per the screenshot displayed below. You will need to substitute the source URL with ‘x-ms-file-path-encoded' which is the output of ‘When a file is created in a folder’ action., Ensure that the appropriate Username and password is entered in the Advanced options section.

Note: this flow requires a Muhimbi API key. Get a free plan with 75 operations per month or a 30 day free trial with no limitations. Sign up to create your API key.

3: Create a file

Insert a ‘Create File’ action to write the converted file back to SharePoint Online. Select the Site Address and Folder path appropriately. Select ‘Base File Name’ which is the output of ‘Convert HTML to PDF’ action for ‘File Name’ and ‘Processed file content’ which is the output of ‘Convert HTML to PDF’ action for ‘File Content’.

4: Publish the workflow

Publish the workflow and create a Wiki page in the Site Pages folder. After a few seconds, the Flow will trigger and a PDF file of the wiki page will be generated in the target location.

Troubleshooting / Caveats

HTML is not the best format for print or PDF Conversion purposes. Depending on your exact needs and source material, you may need to experiment with various available settings. If you have any questions or require assistance please feel free to contact us.

Please consider the following when using Power Automate:

1. Modern Views: In SharePoint Online it is possible to display Lists and Libraries in Modern or Classic mode. Modern View is undergoing constant change (by Microsoft), as a result we currently only support the conversion of pages displayed in Classic View. Some Modern View pages will convert fine while others don't.

2. Multi Factor Authentication (MFA): An increasing number of SharePoint Online / Office 365 environments are secured using MFA. Although this is a positive development, it gets in the way of automated systems such as our HTML converter. If your environment uses MFA then please create an App password for HTML conversions, or disable MFA on your HTML Conversion account.

3. HTML Conversion option not displayed: The option to convert the current page to PDF is only available on Classic SharePoint pages. Modern pages currently do not provide a facility for extending the personal actions menu. We will make sure it is added as soon as Microsoft makes this functionality available.

4. PDF Layout does not match: By default, the page being converted is optimized for print / PDF output. If you prefer the PDF to look exactly like what is displayed on screen, including user interface elements, then set the Media Type to Screen in the HTML Conversion configuration screen.

5. User modified content is not converted: The converter does not have knowledge about the information currently displayed in the user's browser (e.g. size of the browser window, or custom data entered, but not yet submitted to the server). The converter always requests a fresh copy of the URL and converts that information to PDF.

6. User specific information is missing: HTML Conversion is carried out in the context of the configured user account, though the system is not aware of the user carrying out the HTML conversion. Don't specify accounts that display more information than what the users need to have access to.

Additional Resources

Power Automate Templates