5 posts tagged with "power-automate"

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 Power Automate: get a PDF (e.g. from Dropbox) → PDF4me Classify Document → use the returned Class Name to route or organize. Classification lives in your PDF4me account; Power Automate 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 Power Automate: a flow (Get file content using path → PDF - Classify Document) and how to read the result. All steps and screenshots are fact-checked from the PDF4me and Power Automate UIs.

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.

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 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 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.