Automated invoice PDFs in n8n: from data to a polished document
November 18, 2026
Invoicing is one of those tasks that never gets automated because it feels too bespoke — every invoice has the client's name, line items, a due date, and your logo, so it ends up being assembled by hand in a spreadsheet or a Word template. In n8n, the whole pipeline is three nodes: your data source, a RenderDock node, and an email node.
The workflow
Start with the data. Whether it lives in a Google Sheet, an Airtable base, or a webhook from your booking system, the node that reads it produces a JSON item per invoice. The only other thing you need is a Handlebars template that lays out one invoice:
<h1>Invoice {{invoiceNumber}}</h1>
<p>{{companyName}}<br>
{{companyAddress}}</p>
<table>
<thead><tr><th>Item</th><th>Qty</th><th>Amount</th></tr></thead>
<tbody>
{{#each lineItems}}
<tr><td>{{description}}</td><td>{{quantity}}</td><td>{{amount}}</td></tr>
{{/each}}
</tbody>
</table>
<p><strong>Total: {{total}}</strong><br>
Due by {{dueDate}}</p>
The RenderDock node takes this template plus the JSON item, and outputs a designed PDF: A4 page, hairline table rules, page numbers, your typography. The email node attaches it and sends. Run the workflow on a schedule and your month-end invoicing is a thing that happens while you sleep.
Why a rendering node beats the alternatives
- No spreadsheet exports. The invoice is a first-class PDF from the moment the data exists, not a CSV somebody reformats.
- Consistent design. One template means every invoice looks like your company, not like the default print output of whatever tool made it.
- It composes. The same workflow pattern renders certificates, contracts, statements, and reports — swap the template, keep the pipeline.
Set it up
Install the RenderDock community node in n8n (Settings → Community Nodes → n8n-nodes-renderdock), add your API key in the credentials, and drop the node into a workflow. The free tier covers 200 renders a month — enough to run this pipeline for a small business at no cost. API docs have the full reference.