9 posts tagged with "no-code"

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.

This guide is fact-checked against real Make screenshots: New File in Folder, Find Json Data File, Generate Document (template + data file or data text), and Upload File (with 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.