Get PDF
AI-generatedSummary
Navigate Puppeteer to the required URL, append any configured query parameters, and print the page or selected pages to a PDF. Store the PDF as binary data on each output item, alongside the response headers, status code, and final URL.
Inputs
- URL (required) — Page to navigate to before printing.
- Property Name (required) — Binary property for the generated PDF; defaults to
data. - Page Ranges — Optional ranges to print, such as
1-5, 8, 11-13. - Scale (required) — PDF rendering scale from 0.1 to 2; defaults to 1.
- Prefer CSS Page Size (required) — Defaults to true, giving page CSS
@pagesizing priority. When false, configure paper dimensions or format; if either height or width is blank, the selected format is used. - Format, Height, Width — When Prefer CSS Page Size is false, choose a paper format or set dimensions with optional units. These controls are shown only in that mode.
- Landscape (required) — Whether to use landscape orientation; defaults to true.
- Margin — Optional top, bottom, left, and right PDF margins.
- Display Header/Footer (required) — Whether to include print headers and footers; defaults to false.
- Header Template, Footer Template — Optional HTML templates used when headers and footers are enabled. Templates can use classes such as
date,title,url,pageNumber, andtotalPages. - Transparent Background (required) — Whether to omit the default white background; defaults to false.
- Background Graphics (required) — Whether to include page background graphics; defaults to false.
- Query Parameters — Optional name/value pairs appended to the URL.
- Options — Browser and navigation settings, including extra request headers, wait condition and timeout, browser endpoint or executable path, device emulation, proxy, launch arguments, and output file name. Batch Size controls how many pages are opened simultaneously; it defaults to 1.
Output shape
One output item per input item, with PDF binary data and JSON metadata.
The PDF is stored under the configured binary property name. JSON includes the navigation response headers, status code, and URL with appended query parameters. Navigation failures or PDF-generation errors are raised as node errors, unless the node is configured to continue on fail.