Skip to main content

Save Metadata for a PDF in Make

What this module does

PDF4me — PDF - Save metadata for a PDF writes title, author, creator, producer, subject, and keyword fields directly into a PDF from a Make scenario. Every field is optional — leave any field blank and the existing value in the document is preserved. Map values from prior steps to automate metadata tagging across a whole document library without opening a single file manually.

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 write service securely.

Important Facts You Should Not Miss

Partial updates — leave fields blank to keep existing values

You do not need to re-enter all metadata every time. Any field you leave empty is ignored — the value already stored in the PDF remains. Update only what you need to change.

Title and Keywords affect Google indexing

Google reads PDF metadata when crawling. A populated Title field can appear in search result headings. Keywords contribute to relevance signals. Setting these before publishing PDFs to your website is a direct SEO action.

Visual content is never altered

Metadata lives in the document information dictionary — completely separate from the page content. Changing these fields does not affect what readers see when they open the file.

Make PDF4me PDF - Save metadata for a PDF module showing Connection as Classify Document test, File set to Dropbox - Download a File, Title set to Title1, Author to Author1, Creator to Creator1, Producer empty, Subject empty, and Keywords empty

Fill only the fields you want to update. Empty fields preserve whatever value the PDF already has.

Parameters

Required: Connection and File. All metadata fields are optional — only the values you provide are written into the document.

ParameterRequiredWhat it doesExample
ConnectionYesPDF4me API connection used to authenticate metadata write requests.Your PDF4me connection
FileYesSource PDF. Choose Dropbox - Download a File for a direct Dropbox trigger, or Map to supply filename and binary content from a prior module.Dropbox - Download a File
TitleNoDocument title written into the PDF info dictionary. Appears in viewer title bars and is indexed by Google when the PDF is published on the web.Q4 Financial Report 2025
AuthorNoName of the person or team that created the document. Used for attribution in viewers and document management systems.Finance Department
CreatorNoThe application that originally authored the document — for example Microsoft Word or Adobe InDesign.Microsoft Word
ProducerNoThe tool that generated the final PDF bytes — for example a PDF library or a print-to-PDF driver.PDF4me
SubjectNoShort description of the document subject. Visible in the document properties dialog and used by some search systems.Quarterly earnings summary
KeywordsNoComma-separated keyword tags associated with the document. Contributes to Google indexing and internal search when the PDF is hosted online.finance, Q4, 2025, earnings

Quick Setup

  1. Add PDF4mePDF - Save metadata for a PDF to your scenario.
  2. Select Connection (or click Add to create one with your API key).
  3. Set File to Dropbox - Download a File or Map from a prior module.
  4. Fill in the metadata fields you want to update — Title, Author, Creator, Producer, Subject, Keywords. Leave any field blank to keep its current value.
  5. To automate the values, map them from prior modules — for example, pull the title from an Airtable field or derive it from the filename.
  6. Save and click Run once. The output contains Document Name and Document Data — the PDF with updated metadata properties.

Output

FieldTypeWhat it contains
Document NameStringFilename of the output PDF with updated metadata.
Document DataBufferBinary content of the PDF with the new metadata written in. Map this into an upload, archive, or email module.

Workflow Examples

Workflow ExamplesCommon Make scenario patterns that use PDF - Save metadata for a PDF to tag, standardize, and optimize document properties.
Tag whitepapers before web publishing
  1. A new whitepaper PDF is uploaded to a watched Google Drive folder.
  2. A Google Sheets row with the document title, author name, and SEO keywords is looked up by filename.
  3. Save metadata for a PDF writes the Title, Author, and Keywords fields from the sheet into the PDF.
  4. The tagged PDF is uploaded to the public website folder — Google now has proper metadata to index.
  5. A Slack notification confirms the PDF is live with metadata applied.
Standardize metadata across an archive library
  1. A scheduled scenario iterates over all PDFs in a legacy archive folder.
  2. Get Document Information checks whether the Author field is already populated.
  3. A filter skips files that already have an author; the rest continue.
  4. Save metadata for a PDF writes the organization name into Author and a standard keyword set into Keywords.
  5. The updated files are saved back to the archive, ready for compliant search indexing.
Stamp generated reports with dynamic metadata
  1. A monthly report PDF is generated automatically from a data template.
  2. The scenario maps the current month and year into the Title field (e.g. Sales Report — April 2026).
  3. The department name is mapped into Author; relevant product keywords into Keywords.
  4. Save metadata for a PDF writes all three fields in one step.
  5. The metadata-tagged report is archived to SharePoint and emailed to the distribution list.

Frequently Asked Questions

Do I need to fill in all metadata fields?+
No. Every metadata field is optional. Any field you leave empty is ignored — the value already stored in the PDF stays unchanged. This lets you do partial updates without touching fields you do not want to modify.
Does setting PDF metadata affect how Google indexes the file?+
Yes. Google reads PDF metadata when crawling. A populated Title field can appear in search result headings, and Keywords contribute to relevance signals. Setting these before publishing PDFs to your website is a direct SEO improvement.
What is the difference between Creator and Producer?+
Creator is the application that originally authored the document — for example Microsoft Word. Producer is the tool that generated the final PDF bytes — for example a PDF library or print driver. In most automated workflows these are either set to the same value or left at defaults from the authoring tool.
Does this module alter the visual content of the PDF?+
No. Metadata fields are stored in the document information dictionary, completely separate from the page content stream. Changing them has no effect on what readers see when they open the file.
How does this relate to Get Document Information?+
Get Document Information reads existing metadata and returns it as mappable fields. This module writes new values back in. A common pattern is: read with Get Document Information, adjust values in a Make formula or filter, then write the updated version back with Save metadata for a PDF.

Get Help