Skip to main content
PDF4me APIIntegrationsKnowledge BaseExtensionsAPI TesterBlog

HTML File in Dropbox or SharePoint? Power Automate Converts It to PDF. Three Actions, That's It!

· 12 min read
Sankalp Mishra
SEO and Content Writer

You have HTML sitting in Dropbox, SharePoint, or OneDrive. You need a PDF for email, archiving, or sharing. Manually printing to PDF does not scale. Power Automate plus PDF4me turns HTML into PDF in three actions: get the file content, run Convert HTML to PDF, and create the file in your folder. No code. Works with Microsoft 365 and cloud storage. Connect, map the file, and get a ready-to-use PDF.

In a nutshell: Get file content using path (e.g. /blog data/html/sample.html) → PDF4me – Convert HTML to PDF (map File Content from Get file, HTML File Name with .html, Layout Portrait or Landscape) → Create file. Output: PDF ready to store, email, or pass to the next action.

Why-Based Q&A​

Why use Power Automate for HTML to PDF? Power Automate integrates with Microsoft 365, Dropbox, SharePoint, and OneDrive. When HTML lives in a folder, a flow can get it, convert to PDF, and save the result. Ideal for reports, invoices, and certificates without leaving the Microsoft ecosystem.

Why map File Content from Get file content? Convert HTML to PDF needs the actual file bytes. Map File Content from the Get file content action so Power Automate passes the binary to PDF4me, not the path or metadata.

Why PDF4me Convert HTML to PDF? The action preserves CSS, images, and layout. You get Portrait or Landscape control and direct output for Create file. No extra steps when the file is already in your flow.

What You'll Get​

Input: An HTML file in Dropbox, SharePoint, or OneDrive (e.g. sample.html). Output: A PDF file ready to upload, email, or pass to the next action.

What You Need​

  • Power Automate — Open Power Automate. Create a new cloud flow (Instant or Automated).
  • PDF4me API key — Get your API key. Connect it when you add the PDF4me action. First time? See Connect PDF4me to Power Automate.
  • Dropbox, SharePoint, or OneDrive — For the HTML file and output PDF folder. Use the connector that matches your storage.

The Flow at a Glance​

  1. Manually trigger a flow (or When a file is created for automation).
  2. Get file content using path (Dropbox or SharePoint) — Fetches the HTML file from a path.
  3. PDF4me – Convert HTML to PDF — Converts the HTML to PDF. Map File Content from Get file content, set HTML File Name (with .html), and Layout.
  4. Create file (Dropbox or SharePoint) — Saves the PDF to your output folder.

Complete flow overview​

Power Automate flow: Manually trigger a flow, Get file content using path, Convert HTML to PDF, Create file

Four steps in sequence: Trigger, Get file content, Convert HTML to PDF, Create file. Each action shows a green checkmark when configured. The file from Get file content is passed into PDF4me, and the PDF output is saved via Create file.

Step 1: Get the HTML File​

Flow so far: Trigger and Get file content only.

  1. Add Manually trigger a flow (or When a file is created in Dropbox or SharePoint for automation).
  2. Add Dropbox (or SharePoint) → Get file content using path.
  3. File Path — Enter the path to your HTML file, e.g. /blog data/html/sample.html.
  4. Infer content type — Yes (optional).
  5. Run the action to confirm the file is retrieved. The output File Content will be passed to PDF4me.

Get file content using path: Configuration​

Get file content using path: File Path set to HTML file location

Get file content: File Path set to the HTML location. The output File Content (binary) is passed to the Convert HTML to PDF action. Use dynamic content for automation when a new file is created.

Step 2: Convert HTML to PDF​

Flow so far: Get file content → Convert HTML to PDF.

  1. Add PDF4me → Convert HTML to PDF (or HTML to PDF).
  2. File Content — Map File Content from the Get file content action.
  3. HTML File Name — The HTML filename with extension, e.g. sample.html. Must include .html so PDF4me detects the format.
  4. Layout — Portrait or Landscape.
  5. Connect your PDF4me account if prompted.
  6. Run the action to test. PDF4me returns File Content (the PDF binary).

PDF4me – Convert HTML to PDF: File and layout​

Convert HTML to PDF: File Content from Get file content, HTML File Name sample.html, Layout Portrait

Convert HTML to PDF: File Content mapped from Get file content, HTML File Name with .html extension, Layout set to Portrait or Landscape. PDF4me preserves CSS and images from the HTML.

Step 3: Create the File (Save the PDF)​

Flow so far: Get file content → Convert HTML to PDF → Create file.

  1. Add Dropbox (or SharePoint) → Create file.
  2. Folder Path — Enter the output path, e.g. /blog data/html/output.
  3. File Name — e.g. output.pdf or map from the Convert action output.
  4. File Content — Map File Content from the PDF4me Convert HTML to PDF action (not from Get file content; that is the original HTML).
  5. Run the flow. The PDF is saved to your folder.

Create file: Save PDF to output folder​

Create file: Folder Path, File Name output.pdf, File Content from Convert HTML to PDF

Create file: Folder Path, File Name, File Content mapped from Convert HTML to PDF. The PDF is saved to your chosen folder.

Input and Output: What Goes In, What Comes Out​

Here is the HTML input and the generated PDF.

Example HTML input file​

Example HTML file used as input for conversion

Sample HTML input: raw HTML or rendered content. Get file content fetches this file; Convert HTML to PDF preserves CSS, images, and structure in the PDF.

Example PDF output file​

Generated PDF output from Convert HTML to PDF

Generated PDF: same content as the HTML in PDF form. Use Create file to save to Dropbox, SharePoint, or pass to the next flow action.

Use Cases: When to Use HTML to PDF in Power Automate​

Invoices and quotes: Generate HTML from Excel, Dynamics, or a database. Save to a folder; the flow converts to PDF and uploads or emails automatically.

Reports and dashboards: HTML reports from Power BI or templates can be saved in SharePoint. Power Automate converts them to PDF for distribution or archiving.

Certificates and badges: Create HTML certificates from event or training data. Convert to PDF and send via Outlook or store in SharePoint.

Quick Reference: Key Settings​

ActionSettingExample
1. Get file contentFile Path/blog data/html/sample.html
2. Convert HTML to PDFFile ContentFrom Get file content
3. Create fileFile ContentFrom Convert HTML to PDF

For full parameter details, see HTML to PDF — Power Automate.

Troubleshooting​

Convert step: File Content is missing or invalid

Map the actual File Content from Get file content to the Convert HTML to PDF action. Do not use the file path or metadata. The field must contain the binary content.

HTML File Name must include .html

PDF4me uses HTML File Name to detect the format. Include the .html extension (e.g. sample.html).

Create file: map File Content from Convert HTML to PDF

In Create file, map File Content from the Convert HTML to PDF action, not from Get file content. The PDF binary comes from PDF4me.

401, 402, or other API errors

PDF4me Troubleshooting covers 401 (API key), 402 (credits), and more.

What's Next?​

  • Replace the manual trigger with When a file is created in Dropbox or SharePoint to process every new HTML file automatically.
  • Add Send an email after Create file to email the PDF to recipients.
  • Use the same flow pattern in Make or Zapier if you prefer those platforms.

Open Power Automate

Get API Key

HTML to PDF (Power Automate docs)

Add HTML Header Footer (Make)