Skip to main content

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.

Related Blog Posts
No blog post yet for this feature — coming soon.
In the meantime, browse the PDF4me blog for tutorials and workflows across every platform.
Visit the blog →

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​

Strictly non-destructive

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.

14 structured fields returned

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.

Wire directly into routing logic

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.

Make PDF4me Get Document Information module showing Connection set to testuser01@pdf4me.com, File set to Map with Dropbox - Download a File option visible, File Name mapped from step 7 File Name, and Document mapped from step 7 Data

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.

ParameterRequiredWhat it doesExample mapping
ConnectionRequiredPDF4me 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
FileRequiredDetermines 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 NameRequiredFilename 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
DocumentRequiredBinary 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?​

  1. Add PDF4me → Get Document Information to your scenario.
  2. Select Connection (or click Add to create one with your API key).
  3. Under File, choose Map.
  4. Map File Name to the filename field from your download step - include the .pdf extension.
  5. Map Document to the binary data field from the same step (usually Data in Dropbox, or the equivalent binary field in SharePoint/OneDrive modules).
  6. 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.

FieldTypeWhat it contains and how to use it
TitleTextTitle stored in the PDF document properties. Empty when not set. Map into an Airtable record or email subject line.
SubjectTextSubject stored in the PDF document properties. Often populated by enterprise document management systems.
Number of PagesNumber (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.
AuthorTextAuthor stored in the PDF document properties. Use in a Router to send files to department-specific folders based on author.
Created UsingTextApplication used to create the original document - for example Microsoft Word or Adobe InDesign.
Produced ByTextApplication that produced the PDF. Differs from Created Using when a Word file was later exported to PDF.
Created DateTextDate and time the PDF was created. Use in a Filter to process only documents created within a target date range.
Modified DateTextDate and time the PDF was last modified. Compare to a stored baseline to detect documents that have changed since last processing.
File SizeNumber (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 EncryptedYes/NoWhether the PDF is encrypted (password protected). Branch password-protected files to a separate path instead of letting a later module fail.
Fast Web ViewYes/NoWhether the PDF is linearized for Fast Web View - useful when files are served for progressive download in a browser.
PDF Compliance LevelTextPDF/A (or other) compliance level of the file, if any. Check it before routing a document into a regulated archive.
Is SignedYes/NoWhether the PDF contains a digital signature. Use it to separate already-signed contracts from documents still awaiting signature.
PDF VersionTextPDF 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.
Route documents to department folders by subject
  1. A new PDF lands in a shared Dropbox inbox folder and triggers the scenario.
  2. Get Document Information extracts the Subject metadata field.
  3. A Make Router checks the subject value against department names (Finance, Legal, HR).
  4. Each branch uploads the file to the matching team folder in Google Drive.
  5. A Slack notification alerts the destination team with the document Title and Number of Pages.
Pre-processing validation gate
  1. A form submission triggers the scenario with an attached PDF.
  2. Get Document Information returns Number of Pages and File Size.
  3. A Filter blocks files over 50 MB or under 1 page from proceeding.
  4. Valid documents continue to the conversion or e-signature module.
  5. Rejected files trigger an email reply asking the submitter to re-upload a smaller version.
Auto-catalog new archive uploads into Airtable
  1. A scheduled scenario iterates over new PDFs in an OneDrive archive folder.
  2. Get Document Information extracts all 14 metadata fields per file.
  3. An Airtable module creates a new record with Title, Author, Created Date, and Number of Pages.
  4. The record links back to the OneDrive file URL for one-click retrieval.
  5. A Filter skips files that already have a matching Airtable record to prevent duplicates.

Practical Tips​

Structural fields are always populated
Number of Pages, File Size, and PDF Version come from the file structure itself, not optional metadata, so they are never empty even on documents with no author-supplied properties.
Empty strings are normal, not errors
Author, Title, Subject, Created Using, and Produced By return empty strings when the document creator never set them. The module does not fail on missing metadata.
File Name and Document only appear after choosing Map
The panel starts with just Connection and File visible. Select Map under File to reveal the File Name and Document mapping fields.
Run Repair PDF first on suspect files
If incoming PDFs may be corrupted or come from an unreliable source, run Repair PDF before this module so metadata reads cleanly instead of returning empty fields.
Created Using and Produced By are often different
Created Using names the authoring application, Produced By names the library or driver that generated the final PDF bytes, useful for distinguishing a Word export from a native PDF tool.

Cheat Sheet​

FieldValue
FileMap
File Name7. File Name
Document7. Data
Always populatedNumber of Pages, File Size, PDF Version
Can be emptyTitle, Author, Subject, Created Using, Produced By

Frequently Asked Questions​

Does this module modify the PDF in any way?+
No. Get Document Information performs a strictly read-only inspection of the file. The module reads the document dictionary and cross-reference table to extract metadata values and returns them as a structured output bundle. No bytes in the source PDF are written, reordered, or removed during this process. The file you map into this module is identical byte-for-byte to what gets passed into any downstream module - you can safely run it on production documents without any risk of altering the originals.
What if the PDF has no metadata fields set?+
Number of Pages, File Size, and PDF Version are always populated because they are derived from the document structure itself rather than optional metadata fields. Author, Title, Subject, Created Using, and Produced By will return empty strings when the document creator did not fill them in - this is common with PDFs generated by automated systems or older software that strips document information during export. The module does not error on empty metadata; it simply returns empty strings for those specific fields.
Can I use the Number of Pages output to branch my scenario conditionally?+
Yes - this is one of the most practical uses of the module. Map the Number of Pages field into a Make Filter condition placed after Get Document Information. For example, set the Filter to pass only when Number of Pages is greater than 20 and route those to a PDF splitting workflow, while shorter documents continue to an email step. You can similarly use File Size to reject oversized uploads before a conversion step, or check Created Date to process only documents created within a target date range such as the current calendar month.
What PDF versions and variants does this module support?+
The module reads metadata from all common PDF versions - PDF 1.0 through PDF 2.0 - as well as PDF/A archival variants including PDF/A-1, PDF/A-2, and PDF/A-3. The PDF Version field in the output tells you exactly which specification the document conforms to (for example 1.4, 1.7, or 2.0). This is particularly useful in compliance workflows where you need to verify that a document meets a required PDF version before it is sent to a regulated archive or long-term storage system.
How do I access a specific metadata field in a downstream module?+
After the module runs, expand the output bundle in the Make mapping panel - each of the 14 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, PDF Version) appears as its own individually selectable token. Click any token to insert it into a field in the next module - for example, map Title into the Subject field of a Gmail step, Number of Pages into a Filter condition, or Author into an Airtable record column. No custom function or JSON parsing is required.

Same Task on Other Platforms​

Get Help​