How Do You Validate PDF/A When a File Lands in Dropbox? A Two-Step Power Automate Flow.

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.

What this flow produces​

Input: A PDF file created in a monitored Dropbox folder. Output: Validation fields from PDF, Validate PDFA: typically Conformance (e.g. PDF/A-1b), IsConforming, IsPdfA, plus HTTP statusCode when you inspect the raw action output. The action does not modify the file; it only analyzes it.

At a glance: both steps​

Building blocks​

Before you start​

The flow at a glance (two steps)​

1. Dropbox: When a file is created: Folder set to the intake path (example: /blog data/validate pdfa).
2. PDF: Validate PDFA: File Content from the trigger’s file body; File Name from the trigger’s file name field (e.g. encoded name).

Flow overview​

Two connected actions: Dropbox trigger, then PDF4me validation.

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

Flow so far: Trigger only.

1. Create a new automated cloud flow. Search for Dropbox and add When a file is created (wording may vary slightly by connector version).
2. Sign in to Dropbox if prompted.
3. Folder: Enter or browse the folder path. This walkthrough uses /blog data/validate pdfa. Only files created in this folder start the flow.
4. Save the trigger. Open Dynamic content and confirm the trigger exposes at least:

• File Content (or equivalent binary output for the PDF), and
• A file name field (often under headers, e.g. headers/x-ms-file-name-encoded).

5. If File Content is not listed, insert Dropbox: Get file content using path (or Get file metadata + Get file content) after the trigger and map validation inputs from that step instead.

Step 1 screenshot: Parameters tab with required Folder path.

Step 2: PDF: Validate PDFA (PDF4me)​

Flow so far: Trigger → Validate.

1. Add a new step. Search PDF4me (or PDF under PDF4me) and select PDF: Validate PDFA.
2. Connection: Select or create the PDF4me connection and supply the API key when asked.
3. Open the Parameters tab.
4. File Content: From Dynamic content, under When a file is created, select File Content (the PDF bytes). If you used Get file content in step 1, map from that action’s output instead.
5. File Name: Map the filename that includes the .pdf extension. In the reference screenshot this is the Dropbox field such as headers/x-ms-file-name-encoded. If your trigger exposes a plain Name or File name token, use that when it is the full filename.
6. Save the action. Use Test (manual trigger upload or Run trigger) to execute the flow.
7. Inspect the run history for PDF: Validate PDFA. Open Outputs to view the JSON body.

Step 2 screenshot: File Content and File Name mapped from the same trigger.

Output: Conformance and flags​

After a successful run, the action output includes a JSON body (exact structure matches your connector version). A typical conforming result contains:

• conformance: String such as PDF/A-1b naming the level evaluated.
• isConforming: Boolean, true if the file conforms to the checked profile.
• isPdfA: Boolean, additional PDF/A signal; use together with isConforming for routing logic.

Example output (JSON)

Illustrative run output: HTTP 200 and a body with conformance flags.

Output screenshot: use these fields in a Condition to branch pass vs fail.

Next actions (optional): Add a Condition on isConforming equals true. On false, call a Convert to PDF/A flow or notify an owner. On true, move the file, append a row to a list, or end the run.

Quick reference​

Full parameter and output reference: Validate PDFA, Power Automate.

Troubleshooting​

What to try next​

Optional: add a Condition immediately after Validate PDFA on isConforming, then branch to Move file, Send an email, or a child flow that runs Create PdfA.