15 posts tagged with "Microsoft 365"

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.

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