16 posts tagged with "n8n"

Every Swiss invoice must carry a Swiss QR Bill (also called Swiss QR payment slip) so that banks and accounting software can scan and process the payment automatically. n8n and PDF4me make that generation fully automatic. This guide walks through two production-ready workflows: one that overlays the QR slip onto an existing PDF already in Dropbox, and one that generates a standalone QR Bill document from payment data alone with no background PDF required. Both run in under 10 minutes to set up.

This guide wires a four-node n8n workflow you can test with Execute workflow: pull an .xlsx from Dropbox, run PDF4me – Convert to PDF on the binary payload, then upload the resulting PDF to an output path. The screenshots use /blog data/excel to pdf/new invoice.xlsx as the source and /blog data/excel to pdf/output/Excel to Pdf.pdf as the destination filename. Swap paths and names to match your workspace.

This walkthrough builds a four-node n8n workflow: you run it manually, download a fillable PDF from Dropbox, extract field values with PDF4me – Extract form data from PDF, then upload a small text file back to Dropbox built from expressions (for example, name, email, and price). The sample paths match the screenshots: PDF at /blog data/extract form data from pdf/sample_form.pdf, text output at /blog data/extract form data from pdf/output/Form data.txt. Adjust paths to match your account.

This guide builds an n8n workflow that takes invoice data as JSON, creates a ZUGFeRD/Factur‑X invoice with PDF4me, and uploads the final PDF to Dropbox.

You will wire three core parts:

1. push invoice JSON into PDF4me (so you get a stable document URL),
2. generate the ZUGFeRD invoice from that input,
3. upload the output PDF to Dropbox as a binary file.

Invoice tables and line items often arrive as PDFs. You need them in Excel for filters, formulas, and imports. n8n with PDF4me chains the right operations: Dropbox – Download a file pulls the PDF, Convert PDF to editable PDF using OCR recovers text from scans, Convert PDF to Excel builds the workbook, then Dropbox – Upload a file saves the .xlsx next to your process. Five nodes including the trigger. One execution. No retyping.

This guide uses authentic screenshots and descriptive image captions so you can match credentials, binary field names, and quality settings in your own workflow.

You have a Word file (e.g. 3page.docx) and a base PDF (e.g. demo_5_page.pdf) in Dropbox, and you need a Swiss QR Bill merged on top so the final PDF is ready to send. n8n and PDF4me do it in one workflow: Download a file (Word), Convert to PDF, Create SwissQR bill with creditor and debtor details, Download Base PDF file, Merge two PDF files one over another as overlay, then Upload a file to Dropbox. Six nodes. One run. No code.

This guide uses authentic screenshots and descriptive image captions so you can follow each step and match the configuration (paths, binary fields, and parameters) in your own n8n workflow.

You have a fillable PDF form and data in JSON. Typing into each field by hand is slow. n8n plus PDF4me automates it: download the form from Dropbox, run Fill a PDF Form with JSON, and upload the result. No code. Works self-hosted or on n8n Cloud. Connect Dropbox, paste or map your JSON, and get a populated form.

Regular PDFs can age poorly. Fonts go missing, colors shift, links break. PDF/A (ISO 19005) fixes that: fonts, images, and color profiles are embedded so documents stay readable for decades. In n8n, you can automate the full chain: get a PDF (Dropbox Download a file, Read/Write Files from Disk, or—for a quick test—When clicking ‘Execute workflow’ with Base64 in Compress PDF), run Compress PDF, then Create PDF/A. Add Upload a file when you want the PDF/A back in cloud storage.

You have HTML—from a template, a web page, or an API response. You need a PDF. Manually exporting or copying into Word doesn't scale. n8n plus PDF4me turns HTML into PDF in three nodes: trigger → upload → convert. No servers, no custom code. Paste Base64 HTML, map the URL to the converter, and you get output.pdf—ready to download, email, or store.

In a nutshell: When clicking 'Execute workflow' (trigger) → Upload file to PDF4me (Base64 HTML) → Convert Html to PDF (maps documentUrl from Upload). Output: PDF binary (e.g. 29.2 kB) with Download, JSON, and Table views.

Upload an invoice PDF to PDF4me, then run it through the AI-Invoice Parser. Two nodes. You get a processInvoiceModel with vendor name, invoice number, totals, line items, bill-to details—everything in a structured format you can map to databases, spreadsheets, or the next workflow step. n8n gives you Schema, Table, and JSON views so you can inspect the output however you like.

One PDF, multiple documents inside—batch scans, mail with separator sheets, or reports with barcode dividers. PDF4me Split PDF by Barcode finds barcodes (QR Code, Code 128, Data Matrix), filters by text (e.g. starts with PDF4me), and splits the file at each match. In n8n, you need just two PDF4me nodes: Upload file to PDF4me to host the PDF, then Split PDF by barcode to cut it into individual files. Execute the workflow and get PDF4me Barcode 1.pdf, PDF4me Barcode 2.pdf, and more—ready to download or pass to the next node.

You get a mix of PDFs—invoices, contracts, receipts—and you need them sorted by type so the right workflow handles each one. Doing that by hand doesn't scale.

The fix: Define your classification rules on dev.pdf4me.com (using regex or JavaScript expressions), then run the same classification inside n8n: download a PDF (e.g. from Dropbox) → PDF4me Classify Document → use the returned className to route or organize. Classification lives in your PDF4me account; n8n just sends the file and gets back the class.

This guide has two parts. Part 1 is on dev.pdf4me.com: where to go and how to set up your first class (e.g. pdf4me_invoice with a regex like invoice(.*)). Part 2 is on n8n: a three-node workflow (Trigger → Download a file → Classify document) and how to read the result. All steps and screenshots are fact-checked from the PDF4me and n8n UIs.

If you're using n8n for automation, adding HTML headers and footers to your PDFs is straightforward—four nodes, no code. This guide shows you how to set up an n8n workflow that downloads a PDF from Dropbox, adds your custom header or footer using PDF4me, and uploads the branded file back. You paste HTML directly into the Add HTML header footer to PDF node—no separate header file needed.

You get PDFs—invoices, payment slips—each with a Swiss QR code that holds who’s paying, how much, and which reference. You want those files renamed by that data so you can find and sort them in a snap. Doing it by hand doesn’t scale.

The fix: an n8n workflow that downloads the PDF, uses Read Swiss QR Code (PDF4me) to pull out that structured payment data, merges it with the file, and uploads it with a new name—by creditor, amount, reference, or whatever you need. Same file, better filename, zero manual renaming.

This guide walks you through the full flow: download the PDF, read its Swiss QR code, then merge and upload with a filename built from the data you care about—creditor name and city, amount and reference, or debtor details.

You receive PDFs—shipping labels, inventory sheets, invoices—each with a barcode or QR code holding the tracking number, serial ID, or product code you need. You want them renamed by that value so you can find them later. Doing that by hand? It eats hours.

Sound familiar? You're not alone. Manual renaming doesn't scale.

The fix: an n8n workflow that downloads the PDF, uses Read Barcode From PDF (PDF4me) to extract the value from the barcode or QR code, merges that value with the file, and uploads it with the new name. Same content, new filename—no manual renaming.

This guide walks you through the full flow: download the PDF, read its barcode value, then merge and upload the file with the barcode as the new filename.

You receive PDFs—invoices, contracts, purchase orders, reports—and need them renamed by invoice number, customer name, order ID, or contract reference so you can find them later. Doing that by hand? It eats hours.

Sound familiar? You're not alone. Manual renaming doesn't scale.

The fix: an n8n workflow that downloads the file, uses PDF4me Parse Document to extract the value from inside the PDF, merges that value with the file, and uploads it with the new name—automatically. Same content, new filename. No code required.

This guide walks you through three steps: create a parse template in the PDF4me dashboard, wire up Download → Parse document in n8n, then add Merge and Upload so the file is saved with the extracted value as its name.