How Do You Pull PDF Form Answers into Power Automate? A Simple Dropbox + PDF4me Extract Flow.

If you already store filled or fillable PDFs in Dropbox, you do not need to retype what is on the page. This walkthrough wires three steps: you start the flow yourself, Dropbox loads the PDF bytes, and PDF – Extract Form Data (PDF4me) turns AcroForm field values into structured data you can pass to Excel, Dataverse, email, or another API.

The screenshots use Dropbox path /blog data/extract form data from pdf/sample_form.pdf and a PDF4me File Name of Test.pdf. Swap in your folder, file name, and connection—the pattern stays the same.

What you get when it works​

On a successful run you typically see HTTP 200 in the action output and a JSON body where field names from the PDF appear as keys with their filled values as strings (or similar). In the reference run below, keys such as customer_name, email, item, quantity, and price mirror the form definition in sample_form.pdf. Your PDF will emit your field names—treat the screenshot as one real example, not a fixed schema.

At a glance: all three steps​

Why this layout is easy to live with​

Before you start​

The flow at a glance (three steps)​

1. Manually trigger a flow — Run while you design and test.
2. Get file content using path (Dropbox) — Loads sample_form.pdf (or your file) as binary content.
3. PDF – Extract Form Data (PDF4me) — Consumes that content and returns field values in the output JSON.

Flow overview​

Three-step chain: trigger → Dropbox file bytes → PDF4me extraction.

Step 1: Get file content using path (Dropbox)​

Flow so far: Trigger → Get file content.

1. Add Dropbox → Get file content using path (wording may vary slightly by connector version).
2. File Path — Point to your PDF. This guide uses /blog data/extract form data from pdf/sample_form.pdf.
3. Under Show advanced options, set Infer Content Type to Yes so the connector treats the payload correctly.
4. Save and Test this step; confirm File content appears in Dynamic content for the next action.

Step 1: path to the PDF in Dropbox and content-type inference enabled.

Step 2: PDF – Extract Form Data (PDF4me)​

Flow so far: Trigger → Get file content → Extract Form Data.

1. Add PDF – Extract Form Data (PDF4me).
2. File Content — From Dynamic content, choose File content (or equivalent) from Get file content using path.
3. File Name — Enter a PDF name with extension, e.g. Test.pdf, or map a dynamic name if your flow creates or renames files. It does not have to match the Dropbox path string; it must be a plausible .pdf label for the job.
4. Save, then run the flow and open the action Outputs.

Step 2: binary from Dropbox mapped into File Content; File Name set for processing.

Output: from PDF fields to JSON you can use​

After a successful run, inspect PDF – Extract Form Data → Outputs. You should see statusCode: 200 and a body that carries the extracted values. Field keys follow the PDF form definition—the example below is exactly what this sample form produced in one run.

Expand: example run output (screenshot + sample JSON)

The connector wraps the usual HTTP-style envelope (statusCode, headers, body). Inside body, look for the object that lists your fields (here formData). You may also see metadata such as isAsync depending on version and run mode.

Reference output: same values appear in Dynamic content for later steps.

{
"statusCode": 200,
"body": {
  "formData": {
    "customer_name": "Mr. Albert",
    "email": "[email protected]",
    "item": "20",
    "quantity": "100",
    "price": "5000"
  },
  "isAsync": false
}
}

Tip: In a follow-up action, use Dynamic content to pick individual fields, or Parse JSON with a schema that matches your form. Numbers often arrive as strings—convert where needed.

Optional next steps: Append to Excel, Send an email with selected fields, HTTP to a line-of-business API, or Update a row in Dataverse—each field is now a first-class token.

Quick reference​

Full parameter list and integration notes: Extract Form Data from PDF — Power Automate. API reference: Extract Form Data from PDF (API).

Troubleshooting​

What to try next​

Production idea: Replace the manual trigger with Dropbox – When a file is created on the same folder, then keep the Get file content and Extract Form Data pair so each new upload is processed automatically.

That covers the essentials: correct binary mapping, a real .pdf filename, and a fillable source file. Reuse the same structure for SharePoint or email triggers, and refer to the Extract Form Data docs when you extend the flow with parsing, storage, or notifications.