Skip to main content
PDF4me APIIntegrationsKnowledge BaseExtensionsAPI TesterBlog

How Do You Turn a Dropbox Excel Upload into a PDF in Power Automate? A Three-Step Flow.

· 16 min read
Sankalp Mishra
SEO and Content Writer

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.

Downloads (sample files)
The short version

1. Dropbox – When a file is created on your intake folder → 2. PDF – Convert to PDF (PDF4me): map File Content and File Name from the trigger → 3. Dropbox – Create file: Folder Path = your output folder; File Name and File Content from the converter output.

Map both inputs on Convert to PDF

File Content must be the file bytes from the trigger (the dynamic value usually named File Content). File Name must include the real extension, e.g. New Invoice.xlsx, so the engine detects Excel. In Dropbox flows, the encoded name token headers/x-ms-file-name-encoded (or the plain name field your connector exposes) is the usual source.

What you are automating​

You turn Excel workbooks dropped into a watched Dropbox folder into PDFs stored elsewhere (here, an output subfolder). The sample sheet lists line items (Laptop, Mouse, Keyboard, Monitor), quantities, unit prices, line totals, and a Grand Total of 1090; the generated PDF preserves that layout for sharing or archiving.

Excel web workbook New Invoice with columns Item Quantity Unit Price Total and Grand Total 1090

Sample source workbook used in this walkthrough.

At a glance: all three steps​

1When file created
2Convert to PDF
3Create file

Why this pattern works​

Event-driven intake

The flow starts when a file appears, so you do not poll folders or run schedules for simple drop-and-convert scenarios.

One conversion action

Convert to PDF accepts many office formats; for .xlsx, PDF4me returns PDF File Content and a suggested File Name you can pass straight into Create file.

Clean separation of input and output

Saving PDFs under output keeps originals and deliveries apart. If your trigger folder includes that subfolder, add a Condition so only Excel files run the converter (see troubleshooting).

Before you start​

Checklist

Folder layout (before and after)​

The intake directory holds the Excel file and an Output subfolder. After a successful run, the PDF appears alongside that structure under output.

Dropbox folder blog data excel to pdf showing New Invoice xlsx and Output subfolder

Before: workbook in the watched folder, output destination ready.

File list showing New Invoice pdf in output folder with size and modified date

After: New Invoice.pdf in output.

The flow at a glance​

  1. When a file is created (Dropbox) — folder /blog data/excel to pdf.
  2. Convert to PDF (PDF4me) — feed File Content and File Name from the trigger.
  3. Create file (Dropbox) — write to /blog data/excel to pdf/output using the converter’s File Name and File Content.
Power Automate flow When a file is created Convert to PDF Create file Dropbox and PDF4me

End-to-end chain: trigger, convert, save.

Step 1: When a file is created (Dropbox)​

  1. Create an automated cloud flow. Add trigger Dropbox – When a file is created (wording may vary by connector version).
  2. Folder — Set the path that should start the flow. This example uses /blog data/excel to pdf.
  3. Save the trigger. In Dynamic content, confirm you see File Content and a file name field (sometimes under headers).
Dropbox When a file is created trigger Folder path blog data excel to pdf

Step 1: intake folder path on the trigger.

Step 2: Convert to PDF (PDF4me)​

Flow so far: Trigger → Convert to PDF.

  1. Add PDF – Convert to PDF (PDF4me). Sign in or select your PDF4me connection.
  2. File Content — Map File Content from When a file is created.
  3. File Name — Map the trigger’s filename token (example: headers/x-ms-file-name-encoded), or any dynamic value that resolves to the full name with .xlsx.
  4. Save the action. Run the flow with a test upload and open Outputs to confirm PDF bytes are returned.
PDF4me Convert to PDF Parameters File Content and File Name mapped from Dropbox trigger

Step 2: binary and filename from Dropbox into PDF4me.

Step 3: Create file (Dropbox)​

Flow so far: Trigger → Convert to PDF → Create file.

  1. Add Dropbox – Create file.
  2. Folder Path — Destination folder for PDFs. This walkthrough uses /blog data/excel to pdf/output.
  3. File Name — Map File Name from Convert to PDF (PDF4me supplies a PDF name, typically the original base name with a .pdf extension).
  4. File Content — Map File Content from Convert to PDF.
  5. Save and run the full flow. Verify the new object in Dropbox.
Dropbox Create file Folder Path blog data excel to pdf output File Name and File Content from Convert to PDF

Step 3: write the converted PDF into the output folder.

Output check: open the PDF​

Expand: rendered PDF preview (sample run)

The exported PDF should reflect the spreadsheet layout: columns Item, Quantity, Unit Price, Total, and the Grand Total row.

PDF view of invoice table with line items and Grand Total 1090

Visual check after conversion: data matches the source workbook.

Quick reference​

#ActionMain mapping
1When a file is createdFolder = intake path (e.g. /blog data/excel to pdf)
2Convert to PDFFile Content + File Name from trigger
3Create fileFolder = output path; Name + Content from step 2

Action reference: Convert to PDF — Power Automate. API: Convert to PDF (API).

Troubleshooting​

Flow runs twice, or PDF retriggers the flow

If the trigger folder contains the output subfolder, some setups still fire on new PDFs. Add a Condition after the trigger (for example, filename ends with .xlsx, or path does not contain /output, depending on what your connector exposes).

Conversion fails or wrong format

Confirm File Name keeps the .xlsx extension. Re-map File Content from the trigger’s binary output, not from metadata or a sharing link.

401, 402, or connector errors

See PDF4me Troubleshooting for API key, credits, and connection issues.

What to try next​

Power Automate

Get API Key

Convert to PDF (docs)

Extract form data (blog)

You now have a complete loop: upload an Excel file, let PDF4me produce the PDF, and store it in a dedicated output folder. Adjust folder paths, add a file-type condition if needed, and keep the official Convert to PDF documentation handy when you change formats or filenames.