91 posts tagged with "PDF4me"

PDF4me Create PdfA is a Power Automate action that rewrites a PDF to the ISO 19005 archival standard. Chained behind Convert to PDF and Compress, it turns a plain SharePoint folder into an archive drop box: anything left there comes back smaller, standards compliant, and safe to keep for decades.

Search for how to archive documents in SharePoint and every result on page one means the same thing: Microsoft 365 Archive, a cold storage tier. That answers where the bytes live and says nothing about whether the file will still open in twenty years. Archiving is a format problem before it is a storage problem, and a PDF full of embedded font references and external colour profiles is exactly the file that renders wrong a decade from now. This flow fixes the format, then shrinks it.

PDF4me Extract Text and Images is a Power Automate action that returns the text layer of a PDF as an array. Paired with OCR upstream and a Compose join downstream, this flow turns every PDF dropped in a SharePoint library into a matching .txt file, ready for AI search.

Search for how to do this and the first result is Microsoft's own PDF actions reference, which describes Power Automate Desktop actions. They do not exist in a cloud flow. That single detail is why the next two results are a Reddit thread and a Power Platform community thread of people asking the same question and not getting a straight answer. This flow is the straight answer, and it runs entirely in the cloud on standard-tier connectors.

PDF4me Split PDF by Text is a Power Automate action that cuts one PDF into several files wherever a text marker appears. This flow watches a SharePoint folder, splits each new scan on a Serial#: marker, then loops the results into Dropbox. One batch scan becomes three named files, with no manual page picking.

Anyone who runs a scanner knows the problem. Somebody drops a stack of documents in the feeder, hits scan once, and you get back a single PDF holding twenty unrelated records. Every online splitter on the first page of Google will happily fix that, as long as a human uploads the file, clicks through a page picker, and downloads the pieces. That is fine once. It is not fine when the scanner runs every morning. This flow removes the human from the loop entirely.

PDF4me Generate Document Single is a Power Automate action that renders a Handlebars HTML template plus a JSON payload into a finished HTML document, which the paired Convert HTML to PDF action then paginates into A4. A new SharePoint list row fires the flow, Compose assembles the JSON, and Dropbox stores the invoice PDF named after the invoice number. No premium connector, no code.

Every finance team hits the same wall in Power Automate. The native Convert File action requires a premium license and refuses to touch an HTML template. Adobe PDF Services costs. Encodian costs. matthewdevaney's popular workaround skips HTML entirely and locks you into Power Apps. The pattern below is the one nobody in the top ten of the SERP shows end to end: a SharePoint list column set becomes a JSON payload, a real Handlebars template file lives in /Shared Documents/, and two PDF4me actions do the rendering and pagination for the free-tier connector cost.

Handlebars template rendering: PDF4me vs the alternatives​

The comparison every Power Automate architect makes before picking a connector for invoice PDFs:

Fill a PDF Form is a Power Automate action that takes a fillable PDF template plus a JSON payload and returns the same PDF with every field pre-populated. Add PDF - Sign and a SharePoint When an item is created trigger and the whole invoice-generation flow becomes hands-free: a colleague adds a row, Power Automate builds the signed PDF, and Dropbox stores it under a timestamped filename.

The painful part of invoice-style workflows is not the PDF, it is the manual step in the middle. Someone opens the template, retypes eight fields from a spreadsheet row, prints, signs, scans back, uploads. Every field is a chance to typo the customer name or drop a zero from the amount. This walkthrough replaces that ritual with seven Power Automate actions: SharePoint fires the trigger, Dropbox supplies the template plus the signature image, PDF4me fills the form and stamps the signature, Dropbox stores the finished file. Real screenshots, exact Compose expression, the SharePoint schema, and the sample signed invoice all downloadable.

PDF4me Excel - Separate Worksheets is a Make action that splits one .xlsx file into a separate workbook per sheet, without VBA or macros. This four-module scenario reads an Excel file from Dropbox, splits it into per-sheet workbooks, iterates over the returned array, and uploads each new .xlsx back to Dropbox with its own filename.

If you've ever inherited a workbook with twenty tabs and needed each tab as its own file, you've probably reached for VBA, a paid desktop splitter, or a very manual "Move or Copy... to new book" ritual. Every option assumes you're going to sit at a laptop and do it once. This walkthrough replaces all of that with a Make scenario that runs on a schedule, works over Dropbox, and hands you clean per-sheet .xlsx files with zero clicks after the first setup.

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 accounts payable is not paying invoices, it is finding the right vendor's invoice three weeks later when finance asks. Every supplier names files differently. Half are invoice.pdf. The other half are INV-2089-FINAL-v3.pdf from a vendor who switched naming conventions four times. The fix: let AI read the supplier name off every invoice the moment it lands, then rename the file before it goes into long-term storage. This walkthrough builds that exact pattern in Zapier with PDF4me AI - Document Parser and a 2-line Code by Zapier step. Five Zap steps. Real screenshots. The supplier name becomes the filename. Audit-ready folder. Search just works.

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.

The painful part of accounts payable is not paying invoices, it is finding the right invoice in storage when somebody asks for it three weeks later. Every vendor names files differently, every scan is untitled (3).pdf, every Dropbox folder turns into a pit. The fix is to let the AI read the invoice the moment it lands, pull out the customer name, and rename the file before it ever hits long-term storage. This walkthrough builds the exact pattern in Zapier with PDF4me AI - Document Parser, Dropbox, and a 2-line Code by Zapier step. Five Zap steps. Real screenshots from a working Zap. The vendor name becomes the filename. Search just works again.

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.

The hardest part of vendor-invoice automation has always been the file naming. A folder full of 2030703747 (1).pdf and Scan_2026-04-12_invoice.pdf is unsearchable, unsortable, and impossible to audit. PDF4me AI - Document Parser plus a Make Parse JSON module fix that in 4 modules, zero code: the AI extracts the vendor name from the PDF, and the same scenario re-uploads the file as Acme Industries.pdf. The screenshots below walk through the exact run captured in the canvas.

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.

Every Swiss invoice must carry a Swiss QR Bill so banks and accounting software can scan and process the payment automatically. With Zapier and PDF4me the addition is a four-step Zap: Dropbox New File in Folder, Dropbox Find File, PDF4me Create Swiss QR Bill, Dropbox Upload File. The screenshots below walk through the exact run captured in the canvas: a 10-page invoice in /pdf4metest/Swiss-RP becomes a Swiss-compliant invoice with the payment slip appended and saved to /pdf4meoutput. 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.

Every Swiss invoice must carry a Swiss QR Bill so banks and accounting software can scan and process the payment automatically. With Make and PDF4me, the addition is a three-module scenario: Dropbox Download a File, PDF4me Create Swiss QR-bill, Dropbox Upload a File. The screenshots below walk through the exact run shown in the canvas: a 10-page invoice at /pdf4metest/Files/10 page.pdf becomes a Swiss-compliant invoice with the payment slip appended and saved to /pdf4meoutput/. Production-ready in under 10 minutes.

ZUGFeRD 2.0+ (also known as Factur-X in France and XRechnung in the German public sector) is a hybrid PDF/A-3 invoice with the machine-readable XML embedded inside the PDF. One file that both humans and ERP systems can consume. This guide walks through the exact run shown in the screenshots: a base invoice PDF and a ZUGFeRD 2.0+ XML in Dropbox become an EN16931-compliant hybrid e-invoice in /pdf4meoutput/, in 4 Make modules, zero code.

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.

Every Swiss invoice must carry a Swiss QR Bill (also called Swiss QR payment slip) so that banks and accounting software can scan and process the payment automatically. n8n and PDF4me make that generation fully automatic. This guide walks through two production-ready workflows: one that overlays the QR slip onto an existing PDF already in Dropbox, and one that generates a standalone QR Bill document from payment data alone with no background PDF required. Both run in under 10 minutes to set up.

If you sell into Germany, Austria, or any EU buyer that requires structured electronic invoicing under EN 16931, you have probably been asked to send a ZUGFeRD (or Factur-X) invoice. That is a single PDF that is both human-readable and machine-readable, thanks to XML embedded inside the PDF.

This guide shows the full Zapier workflow that watches a Dropbox folder for new uploads, pulls a base PDF and an invoice XML payload, runs PDF4me Create ZUGFeRD Invoice, and writes the finished hybrid file back to Dropbox. Five Zap steps. No code. Reproducible end to end.

The screenshots use these sample paths:

• Trigger folder: /Blog Data/Zugferd Invoice
• Base PDF: /pdf4metest/sample/10 page.pdf
• Invoice XML: /pdf4metest/Zugfred Invoice/version2.xml
• Output folder: /pdf4meoutput

Teams often automate PDF forms the same way: watch a cloud folder for new files, download the PDF bytes, then extract field names and values into structured data for sheets, CRMs, or databases. This guide builds that path in Make (Make.com): Dropbox, Watch Files on /Blog Data/Extract Form Data From PDF/, Dropbox, Download a File with the path coming from the trigger, and PDF4me, Extract PDF Form Data with File name and Document mapped from Download. The run output shows Form Data such as customer_name, email, item, quantity, and price for sample_form.pdf.

Make (Make.com) is a common choice when you want visual scenarios: drag modules, connect them, and map fields without writing code. This guide mirrors a working setup: Dropbox fetches an Excel file, PDF4me converts it to PDF, and Dropbox writes the PDF to an Output folder. The screenshots use /Blog Data/Excel to PDF/sample_excel_file.xlsx and /Blog Data/Excel to PDF/Output/. Your paths can differ; keep the same mapping idea: module 1 feeds PDF4me, module 2 feeds the final Upload.

This guide wires a four-node n8n workflow you can test with Execute workflow: pull an .xlsx from Dropbox, run PDF4me, Convert to PDF on the binary payload, then upload the resulting PDF to an output path. The screenshots use /blog data/excel to pdf/new invoice.xlsx as the source and /blog data/excel to pdf/output/Excel to Pdf.pdf as the destination filename. Swap paths and names to match your workspace.

This walkthrough builds a four-node n8n workflow: you run it manually, download a fillable PDF from Dropbox, extract field values with PDF4me, Extract form data from PDF, then upload a small text file back to Dropbox built from expressions (for example, name, email, and price). The sample paths match the screenshots: PDF at /blog data/extract form data from pdf/sample_form.pdf, text output at /blog data/extract form data from pdf/output/Form data.txt. Adjust paths to match your account.

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 builds an n8n workflow that takes invoice data as JSON, creates a ZUGFeRD/Factur‑X invoice with PDF4me, and uploads the final PDF to Dropbox.

You will wire three core parts:

1. push invoice JSON into PDF4me (so you get a stable document URL),
2. generate the ZUGFeRD invoice from that input,
3. upload the output PDF to Dropbox as a binary file.

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.

Picture this: you already have a multi-page base PDF (your invoice layout, letterhead, whatever lives in demo_5_page.pdf). You also work from a Word file that you want turned into a proper Swiss QR-bill and stamped on top of that base. Copy-pasting PDFs between tools gets old fast.

Here is a Zap that does the boring work: Dropbox wakes up when something new lands, PDF4me converts your Word doc, builds the SwissQR slip, overlays it on the base file, and drops the finished PDF back in a folder you choose. The screenshots below use real paths and names from a test workspace (/pdf4metest/TestRP, 3Page.docx, and so on). Swap them for yours and you are set.

Invoice tables and line items often arrive as PDFs. You need them in Excel for filters, formulas, and imports. n8n with PDF4me chains the right operations: Dropbox, Download a file pulls the PDF, Convert PDF to editable PDF using OCR recovers text from scans, Convert PDF to Excel builds the workbook, then Dropbox, Upload a file saves the .xlsx next to your process. Five nodes including the trigger. One execution. No retyping.

This guide uses authentic screenshots and descriptive image captions so you can match credentials, binary field names, and quality settings in your own workflow.

You have a PDF that should become a PowerPoint deck, maybe a report exported as PDF, or a scan that is not editable slide-by-slide. Doing it by hand means recreating layouts. Make with PDF4me runs a straight line: Dropbox, Download a File pulls the PDF, PDF OCR makes text and layout machine-friendly (especially for scans), PDF to Powerpoint builds the .pptx, then Dropbox, Upload a File saves it beside your source files. Four modules in the happy path. One scenario. Your team opens PowerPoint instead of fighting the PDF.

This guide uses authentic screenshots and descriptive image captions so you can match connections, file sources, quality levels, and upload mapping in your own scenario.

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 file (e.g. 3Page.docx) and a base PDF (e.g. demo_5_page.pdf) in Dropbox, and you need a Swiss QR Bill merged on top so the final PDF is ready to send. Make and PDF4me do it in one scenario: Dropbox, Download a File (Word), PDF4me, Convert to PDF, PDF4me, Create SwissQR Bill with creditor and debtor details, Dropbox, Download a File (base PDF), PDF4me, Merge PDF Overlay (base + Swiss QR layer), then Dropbox, Upload a File. Six modules. One run. No code.

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

Drop a data file (e.g. JSON) into a Dropbox folder and keep a Google Docs template (e.g. Google Docs Template.docx) in the same place. When a new file appears, Make can run automatically: Find Template File gets the template, PDF4me, Generate Document runs twice, once with Data Text (inline JSON) → PDF, once with Data File (the triggered file) → Word, then Upload File saves both. Six modules. Trigger-based. No manual run.

This guide uses authentic screenshots and descriptive image captions so you can follow each step and match the configuration (folder paths, template name, data format, and output file names) in your own Make scenario.

Drop a data file (e.g. JSON) into a Dropbox folder and keep a Google Docs template (e.g. Google Docs Template.docx) in the same place. When a new file appears, Zapier can run automatically: a find file step loads the template, PDF4me, Generate Document runs twice, once with Data Text (inline JSON) → PDF, once with Data File (the file from the trigger) → Word, then Upload File saves both. Six steps. Trigger-based. No manual run.

The screenshots below show the same folder paths, template name, and PDF4me settings you use in Zapier; map each Dropbox or PDF4me field from the previous step’s output (trigger → find template → actions) the way you see in the images.

You have a Word file (e.g. 3page.docx) and a base PDF (e.g. demo_5_page.pdf) in Dropbox, and you need a Swiss QR Bill merged on top so the final PDF is ready to send. n8n and PDF4me do it in one workflow: Download a file (Word), Convert to PDF, Create SwissQR bill with creditor and debtor details, Download Base PDF file, Merge two PDF files one over another as overlay, then Upload a file to Dropbox. Six nodes. One run. No code.

This guide uses authentic screenshots and descriptive image captions so you can follow each step and match the configuration (paths, binary fields, and parameters) in your own n8n workflow.

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.

Drop a Word template (e.g. simple_mail_merge_template.docx) into a Dropbox folder and keep a JSON file (e.g. sample_mail_merge_data.json) in the same place. When a new file appears, Make can run a mail merge automatically: find the JSON, call PDF4me - Generate Document (Template File Type: Mail Merge), then upload the result as Word and again as PDF. Six modules. Trigger-based. No manual run.

Screenshots in this guide match the Make module UI for New File in Folder, Find Json Data File, Generate Document (template plus data file or data text), and Upload File (folder path, file name, and extension).

Drop a Word template (e.g. simple_mail_merge_template.docx) into a Dropbox folder and keep a JSON file (e.g. sample_mail_merge_data.json) in the same place. When a new file appears, Zapier can run a mail merge: find the JSON, call PDF4me, Generate Document (Template File Type: Mail Merge), upload Word, run Generate Document again for PDF, then upload. Six steps. Trigger-based. No manual run.

The screenshots match the folder paths, file names, and PDF4me options you set in Zapier, map trigger → find JSON → PDF4me → upload using the same values shown in each image.

You have a Word template (e.g. simple_mail_merge_template.docx) with merge placeholders and data in JSON (e.g. sample_mail_merge_data.json). Manually filling each document is slow and error-prone. With Make and PDF4me, you can automate it: download the template and JSON from Dropbox, run PDF4me, Generate Document with Template File Type: Mail Merge and Output Type: Pdf (or Word), then upload the generated file. Four modules. One scenario. No code.

This guide is organized into In a nutshell, What You Need, step-by-step instructions with screenshots, real-world use cases, Quick Reference, Troubleshooting, and links to the action docs.

You have a Google Docs template with placeholders (e.g. {{name}}, {{course}}, {{date}}) and data in JSON. Manually copying values into each document is slow and scales poorly. With Make and PDF4me, you can automate it: download the template and JSON from Dropbox, run PDF4me, Generate Document with Template File Type: Google Docs and Output Type: Pdf (or Word), then upload the generated file. Four modules. One scenario. No code.

This guide is organized into In a nutshell, What You Need, step-by-step instructions with screenshots, real-world use cases, Quick Reference, Troubleshooting, and links to the action docs.

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. Manual flow: fill the fields, place the signature, save, upload. Make plus PDF4me does it in one scenario: download the template, JSON, and signature from Dropbox (or Google Drive); run Fill a PDF Form and Sign PDF; then upload the signed document. No code. Ideal for contracts, agreements, and any form that must be filled and signed before delivery.

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.

You have a fillable PDF form, invoices, contracts, certificates, and data in JSON. Manually copying each value is tedious and error-prone. Make plus PDF4me automates it: download the blank form and JSON from Dropbox, run Fill a PDF Form with JSON input, and upload the completed PDF. No code, no servers. Connect storage, map file and data, and get a populated form.

You have a fillable PDF form and data in JSON. Typing into each field by hand is slow. n8n plus PDF4me automates it: download the form from Dropbox, run Fill a PDF Form with JSON, and upload the result. No code. Works self-hosted or on n8n Cloud. Connect Dropbox, paste or map your JSON, and get a populated form.

You have a fillable PDF form in Dropbox and JSON data ready. Typing into each field by hand is slow. Zapier plus PDF4me automates it: when a new PDF appears in a folder, run Fill a PDF Form with JSON, and upload the result. No code. Works with Dropbox, Google Drive, and thousands of apps. Connect your storage, map the template and JSON, and get a populated form.

You have HTML, from a template, a form, or cloud storage. You need a PDF for email, archiving, or distribution. Manually exporting doesn't scale. Make plus PDF4me turns HTML into PDF in three modules: download the file from Dropbox (or Google Drive), run Convert HTML to PDF, and upload the result. No code, no servers. Connect your storage, map the HTML file, and get a ready-to-use PDF.

Regular PDFs can age poorly. Fonts go missing, colors shift, links break. PDF/A (ISO 19005) fixes that: fonts, images, and color profiles are embedded so documents stay readable for decades. In n8n, you can automate the full chain: get a PDF (Dropbox Download a file, Read/Write Files from Disk, or, for a quick test, When clicking ‘Execute workflow’ with Base64 in Compress PDF), run Compress PDF, then Create PDF/A. Add Upload a file when you want the PDF/A back in cloud storage.

You have HTML, from a form (e.g. JotForm, Typeform), a template, or a web hook. You need a PDF for storage, email, or compliance. Manually saving as PDF doesn't scale. Zapier plus PDF4me turns HTML into PDF in one trigger and one action: when a new HTML file appears (or a form is submitted), run Convert HTML to PDF and get a ready-to-use PDF. No servers, no code. Connect Dropbox, Google Drive, or your form app; map the HTML file; done.

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 HTML, from a template, a web page, or an API response. You need a PDF. Manually exporting or copying into Word doesn't scale. n8n plus PDF4me turns HTML into PDF in three nodes: trigger → upload → convert. No servers, no custom code. Paste Base64 HTML, map the URL to the converter, and you get output.pdf, ready to download, email, or store.

In a nutshell: When clicking 'Execute workflow' (trigger) → Upload file to PDF4me (Base64 HTML) → Convert Html to PDF (maps documentUrl from Upload). Output: PDF binary (e.g. 29.2 kB) with Download, JSON, and Table views.

Reports, contracts, proposals, often they sit as Word files in Dropbox or other cloud storage. When you need them archived for compliance or retention, a raw .docx isn't enough. PDF/A (ISO 19005) is the standard: fonts embedded, no external links, readable for decades. You can't jump straight from Word to PDF/A, you need to convert to PDF first. In Make, wire up a scenario: download a Word (or Excel, PowerPoint) file from Dropbox, convert it to PDF, compress it, turn that into PDF/A, and upload the archival file. Five modules. One scenario. No manual export.

Contracts, reports, proposals, many start as Word files. When you need them archived for compliance or long-term storage, a plain .docx won't cut it. PDF/A (ISO 19005) is the standard: 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 Zapier, automate the full chain: watch a folder, convert Word (or Excel, PowerPoint) to PDF, compress it, turn that into PDF/A, and upload the archival file. Five steps. 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.

Tired of manually converting PDFs for your archive? Point Zapier at a folder, and every new PDF gets compressed, turned into PDF/A, and dropped into an output folder. No clicking, no batch runs. PDF/A keeps documents readable for years, everything’s embedded, nothing depends on external fonts or links. Here’s how to wire it up.

Banks keep loan agreements for decades. Courts store electronic filings for generations. Regulators expect records that stay readable even when software and hardware change. PDF/A (ISO 19005) is the standard for that, fonts and images embedded, no external links, no encryption. Your document remains accessible and verifiable for years. In Make, you can automate the whole thing: download from Dropbox, compress (optional), convert to PDF/A, and upload the archival file. Four modules. One scenario.

One PDF, multiple documents inside, batch scans, mail with separator sheets, or reports with barcode dividers. PDF4me Split PDF by Barcode finds barcodes (QR Code, Code 128, Data Matrix), filters by text (e.g. starts with PDF4me), and splits the file at each match. In n8n, you need just two PDF4me nodes: Upload file to PDF4me to host the PDF, then Split PDF by barcode to cut it into individual files. Execute the workflow and get PDF4me Barcode 1.pdf, PDF4me Barcode 2.pdf, and more, ready to download or pass to the next node.

When you scan a stack of documents into one PDF, batch invoices, mail with separator sheets, or reports with barcode dividers, you need each document in its own file. PDF4me’s Split by Barcode action detects barcodes, filters by text (e.g. starts with PDF4me), and splits before, after, or at the barcode page. In Zapier, you can wire this into a three-step Zap: watch a Dropbox folder, split the PDF, and upload the results as individual files or a single ZIP.

Scanned invoices, faxed forms, or screenshots saved as PDFs, they look like documents, but the text is just pixels. You can’t select it, copy it, or feed it into your Zap. The workaround: run OCR first to make the PDF searchable, then extract the text. Here’s a three-step Zap that does exactly that, using Dropbox and PDF4me.

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.

When you scan a stack of documents into one PDF, batch invoices, mail with separator sheets, or reports with barcode dividers, you need each document in its own file. PDF4me’s Split by Barcode module detects barcodes, filters by text (e.g. starts with PDF4me), and splits before, after, or at the barcode page, and Make’s Iterator turns the split results into individual files you can upload to Dropbox, Google Drive, or any storage.

This guide walks you through the exact modules, fields, and values to get from one PDF to many, with each split saved as its own file.

PDFs named input.pdf or document.pdf are hard to search. You want the invoice number, customer name, or order ID in the filename, automatically. This guide shows a clean Make scenario that parses the PDF and renames it using the extracted value.

Flow (3 modules): Dropbox, Download a File → PDF4me, Parse a Document → Dropbox, Upload a File. The Parse action returns Parse Info (e.g. KeyName: Invoice #Pdf4me-202503-25041), and you use that value as the new filename.

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 have multiple PDFs in a Dropbox folder and want them merged into a single PDF automatically. The catch: PDF4me Merge Multiple PDFs expects an array of file data, but Dropbox Watch Files returns a list of file metadata, and Download a File returns one file at a time. To bridge that gap, you need Iterator and Array Aggregator: the Iterator processes each file one by one, and the Array Aggregator collects those results into the array that Merge expects.

This guide walks through the full Make scenario, with special focus on how the Iterator and Array Aggregator work and how to wire them to the PDF4me Make connector.

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 Zapier: when a new PDF lands in a folder → PDF4me Classify Document → use the returned Class Name to route or organize. Classification lives in your PDF4me account; Zapier just sends the file and gets back the class.

First, set up your classes on dev.pdf4me.com (e.g. pdf4me_invoice with a regex like invoice(.*)). Then, build the Zap in Zapier: New File in Folder → Classify Document. All steps and screenshots are fact-checked from the PDF4me and Zapier UIs.

You use PDF4me in Zapier to extract data from PDF invoices, but mapping every field from the PDF into your next step can feel unclear. Which action should you use? How do you get vendor name, invoice number, amounts, and dates out of the PDF and into a usable format?

This guide shows a simple, repeatable flow: When a new invoice PDF lands in a Dropbox folder, PDF4me AI - Invoice Parser extracts structured fields (invoice number, vendor name, vendor address, store number, delivery date, subtotal, total, and more). You then upload a text file to the same folder with the extracted data as the file content and the invoice number as the filename. So you get both the original PDF and a small .txt file (e.g. Pdf4me-202503-25041.txt) containing the parsed data, ready for downstream Zaps, spreadsheets, or ERP.

Every step, field name, folder path, and mapping below is fact-checked from the Zapier and Dropbox screenshots. Use it as your step-by-step setup.

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.

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 n8n: download a PDF (e.g. from Dropbox) → PDF4me Classify Document → use the returned className to route or organize. Classification lives in your PDF4me account; n8n 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 n8n: a three-node workflow (Trigger → Download a file → Classify document) and how to read the result. All steps and screenshots are fact-checked from the PDF4me and n8n UIs.

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 with plain pages, reports, invoices, contracts, often need consistent branding: your logo, document metadata, page numbers, or legal footers. Doing that by hand for every file doesn't scale.

Here's the approach: A Zapier Zap in three steps: New File in Folder (trigger) → Add HTML Header/Footer (PDF4me) → Upload File. When a new PDF lands in your folder, Zapier sends it to PDF4me, you paste your HTML in the action, and the branded PDF is uploaded back. No code, just configure, map fields, and turn on the Zap.

Result: A plain PDF like sample_3_page.pdf becomes Header_PDF_ZAP.pdf with a professional header showing Document Type, ID, Title, Author, Date, and Revision, ready to share or archive.

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

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.

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.

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.