Fill Existing PDF Forms from n8n Without Rebuilding the Template

Useful takeaways from this story.

It is the wrong tool when a customer, carrier, government office, or employer requires its existing PDF to keep the same layout.

The workflow below handles that second case: n8n receives a PDF and a JSON object.

The workflow JSON is importable and the integration uses normal HTTP Request nodes, so you can inspect every request before running it.

Building the complete brief

The page is ready to read now. The fuller skim-friendly version will appear here automatically.

The useful part

It is the wrong tool when a customer, carrier, government office, or employer requires its existing PDF to keep the same layout. The workflow below handles that second case: n8n receives a PDF and a JSON object. The workflow JSON is importable and the integration uses normal HTTP Request nodes, so you can inspect every request before running it.

How it works

It uploads the binary directly, without embedding base64 in the workflow.
Historical n8n execution screenshot, not evidence of the September strict-mapping update.
An LLM can help interpret an unfamiliar form, but repeated production runs should not have to rediscover the same coordinates.
For recurring forms, open the PDF once, review the detected boxes, give them stable names such as customer_name, invoice_number, and <co...

Example or evidence

Details worth keeping

That is the right tool for invoices and reports you design yourself. It opens the PDF and gets its detected or saved fields. It maps the JSON keys to reviewed field names.

Keep reading in the app

Open the app view to save this story, compare related coverage, and continue from the same source.

Open in app