Turn Every Inbound Email Into an Audit-Ready PDF Archive in Power Automate: A 7-Step Outlook Workflow

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.

Why-Based Q&A​

What You'll Get​

Input: Any inbound email at the watched Outlook address (here [email protected]) with one or more attachments. This walkthrough uses a short message body ("Hi, Hope you are doing well...") and two DOCX attachments (3Page.docx, Docx_2Pages.docx). Output: A single consolidated archive PDF in /blog data/merge blog template/output/, named merge-YYYYMMDD-HHmmss.pdf. Page 1 is the body. Page 2 onwards is each attachment in attachment order, rendered through Aspose Words.

The incoming email​

The archive folder after two runs​

Page 1 of a merged archive PDF​

What You Need​

The Flow at a Glance​

1. Outlook: When a new email arrives (V3) (trigger).
2. Initialize variable named email (Array).
3. PDF4me: Convert to PDF (Body). Reads the HTML body, returns a PDF.
4. Append to array variable with base64ToBinary on the converted body.
5. Apply to each on triggerOutputs()?['body/attachments']:
   • PDF4me: Convert to PDF the attachment.
   • Append to array variable with base64ToBinary on the converted PDF.
6. PDF4me: Merge multiple PDF files into a single PDF file. Array in, one PDF out.
7. Dropbox: Create file. File Name expression stamps the UTC timestamp.

Complete flow overview​

Seven actions. PDF4me sits in the flow three times: convert body, convert each attachment, merge everything.

Outlook attachment fields (reference)​

The Outlook When a new email arrives V3 trigger exposes these attachment fields you map into the converter:

PDF4me Convert to PDF reads the file extension off name to pick the right renderer (.docx → Aspose Words, .xlsx → Aspose Cells, .pptx → Aspose Slides, images and PDFs handled natively).

Step 1: How do you watch an Outlook inbox for inbound email?​

Flow so far: trigger only.

1. In Power Automate click Create, choose Automated cloud flow.
2. Name the flow (e.g. Email Archive to PDF), pick Office 365 Outlook: When a new email arrives (V3) as the trigger, click Create.
3. Connect your Office 365 mailbox.
4. Expand Advanced parameters and click Show all to reveal filtering options.
5. Configure:
   • To: [email protected] (filter so only mail addressed to this address triggers the flow)
   • Include Attachments: Yes
   • Only with Attachments: Yes

Trigger configuration​

Step 2: Initialize Variable email​

Flow so far: trigger plus Initialize variable.

Open an empty array to collect the body PDF and every attachment PDF.

1. Click + New step, pick Initialize variable.
2. Configure:
   • Name: email
   • Type: Array
   • Value: leave blank

Initialize variable configuration​

Step 3: How does PDF4me render the email body to PDF?​

Flow so far: trigger plus Initialize variable plus Convert to PDF Body.

The Outlook trigger emits the message body as HTML on body/body. PDF4me Convert to PDF reads HTML directly, so the entire conversion is one action call.

1. Click + New step, search PDF4me, pick Convert to PDF.
2. Rename the action to Convert to PDF Body so step 5's Convert to PDF action gets its own clean name later.
3. Connect PDF4me Connect with your API key (first time only).
4. Configure:
   • File Content (expression, click fx): triggerOutputs()?['body/body']
   • File Name: email-body.html

Convert to PDF Body configuration​

The .html extension on the filename tells PDF4me which renderer to use. Send .docx, .xlsx, .png, or .jpg just as easily, the same action handles them all.

Step 4: Append to Array Variable (Email Body)​

Flow so far: trigger plus Initialize variable plus Convert to PDF Body plus Append (email body).

Push the converted body PDF onto the email array as page 1.

1. Click + New step, pick Append to array variable.
2. Rename the action to Append to array variable (email body) for clarity.
3. Configure:
   • Name: email
   • Value (expression): base64ToBinary(body('Convert_to_PDF_Body')?['$content'])

Append email body configuration​

Step 5: How do you loop over every attachment and convert each one?​

Flow so far: trigger plus Initialize variable plus Convert to PDF Body plus Append (email body) plus Apply to each.

Loop over every attachment, convert each to PDF, and append in turn so the final merge respects attachment order.

Step 5a: Apply to each (pick the source)​

1. Click + New step, pick Apply to each.
2. Configure:
   • Select an output from previous steps (expression): triggerOutputs()?['body/attachments']

Step 5b: Convert to PDF (the attachment)​

3. Inside the loop click Add an action, pick PDF4me: Convert to PDF.
4. Configure:
   • File Content (expression): base64ToBinary(items('Apply_to_each')?['contentBytes'])
   • File Name (dynamic content): pick name from the Apply to each current item

The name dynamic-content token resolves at run time to items('Apply_to_each')?['name'], so each attachment is converted using its original filename. PDF4me reads the extension to pick the right renderer.

Step 5c: Append to array variable (the converted attachment)​

5. Below Convert to PDF inside the same loop, Add an action, pick Append to array variable.
6. Configure:
   • Name: email
   • Value (expression): base64ToBinary(body('Convert_to_PDF')?['$content'])

Step 6: Merge Multiple PDF Files Into a Single Archive PDF​

Flow so far: trigger plus Initialize variable plus Convert to PDF Body plus Append (body) plus Apply to each plus Merge multiple PDFs.

The whole email array (body PDF first, then attachment PDFs in attachment order) goes into a single Merge call.

1. Below the Apply to each loop click + New step, search PDF4me, pick Merge multiple PDF files into a single PDF file.
2. Configure:
   • Body/docContent: pick the email variable token
   • Output File Name: Email Attachment Merge Output.pdf

Merge action configuration​

Step 7: Why a Timestamped Filename for the Archive?​

Flow so far: trigger plus Initialize variable plus Convert to PDF Body plus Append plus Apply to each plus Merge plus Create file.

Write the consolidated PDF to Dropbox with a UTC-timestamped filename so every archive entry is a fresh, sortable file. Two emails to the same address in the same second is rare enough that this provides effective uniqueness without needing to embed message IDs.

1. Click + New step, pick Dropbox: Create file.
2. Configure:
   • Folder Path: /blog data/merge blog template/output
   • File Name (expression, click fx): concat('merge-', formatDateTime(utcNow(), 'yyyyMMdd-HHmmss'), '.pdf')
   • File Content: pick the File Content token from the Merge multiple PDFs action

File name expression​

Final action with File Content mapped​

Run the Flow and Verify​

1. Save the flow at the top right.
2. Email a message with one or more attachments to the watched address.
3. Open Run history. The trigger should fire within seconds.
4. Open Dropbox at /blog data/merge blog template/output/. A file named merge-YYYYMMDD-HHmmss.pdf is there.
5. Open the PDF. Page 1 is the body text. Page 2 onwards is each attachment, fully rendered, in attachment order.

Common Variations You Can Add Without Rebuilding​

Email archive: PDF vs EML​

Common questions​

How do I trigger this flow on a shared mailbox instead of a personal inbox?​

Replace the When a new email arrives (V3) trigger with When a new email arrives in a shared mailbox (V2). Pass the mailbox address as the Original Mailbox Address field. The rest of the flow stays identical, every attachment reference and body expression resolves the same way.

What if an email has no attachments?​

The trigger's Only with Attachments Yes filter prevents the flow from firing on body-only emails. If you want to archive body-only emails too, set that filter to No and wrap the Apply to each loop in a Condition: only run it when length(triggerOutputs()?['body/attachments']) is greater than zero. The merge action will still work with just the one body PDF in the array, producing a single-page archive.

How do I include the sender, subject, and received date on page 1 of the archive?​

Before step 3, add a Compose action with an HTML preamble:

<h2>From: @{triggerOutputs()?['body/from']}</h2>
<h2>Subject: @{triggerOutputs()?['body/subject']}</h2>
<p>Received: @{triggerOutputs()?['body/receivedDateTime']}</p>
<hr>
@{triggerOutputs()?['body/body']}

Then point step 3's File Content at the Compose output. Page 1 now carries searchable header metadata.

Will this work with HTML emails containing inline images?​

Yes. PDF4me Convert to PDF renders HTML with inline <img src="cid:..."> references and embedded base64 images. Outlook's body/body includes the full HTML with inline content, so the rendered PDF preserves the visual fidelity of what the recipient saw.

How long does the flow take to run?​

Roughly 10-15 seconds per attachment on a one-page DOCX, plus 5-10 seconds for the trigger and final upload. A typical 2-attachment email completes in 35-45 seconds end-to-end. Power Automate's Apply to each runs sequentially by default for ordered output; if order does not matter and you need speed, set Concurrency Control to 20 in the loop's Settings.

Troubleshooting​

Next Steps​

The same seven-step pattern (trigger then init array then convert body then loop-convert-and-append then merge then save with a timestamp) works for any "email plus attachments to one PDF" automation. Ship one and every inbound message becomes a searchable, sortable, audit-ready archive entry automatically.