Swiss QR invoice PDFs—payment slips, bills, receipts—arrive with generic names. You need them renamed by debtor, creditor, amount, or reference so you can search, reconcile, and file them. Manual renaming doesn’t scale.

The fix: A Zapier Zap in four steps—no Find File needed. New File in Folder (trigger) gives you the file directly. Read SwissQR Code (PDF4me) extracts the QR-bill data as JSON. Code by Zapier parses it and pulls out the field you want (debtor ud_Name, creditor cr_Name, IBAN, or reference). Upload File saves the same PDF with the new name. Same file, searchable filename—every time.

This guide walks you through each step. Every field, folder path, and mapping is fact-checked from the Zapier screenshots.

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 PDF4me.com (using regex or JavaScript expressions), then run the same classification inside Make: download a PDF (e.g. from Dropbox) → PDF4me Classify Document → use the returned Class Name to route or organize. Classification lives in your PDF4me account; Make just sends the file and gets back the class.

This guide has two parts. Part 1 is on 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 Make: a two-module scenario (Dropbox Download a File → PDF4me Classify Document) and how to read the result. All steps and screenshots are fact-checked from the PDF4me and Make 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.

If you're already using Make (formerly Integromat) to automate workflows, adding professional HTML headers and footers to your PDFs is straightforward—three modules, no code. This guide shows you exactly how to set up a Make scenario that downloads a PDF from Dropbox, adds your custom header or footer using PDF4me, and uploads the branded file back. You'll use the Add Html Header Footer to PDF action and paste your HTML directly into Make—no separate header file needed.

PDFs landing in your folder as document.pdf or invoice (1).pdf are hard to find and match to the right record. You need the invoice number, PO, contract ID, or customer name right in the filename—without opening every file.

Power Automate can do that. This guide shows you a flow that gets the file from Dropbox, uses PDF4me Parse Document to pull the value from inside the PDF, and saves a new file with that value as the name. No code; same content, findable filename.

This guide walks you through the same three parts as the n8n Parse Document rename guide: create a parse template in the PDF4me dashboard, wire up Get file content using path and Parse Document in Power Automate, then Create file so the file is saved with the extracted value as its name. All steps and parameters below are fact-checked from the Power Automate UI in the screenshots.

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: A Make scenario with five modules: Watch Files (Dropbox) → Download a File (Dropbox) → Read SwissQR Code (PDF4me) to extract the Swiss QR-bill data → Parse JSON so fields like creditor name and IBAN are easy to use → Upload a File (Dropbox) with the same PDF and a new filename built from those fields. Same file, better filename, zero manual renaming.

This guide walks you through each step. All parameters below are fact-checked from the Make UI in the screenshots so you can follow along with confidence.

Add a company logo, document metadata (author, date, revision), or customer-specific footers to your PDFs using Power Automate—no code required. This guide walks you through the full 5-step flow (trigger → get PDF → get header file → Add HTML Header Footer to PDF → create file) with screenshots for every step, then sample HTML snippets you can copy and use for branding, page numbers, and per-customer footers, plus use cases like report headers and reusable templates.

PDFs with barcodes or QR codes—shipping labels, invoices, inventory sheets—often need to be renamed by the value inside the barcode so you can find them later. Doing that by hand doesn’t scale.

Here’s the approach: A Zapier Zap in four steps: New File in Folder (trigger) → Find File → Read Barcodes (PDF4me) → Upload File. You map data from step to step: the file from step 2 goes to Read Barcodes and to Upload; the barcode text from step 3 becomes the new filename. No code—just point, configure, and click Continue.

Result: A file like barcode.pdf in a watched folder becomes e.g. PDF4me Barcode Sample.pdf in your output folder—named by whatever the barcode says.

Every step name, field, folder path, and mapping below is taken from the Zapier UI in the screenshots. Use this as your setup guide from scratch.

PDFs with barcodes or QR codes—shipping labels, invoices, inventory sheets—often need to be renamed by the value inside the barcode so you can find them later. Doing that manually doesn’t scale.

Here’s the approach: A Power Automate cloud flow in four actions: trigger → get file content (Dropbox) → Barcode – Read Barcode from PDF (PDF4me) → create file (Dropbox) with the barcode text as the filename. One expression for the file name; no code. Same PDF, new name.

Result: barcode.pdf in a folder becomes e.g. PDF4me Barcode Sample.pdf in your output folder—named by whatever the barcode says.

Every action name, parameter, path, and the File Name expression below are taken from a real run—use this as a setup guide from scratch.

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 doesn't scale.

The fix: A Make scenario with three modules: download the PDF from Dropbox → read the barcode with PDF4me Read Barcodes from PDF → upload the same file with the barcode text as the new name. No code. Same content, new filename.

Before: barcode.pdf in a folder → After: PDF4me Barcode Sample.pdf (or whatever your barcode says) in your output folder—easy to search and organize.

This guide walks you through each step. All paths, file names, and outputs below match a real Make run so you can follow along with confidence.