Convert
HTML → PDF
Turns a web page or HTML document into a PDF. Often used right before sending, since fax machines and some inboxes need a PDF rather than a web page.
How it works
Many steps in a flow produce content as HTML, the format of a web page. That is fine for a browser, but not for sending: a fax line needs a PDF, and some recipients expect a proper document they can save and print. This node bridges that gap.
Convert takes the web page or HTML you built earlier and renders it into a clean, fixed PDF, laying it out the way it would look on screen. From there the file behaves like any other document in your flow.
It most often sits just before a delivery step. A common pattern is building a page with a document step, converting it here, then faxing or emailing the resulting PDF.
Common use cases
Real situations where this node earns its place in a flow.
Make a report faxable
Convert an HTML report to PDF so a fax step can send it.
Printable attachment
Render HTML to PDF for a clean, fixed-layout file to email.
Freeze a document
Convert to PDF before storing so it looks the same forever.
Convert in a workflow
A simple example of where this node sits in a flow.
What you set up
- Feed it the HTML or web-page content produced by an earlier step.
- Let it render the layout into a PDF.
- Send the PDF on to a delivery step like fax or email that needs a document, not a web page.
Common questions
Why do I need this before faxing?
Fax can only send a PDF, not a live web page. If your content is HTML, this node turns it into the PDF the fax step requires.
Will the PDF look like the web page?
It renders the page's layout into fixed pages, so it reads much like the on-screen version, now as a document you can save and print.
Settings you configure on this node, stored under data.config in the workflow JSON. Leave a field unset to use its default.
inputFormatExpected format of the upstream artifact to convert.
Type: stringDefault:htmloutputFormatTarget format to convert to.
Type: stringDefault:pdffilenameTemplateTemplate for the output filename.
Type: stringDefault:{merchant}-{date}
How this node appears inside a workflow's nodes[] array (the shape you see in the Developer export / import). A full workflow is { nodes: [...], edges: [...] }.
{
"id": "file-convert",
"type": "card",
"position": {
"x": 160,
"y": 120
},
"data": {
"type": "file-convert",
"kind": "processor",
"title": "Convert",
"subtitle": "HTML → PDF",
"config": {
"inputFormat": "html",
"outputFormat": "pdf",
"filenameTemplate": "{merchant}-{date}"
}
}
}