HTML 2 PDF
DocumentsConvert web pages and raw HTML into PDF documents with html2pdf.app, rendered in headless Chromium with full modern CSS support. Agents produce invoices, statements, and reports that look the way the browser shows them.
What This Integration Enables
Most document toolkits ask you to learn their document model. HTML 2 PDF asks you to know HTML and CSS, which your team already does, and then it refuses to do anything else. Three actions is the entire surface: render a live URL, render a raw HTML string, or queue a render for callback delivery. That narrowness is the argument. Rendering runs in headless Chromium with full modern CSS and JavaScript support, so web fonts, script-driven charts and print stylesheets land in the PDF exactly as the browser shows them, and there is no second layout engine to keep in sync with the first.
The configuration surface is where the finance detail lives. Standard page formats from A0 through A6 plus Letter, Legal, Tabloid and Ledger, or custom pixel dimensions. Pixel margins, content scaling, portrait or landscape, and a choice between print and screen CSS media. HTML header and footer templates that inject print date, document title, source URL and page numbering on every page. A configurable render delay for pages that load their content asynchronously, which is what makes a JavaScript dashboard reliably capturable instead of intermittently blank. Finished documents can carry AES-128 encryption with a separate user password, owner password and granular permission set. Agents built on FlowRunner treat all of that as flow configuration rather than application code, so the statement that goes to a customer is governed by the same connectors discipline as every other step in the run.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Month-End Customer Statements
Billing close publishes the period's account activity. For each account the agent assembles a statement from the existing HTML template, fills in balance, aging buckets and transaction lines, and calls Convert HTML to PDF with a footer template carrying the account number and page numbering. Confidential accounts get AES-128 protection with an owner password that blocks copying and annotation while still allowing print. The stored file URL attaches to the customer record in QuickBooks Online or the billing system of record, and the outbound message goes through Gmail. The controller no longer reviews formatting, because the statement is the same markup the finance team already maintains.
Archiving a Dashboard as Audit Evidence
An operations dashboard is the source of truth for a metric a regulator or an auditor will later ask about, but a dashboard is not evidence because it always shows now. On a schedule, the agent calls Convert URL to PDF against the published dashboard with a render delay long enough for the charts to draw, a header template stamping the capture date, and print CSS media so the layout uses the print stylesheet rather than the screen one. The stored file lands in Amazon S3 under a dated key. What was a screenshot somebody remembered to take becomes a dated artifact with a provenance trail.
Heavy Documents Through the Callback Path
A year-end package runs to several hundred pages and would blow through a synchronous execution window. The agent calls Request PDF With Callback instead. The API acknowledges immediately and later POSTs the finished document to a callback endpoint as JSON containing the base64 PDF and an unchanged state value. This is the one action on the connector that does not store a file in FlowRunner, so the receiving endpoint owns decoding, saving and idempotency, and a failed delivery is retried up to three times. Before the first production run switches to this path, the agent stops and asks a person to confirm where the document is going.
Human-in-Loop Highlight
Request PDF With Callback is the moment a finance document leaves FlowRunner's custody. Every other action on this connector returns a stored file URL inside the platform, where the audit trail already lives. The callback path posts the base64 PDF to an endpoint you nominate, retries a failed delivery up to three times, and never writes a copy to file storage. So when a flow is reconfigured to send statements down that path, the agent pauses and messages the controller in Slack before the first run: "Statement batch for [period] is set to deliver through the callback endpoint at [host] instead of FlowRunner file storage. [N] documents, retried up to three times on failure, no copy retained here. Confirm this endpoint owns customer statements?" A rendering job is repeatable. A statement delivered three times to an endpoint nobody vetted is not. This is the digital andon cord applied to document custody: the agent does the rendering, and a person owns the decision about where the document lands.
Agent Capabilities
3 actionsRendering
2- Convert URL to PDF Renders a publicly reachable web page in headless Chromium and stores the resulting PDF in FlowRunner file storage. The page is fetched server side by html2pdf.app, so it must be reachable from the public internet without authentication. Supports standard page formats or custom pixel dimensions, landscape orientation, pixel margins, HTML header and footer templates with page numbering, content scaling, print or screen CSS media, a render delay for JavaScript-driven pages, and AES-128 password protection. Use it to archive dashboards, published reports and order confirmations as dated documents.
- Convert HTML to PDF Converts a raw HTML string into a PDF and stores it in FlowRunner file storage. This is the action for invoices, statements, contracts and certificates assembled earlier in the flow from a template. Images, stylesheets and web fonts referenced by absolute public URLs are downloaded during the render, and CSS break-after rules control pagination. The same page format, margin, header and footer, scaling, render delay and AES-128 options apply. Returns the stored file URL rather than the raw bytes.
Asynchronous Delivery
1- Request PDF With Callback Queues a conversion to run in the background rather than waiting for the document, from either a public URL or a raw HTML string. The API acknowledges immediately, then POSTs the finished document to your callback URL as JSON containing the base64-encoded PDF plus an optional state value passed through unchanged. Use it for long or heavy documents that would otherwise exceed a synchronous execution window. The callback endpoint must be a publicly reachable HTTPS URL that handles deliveries idempotently, because a failed delivery is retried up to three times, and this action does not store a file in FlowRunner.
Frequently Asked Questions
What can FlowRunner do with HTML 2 PDF?
FlowRunner agents can run Convert URL to PDF, Convert HTML to PDF, and Request PDF With Callback in HTML 2 PDF.
Does connecting HTML 2 PDF to FlowRunner require OAuth?
No. HTML 2 PDF connects to FlowRunner with an API key, no OAuth flow required.
Can HTML 2 PDF trigger a FlowRunner workflow automatically?
HTML 2 PDF doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with HTML 2 PDF
$100 in credits. No card required. Connect in minutes.