11 posts tagged with "file-renaming"

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

This guide shows a simple flow: When a new PDF lands in a Dropbox folder, PDF4me Parse Document extracts the field you need (e.g. invoice number) using a template you define on dev.pdf4me.com. You then upload the same file with a new name—the extracted value. Same content, findable filename. No code.

First, create a parse template on dev.pdf4me.com (e.g. Blog-test with key Invoice No). Then, build the Zap in Zapier: New File in Folder → Parse Document → Upload File. All steps and parameters below are fact-checked from the Zapier and PDF4me dashboards.

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.

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.

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.

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.