Power Automate PDF Generation from a SharePoint List: A Handlebars Template plus HTML to PDF Invoice Workflow
PDF4me Generate Document Single is a Power Automate action that renders a Handlebars HTML template plus a JSON payload into a finished HTML document, which the paired Convert HTML to PDF action then paginates into A4. A new SharePoint list row fires the flow, Compose assembles the JSON, and Dropbox stores the invoice PDF named after the invoice number. No premium connector, no code.
Every finance team hits the same wall in Power Automate. The native Convert File action requires a premium license and refuses to touch an HTML template. Adobe PDF Services costs. Encodian costs. matthewdevaney's popular workaround skips HTML entirely and locks you into Power Apps. The pattern below is the one nobody in the top ten of the SERP shows end to end: a SharePoint list column set becomes a JSON payload, a real Handlebars template file lives in /Shared Documents/, and two PDF4me actions do the rendering and pagination for the free-tier connector cost.
Handlebars template rendering: PDF4me vs the alternatives
The comparison every Power Automate architect makes before picking a connector for invoice PDFs:
| Approach vs PDF4me | Handlebars templating? | HTML to PDF paginator? | Connector tier | Notes |
|---|---|---|---|---|
| PDF4me (this blog) | Yes, Generate Document Single | Yes, Convert HTML to PDF | Standard | Two single-purpose actions, no premium license needed |
| Adobe PDF Services | No | Yes | Premium | Cost per user, no template engine, HTML only |
| Encodian | No native templating | Yes | Premium | Popular but paid per invocation |
| matthewdevaney Power Apps route | Word template only | N/A | Standard | Skips HTML entirely, locked to Power Apps front-end |
Native Convert File | No | Word / Excel only, not HTML | Premium | Cannot render an HTML invoice at all |