32 posts tagged with "no-code"

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.

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.

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