Extract PDF Form Data in Make
What this module does
The PDF4me Extract PDF Form Data module reads a filled PDF form and pulls out every field name and its value — text inputs, checkboxes, dropdowns, radio buttons — inside a Make scenario. No manual data entry, no copying values out of PDFs. The extracted data comes back as structured output you can pipe directly into a database, spreadsheet, CRM, or any downstream module.
Authenticating Your API Request
Every PDF4me module in Make needs a valid Connection backed by your PDF4me API key. Add or select a connection before you map files into this module.
Important Facts You Should Not Miss
The field labelled Document / public file URL accepts both a binary PDF buffer from a prior module and a direct public URL to a PDF file. You can map either — just make sure the PDF contains actual filled form fields, not an empty blank form.
This module reads form fields only. It does not extract free text, annotations, or content outside of interactive form fields. If your PDF uses typed text over a scanned image rather than real PDF form fields, use the PDF OCR or Parse Document module instead.
The output returns every field as a key-value pair. Field names come from whatever the PDF creator named them — these are often technical IDs like field_001 rather than readable labels. Test with a sample PDF first to map the field names before building downstream logic.

Map is selected so File Name and Document / public file URL come from the previous module's output — typically a download step from Dropbox, Google Drive, or an email attachment.
Parameters
Required: Connection, File Name, and Document / public file URL are all required. There are no optional parameters.
| Parameter | Required | What it does | Example |
|---|---|---|---|
| Connection | Yes | PDF4me API connection for the scenario. | Your PDF4me connection |
| File | Yes | How the PDF is supplied — Dropbox module or Map from a prior step. | Map |
| File Name | Yes | Filename of the filled PDF, mapped from the prior step. | 1. File Name |
| Document / public file URL | Yes | The filled PDF as a binary buffer or a public URL. The UI accepts both file data and a public file URL. | 1. Data |
Output
| Field | Type | What it contains |
|---|---|---|
Form Fields | Array | All extracted field names and their filled values as key-value pairs. |
Workflow Examples
Workflow ExamplesThree common ways teams use Extract PDF Form Data inside Make.
Email arrives with a filled application PDF → Extract PDF Form Data → map FirstName, Email, and Position fields → create a row in Airtable → send an acknowledgement email to the applicant.
Dropbox watch fires on a new PDF upload → Extract PDF Form Data → append all field values as a new row in Google Sheets → update a summary dashboard → archive the PDF.
Fax-to-email delivers a scanned order form PDF → Extract PDF Form Data → validate required fields are filled → create an order record in your CRM → send an order confirmation to the customer.