Read PDF Metadata in Make: Get Document Information
PDF4me Get Document Information is a Make module that reads a PDF and returns 14 metadata fields, title, author, number of pages, file size, and more, without modifying the source file. Use it to route documents by keyword, block oversized uploads before conversion, or auto-catalog archive files into a spreadsheet.
What this module does
PDF4me - Get Document Information reads the metadata and structural properties of any PDF without touching the source file. It returns 14 individual fields - Title, Subject, Number of Pages, Author, Created Using, Produced By, Created Date, Modified Date, File Size, Is Encrypted, Fast Web View, PDF Compliance Level, Is Signed, and PDF Version - as mappable tokens you can wire directly into Make Filters, Routers, database modules, or notification steps. Use it to pre-screen document size before a conversion step, route files by author or department keyword, auto-catalog archive uploads into Airtable or Google Sheets, or surface the page count in an approval email so reviewers know what they're signing off on.
Authenticating Your API Request
Every PDF4me module in Make requires a valid Connection. Create or select one that holds your PDF4me API key so the scenario can call the metadata service securely.
Important Facts You Should Not Miss
The module reads the file structure and returns data. No bytes in the original PDF are written, reordered, or removed. The document you map in is identical to the one passed downstream - safe to run on production files without any risk of altering the source.
Title, Subject, Number of Pages, Author, Created Using, Produced By, Created Date, Modified Date, File Size, Is Encrypted, Fast Web View, PDF Compliance Level, Is Signed, and PDF Version are all available as individual mappable tokens in the output bundle - no parsing step or custom function needed to extract individual values.
Map Number of Pages, Author, or Is Encrypted directly into a Make Filter or Router to branch your scenario based on document properties. Route oversized files to a rejection path, send author-tagged PDFs to matching folders, or divert password-protected files to a separate branch.

Select Map under File, then map File Name and Document from the step that downloaded the PDF.
Parameters
Required: Connection, File Name, and Document. Set File to Map first so both input fields become visible. Binary file bytes are required for Document - a URL string or filename alone will not work.
| Parameter | Required | What it does | Example mapping |
|---|---|---|---|
| Connection | Required | PDF4me API connection used by the scenario to authenticate metadata requests. Click Add and paste your API key if connecting for the first time. | Your PDF4me connection |
| File | Required | Determines how the PDF is supplied. Choose Map to wire File Name and Document from a prior module's output - the most common setup for multi-step scenarios. | Map |
| File Name | Required | Filename with .pdf extension from the source module, supplied when File is set to Map. Map from the file name field of your Dropbox, Drive, or OneDrive step. | 7. File Name |
| Document | Required | Binary PDF content from the download step, supplied when File is set to Map. Must be actual file bytes - not a URL or a filename string. Map from the Data field of Dropbox or the equivalent binary field of SharePoint. | 7. Data |
How Do I Read PDF Metadata in Make?
- Add PDF4me → Get Document Information to your scenario.
- Select Connection (or click Add to create one with your API key).
- Under File, choose Map.
- Map File Name to the filename field from your download step - include the
.pdfextension. - Map Document to the binary data field from the same step (usually Data in Dropbox, or the equivalent binary field in SharePoint/OneDrive modules).
- Save and click Run once. Expand the output bundle - each of the 14 metadata fields is a separate mappable token ready to wire into any subsequent module.
What Metadata Fields Does This Module Return?
The module returns 14 individual metadata fields - each is independently mappable. Title, Subject, Author, Created Using, and Produced By come from the PDF document information dictionary (Section 14.3.3 of the PDF 32000-1:2008 specification), while Number of Pages, File Size, Is Encrypted, Fast Web View, PDF Compliance Level, Is Signed, and PDF Version are read from the file structure itself.
| Field | Type | What it contains and how to use it |
|---|---|---|
Title | Text | Title stored in the PDF document properties. Empty when not set. Map into an Airtable record or email subject line. |
Subject | Text | Subject stored in the PDF document properties. Often populated by enterprise document management systems. |
Number of Pages | Number (whole) | Number of pages in the PDF. Use in a Filter to block files over a page limit or route short vs. long documents to different processing branches. |
Author | Text | Author stored in the PDF document properties. Use in a Router to send files to department-specific folders based on author. |
Created Using | Text | Application used to create the original document - for example Microsoft Word or Adobe InDesign. |
Produced By | Text | Application that produced the PDF. Differs from Created Using when a Word file was later exported to PDF. |
Created Date | Text | Date and time the PDF was created. Use in a Filter to process only documents created within a target date range. |
Modified Date | Text | Date and time the PDF was last modified. Compare to a stored baseline to detect documents that have changed since last processing. |
File Size | Number (whole) | Size of the PDF file in bytes. Gate on this before a conversion or email step - reject oversized files and notify the submitter to re-upload a compressed version. |
Is Encrypted | Yes/No | Whether the PDF is encrypted (password protected). Branch password-protected files to a separate path instead of letting a later module fail. |
Fast Web View | Yes/No | Whether the PDF is linearized for Fast Web View - useful when files are served for progressive download in a browser. |
PDF Compliance Level | Text | PDF/A (or other) compliance level of the file, if any. Check it before routing a document into a regulated archive. |
Is Signed | Yes/No | Whether the PDF contains a digital signature. Use it to separate already-signed contracts from documents still awaiting signature. |
PDF Version | Text | PDF version of the file, for example 1.7. Verify conformance before routing to an archive that requires a specific version. |
When Should I Use Get Document Information?
Typical SetupsCommon Make scenario patterns that use Get Document Information to drive routing, validation, or cataloging.
- A new PDF lands in a shared Dropbox inbox folder and triggers the scenario.
- Get Document Information extracts the Subject metadata field.
- A Make Router checks the subject value against department names (Finance, Legal, HR).
- Each branch uploads the file to the matching team folder in Google Drive.
- A Slack notification alerts the destination team with the document Title and Number of Pages.
- A form submission triggers the scenario with an attached PDF.
- Get Document Information returns Number of Pages and File Size.
- A Filter blocks files over 50 MB or under 1 page from proceeding.
- Valid documents continue to the conversion or e-signature module.
- Rejected files trigger an email reply asking the submitter to re-upload a smaller version.
- A scheduled scenario iterates over new PDFs in an OneDrive archive folder.
- Get Document Information extracts all 14 metadata fields per file.
- An Airtable module creates a new record with Title, Author, Created Date, and Number of Pages.
- The record links back to the OneDrive file URL for one-click retrieval.
- A Filter skips files that already have a matching Airtable record to prevent duplicates.
Practical Tips
Cheat Sheet
| Field | Value |
|---|---|
| File | Map |
| File Name | 7. File Name |
| Document | 7. Data |
| Always populated | Number of Pages, File Size, PDF Version |
| Can be empty | Title, Author, Subject, Created Using, Produced By |