You get PDFs with Swiss QR codes—payment slips, bills, invoices—and need them organized so you can find them by creditor name, IBAN, reference, or amount, match them to payments, reconcile accounts, or meet audit and archiving needs. Manual renaming doesn't scale.

Sound familiar? You're not alone.

Power Automate can use Dropbox, Google Drive, or SharePoint as the file source. The PDF4me Read SwissQR Code action extracts the data from the QR (creditor, IBAN, amount, currency, reference, debtor, and more), so you can save the file with a dynamic name—no code.

This guide describes the SharePoint automated flow: when a file is created or modified in a document library, the flow runs, extracts the Swiss QR data, and renames the file (e.g. creditor+IBAN that is Test AG_CH0200700110003765824.pdf). The same pattern works with Dropbox or Drive triggers.

This guide walks you through the SharePoint flow step by step.

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.

You're in the middle of a Teams meeting, someone shares a PDF that needs to be converted to Word. Or you're browsing the web and find a PDF that needs compression before emailing. The old way? Download, open another app, process, upload back. The new way? Process it right where you are.

PDF4me Extensions eliminate the context-switching that kills productivity. Instead of juggling multiple applications, you can convert, edit, merge, and optimize PDFs directly within Microsoft Teams and Google Chrome—exactly where your work happens.

Picture this: You're building an order management system. Everything works great until the client asks, "Can we add tracking barcodes to the invoices?" Suddenly, you're down a rabbit hole of barcode libraries, encoding standards, and PDF manipulation quirks.

Sound familiar? You're not alone. Barcode integration is one of those features that seems simple until you actually implement it.

This guide cuts through the complexity. We'll explore practical approaches to adding barcodes to PDFs, when to use which barcode type, and how to avoid common pitfalls.

If you've ever integrated a third-party API, you know the drill: read the documentation, write some boilerplate code, run it, debug the errors, and repeat. It's time-consuming, especially when you're just trying to understand how an API works. That's exactly why we built the PDF4me API Tester—an interactive tool that lets you explore and test our REST API endpoints directly in your browser. No IDE required. No code to write. Just configure your request, hit send, and see real results instantly.