29 posts tagged with "Power Automate"

A Custom AI Analyzer Template is a named JSON schema you define in the PDF4me dev portal that tells the AI which fields to extract from a specific document type. This walkthrough builds an Analyzer for PDF4me's own SaaS subscription invoices (33 fields: vendor address block, Swiss MWST rate, subscription Id, line items, discount details), then calls it from a 3-step Power Automate flow that reads a PDF from Dropbox and returns structured JSON.

The built-in default_invoice_extraction covers generic invoices, but real AP teams have vendor-specific layouts, custom line-item columns, jurisdiction-specific tax fields, and subscription metadata that the generic schema misses. Building a custom Analyzer once gets you exact-match extraction forever, no per-field prompting required, no follow-up logic to clean up the response.

Email-to-PDF archive is a Power Automate flow that fires on every new inbound Outlook email, converts the message body and every attachment to PDF, merges them into one timestamped consolidated PDF, and writes the result to Dropbox for long-term compliance retention. Seven actions. No code. One file per email, body first then attachments in order. The output is named merge-YYYYMMDD-HHmmss.pdf so every archive entry is uniquely sortable.

Audit teams, records-management leads, and compliance officers need email evidence preserved in a tamper-evident, searchable format that survives Exchange retention policies. Native Outlook export is manual, file-by-file, and loses attachments to separate files. This walkthrough builds the no-code alternative: every email that lands becomes a single consolidated PDF, automatically, with the original .eml and attachments still in Outlook for legal hold but the archive PDF as the authoritative records copy.

The painful part of "merge these PDFs" tickets is not the merging, it is knowing what is in the folder at run time. Names change, files come and go, somebody adds a fifth document at 4:55 pm. This walkthrough builds the exact pattern in Power Automate with PDF4me Merge multiple PDF files, Dropbox, and a single Apply to each loop. Six flow actions. Zero hardcoded filenames. Every PDF currently in the watched folder gets stitched together the moment a new file lands, and the output name carries the file count so each run is uniquely identifiable.

The painful part of email-driven workflows is not the email, it is everything that comes with it. The body holds the context (who sent it, why, what to do), the attachments hold the artefacts (the invoice, the form, the signed contract), and storing them separately means future-you needs three clicks to reconstruct the message later. This walkthrough builds the exact pattern in Power Automate with PDF4me Convert to PDF, PDF4me Merge multiple PDF files, Outlook, Dropbox, and a single Apply to each loop. Seven flow actions. One incoming email lands. One consolidated PDF goes out, body first then attachment by attachment, timestamped and dropped into your archive folder automatically.

The painful part of bulk mailouts is not writing the letter, it is stitching the personalised copies together so finance, HR, or operations get one clean PDF instead of fifty attachments. This walkthrough builds the exact pattern in Power Automate with PDF4me Generate Documents (Multiple), Merge multiple PDF files, Dropbox, and a single Apply to each loop. Seven flow actions. One DOCX template. A JSON array of recipients. Out the other end falls one consolidated PDF, one page per recipient, named and uploaded back to Dropbox automatically.

Germany's Wachstumschancengesetz (Growth Opportunities Act) turned ZUGFeRD-style hybrid e-invoices from a "nice to have" into a B2B requirement. From 1 January 2025 every German business must be able to receive structured e-invoices, with full sending obligations phased in by 2028. The fastest path for any Microsoft 365 team is a five-action Power Automate flow: Manually trigger → Dropbox Get file content (PDF) → Dropbox Get file content (XML) → PDF4me Create ZUGFeRD Invoice → Dropbox Create file. The XML payload is embedded inside a PDF/A-3 archival shell, producing one file that humans open and accounting systems parse. This walkthrough uses the exact screenshots captured in the canvas: /pdf4metest/sample/10 page.pdf for the visual carrier and /pdf4metest/zugfred invoice/version2.xml for the structured data, with the hybrid output landing in /pdf4meoutput under a unique GUID-prefixed name. Production-ready in under 10 minutes.

Every Swiss invoice must carry a Swiss QR Bill so banks and accounting software can scan and process the payment automatically. With Power Automate and PDF4me the addition is a four-action flow: Manually trigger, Dropbox Get file content, PDF4me Barcode - Create SwissQR Bill, Dropbox Create file. The screenshots below walk through the exact run captured in the canvas. A 10-page invoice in /pdf4metest/sample becomes a Swiss-compliant invoice with the payment slip appended and uploaded to /pdf4meoutput with a unique file name. Production-ready in under 10 minutes.

Most Swiss QR-bill tutorials put the payment slip on page 1 (or append it to the end). Real invoices often need it somewhere in the middle: a 10-page contract pack where the QR-bill belongs right after the summary, or a quarterly statement where the slip should follow the cover page. The PDF4me Power Automate connector handles that in one action via Paging Options = custom plus a Page Number field. This guide walks through the exact run captured in the canvas: /pdf4metest/sample/10 page.pdf becomes a Swiss-compliant file with the QR-bill inserted as page 3, then uploaded to /pdf4meoutput with a guid-prefixed name so re-runs do not collide. 4 actions, zero code, runs in seconds.

Drop an Excel template that uses Aspose Smart Markers (cells written like &=RootData.Items.ItemName) into Dropbox, paste a matching JSON payload into a Power Automate flow, and the populated workbook lands back in Dropbox with totals already calculated. This guide walks through the exact four-action flow shown in the screenshots: Manual trigger, Dropbox Get file content using path, PDF4me Excel - Populate, and Dropbox Create file. Every field value comes from a real run; the input template, JSON payload, and output workbook are all linked at the end.

A workbook with 5, 50, or 500 sheets can be split into individual .xlsx files in a single Power Automate flow. PDF4me Excel - Separate Worksheets returns an array with one file per sheet; an Apply to each loop fans the writes out to Dropbox, SharePoint, OneDrive, or Dataverse. This guide walks through the exact run shown in the screenshots: a 5-tab Separate.xlsx in Dropbox becomes Sheet1.xlsx through Sheet5.xlsx in an output folder. Total flow: 4 actions, zero code, runs in ~9 seconds end-to-end.

Teams often want a single, reliable PDF after someone saves a spreadsheet to the cloud. This guide builds an automated cloud flow with three actions: Dropbox detects a new file, PDF4me, Convert to PDF turns the workbook into a PDF, and Dropbox, Create file writes the result into an output folder. The walkthrough uses folder /blog data/excel to pdf, sample workbook New Invoice.xlsx, and output path /blog data/excel to pdf/output. Replace those paths with yours, and keep the same wiring.

If you already store filled or fillable PDFs in Dropbox, you do not need to retype what is on the page. This walkthrough wires three steps: you start the flow yourself, Dropbox loads the PDF bytes, and PDF, Extract Form Data (PDF4me) turns AcroForm field values into structured data you can pass to Excel, Dataverse, email, or another API.

The screenshots use Dropbox path /blog data/extract form data from pdf/sample_form.pdf and a PDF4me File Name of Test.pdf. Swap in your folder, file name, and connection, the pattern stays the same.

This guide shows a full Power Automate workflow that reads a base PDF and invoice JSON from Dropbox, generates a ZUGFeRD/Factur-X invoice using PDF4me Create ZUGFeRD Invoice, and writes the final file back to Dropbox.

The screenshot sequence uses these sample paths:

• Base PDF: /blog data/zugferd invoice/simplepdf.pdf
• JSON: /blog data/zugferd invoice/sample-invoice.json
• Output folder: /blog data/zugferd invoice/output

This guide builds an automated cloud flow with two actions: Dropbox, When a file is created watches a folder, then PDF, Validate PDFA (PDF4me) checks whether the uploaded PDF conforms to PDF/A (ISO 19005). The run returns Conformance, IsConforming, and IsPdfA for use in Condition or Switch steps. The screenshots use folder path /blog data/validate pdfa; replace with your own paths.

Invoice and order tables often arrive as PDFs: sometimes scans you cannot sort or filter. Copy-pasting row by row is slow and brittle. Power Automate with PDF4me runs a simple pipeline: pull the file from Dropbox, Convert PDF to editable PDF using OCR so text and tables are machine-readable, Convert PDF to Excel to get a workbook, then Create file back in Dropbox. Five actions. One flow. Tables land in Excel ready for formulas, pivots, and handoff to finance or BI.

This guide uses authentic screenshots and descriptive image captions so you can follow each step and match paths, quality settings, and dynamic content in your own flow.

You have a Word document (e.g. an invoice or letter) and need a Swiss QR Bill payment slip merged onto it so the final PDF is ready to send. Doing it by hand means converting Word to PDF, generating the QR bill, then combining the two. Power Automate and PDF4me do it in one flow: get the Word file from Dropbox, Convert to PDF, Create SwissQR Bill with your creditor and debtor details, get a base PDF (e.g. your invoice layout), Merge two PDF files one over another as Overlay so the QR bill sits on the base, then Create file in Dropbox. Seven actions. One flow. No code.

This guide uses authentic screenshots and descriptive image captions so you can follow each step and match the configuration (paths, file names, and parameters) in your own flow.

You have a fillable PDF form and data in JSON. Manually typing into each field is slow and error prone. Power Automate plus PDF4me automates it: get the template and JSON from Dropbox (or SharePoint), run Fill a PDF Form, and create the filled file. No code. Works with Microsoft 365. Connect storage, map the files, and get a populated form.

You have HTML sitting in Dropbox, SharePoint, or OneDrive. You need a PDF for email, archiving, or sharing. Manually printing to PDF does not scale. Power Automate plus PDF4me turns HTML into PDF in three actions: get the file content, run Convert HTML to PDF, and create the file in your folder. No code. Works with Microsoft 365 and cloud storage. Connect, map the file, and get a ready-to-use PDF.

You have a fillable PDF form, data in JSON, and a signature image. Doing it by hand: fill fields, place the signature, save. Power Automate plus PDF4me automates it: get the template, JSON, and signature from Dropbox or SharePoint; run Fill a PDF Form and Sign PDF; then save the signed document. No code. Perfect for contracts, agreements, and forms that must be filled and signed in one flow.

Reports, contracts, and proposals often live as Word files in Dropbox, SharePoint, or OneDrive. When you need them archived for compliance, audits, or long-term preservation, a raw .docx isn't enough. PDF/A (ISO 19005) is the standard for digital archiving: fonts embedded, no external links, readable for decades. You can't go straight from Word to PDF/A, you must convert to PDF first. In Power Automate, build a flow: get a Word (or Excel, PowerPoint) file from cloud storage, convert it to PDF, compress it, turn that into PDF/A, and save the archival file. Five steps. One flow. No manual export.

You have a PDF, maybe a form with fields, a signed contract, or a scanned document, and it needs to last. Regular PDFs can lose fonts, break links, or change appearance over time. PDF/A (ISO 19005) locks everything in: fonts, images, and color profiles stay embedded so the document stays readable for decades. In Power Automate, you can wire up a flow that grabs a file from a Dropbox path, compresses it, converts it to PDF/A, and saves the archival version to an output folder. Five steps. One flow. No manual conversion.

Invoices land in email, Dropbox, or SharePoint, and someone has to type the numbers into your system. PDF4me AI - Invoice Parser extracts vendor name, invoice number, amounts, dates, and line items from PDF invoices automatically. Wire it into Power Automate: watch a Dropbox folder, parse each new invoice with AI, and create a SharePoint list item with the extracted data. No manual data entry.

You have PDFs in Dropbox, SharePoint, or email, some are plain text, others are scanned or image-based, and you need the text out in one reliable flow. The catch: image-based PDFs have no selectable text. They need OCR first. Once they're searchable, PDF4me Extract Text and Images pulls everything in one call: no second read, no wasted API credits.

This guide walks you through a flow that handles both: trigger → get file content (Dropbox) → Convert PDF to editable PDF using OCR (for scanned docs) → Extract Text and Images (PDF4me). You get the exact output structure and links to troubleshoot and try the API yourself.

You have a multi-document PDF: batch-scanned invoices, mail with separator sheets, or reports with barcode dividers, and you need each document split into its own file. Doing that manually is tedious. PDF4me Split PDF by Barcode detects barcodes in the PDF, filters by text (e.g. starts with PDF4me), and splits before, after, or at the barcode page. In Power Automate, you wire it up in five steps: trigger → get file content (Dropbox) → Barcode, Split Document by Barcode (PDF4me) → Apply to each → Create file (Dropbox).

This guide is fact-checked against the Power Automate UI and the Split PDF by Barcode action reference. Every parameter, path, and output field matches a real run. At the end, we include the raw response structure and links to try the API interactively.

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.

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.