Convert HTML to PDF Using Power Automate

In this guide, you’ll learn how to convert HTML to PDF using Power Automate and Muhimbi PDF Connector. You can use this flow to convert webpages, URLs, SharePoint pages, and wikis to a PDF document.

Steps to convert HTML to PDF using Power Automate:

  1. Create a flow in Power Automate

  2. Define your action

  3. Create a file

  4. Publish your workflow

This example uses Power Automate to convert HTML to PDF in SharePoint. However, you can save your PDF file to Dropbox, Google Drive, OneDrive, or any platform supported by Power Automate. You can also extend our example by adding additional automation, such as sending the converted PDF as an email.

1: Creating a New Flow in Power Automate

Create a new flow and use the When an item is created or modified trigger for SharePoint Online. Fill out the URL for the site address and select the relevant SharePoint list from the dropdown menu.

Create a new flow

2: Converting HTML to PDF

Insert Muhimbi’s Convert HTML to PDF action and fill it out as shown in the screenshot displayed below. You’ll need to substitute the Source URL or HTML, User name, and Password fields with suitable values. Make sure that for SharePoint Online conversions, Print is selected as the Media type.

Convert HTML to PDF

3: Creating a File

Insert a Create file action to write the converted file back to SharePoint Online or your desired destination.

Create a file

4: Publishing the Workflow

Publish the workflow and create or update a list item in the specified list. After a few seconds, the flow will trigger and a PDF file will be generated.

Troubleshooting/Caveats

HTML isn’t 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’s possible to display lists and libraries in modern or classic mode. Modern view is undergoing constant change (by Microsoft), and some modern view pages will convert fine, while others don’t. As a result, we currently only support the conversion of pages displayed in classic view.

  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, including our HTML converter. If your environment uses MFA, create an app password for HTML conversions, or disable MFA on your HTML conversion account.

  3. HTML conversion option isn’t displayed — The option to convert the current page to PDF is only available in classic SharePoint pages. Modern pages currently don’t provide the ability to extend the personal actions menu. As soon as Microsoft makes this functionality available, we’ll add it.

  4. PDF layout doesn’t match — By default, the page being converted is optimized for print/PDF output. If you prefer for a PDF to look exactly like what’s displayed onscreen, including user interface elements, set the Media Type to Screen in the HTML conversion configuration screen.

  5. User-modified content isn’t converted — The converter doesn’t 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 isn’t aware of the user carrying out the HTML conversion. Don’t specify accounts that display more information than what users need to have access to.

Additional Resources

For more information, refer to the following resources.

Power Automate Templates

Articles