Skip to main content
PDF4me APIIntegrationsKnowledge BaseExtensionsAPI TesterBlog

Extract Metadata from Word in Zapier

PDF4me Extract Metadata is a Zapier action that reads title, author, subject, keywords, creation and modification dates, page count, word count, and any custom properties from a Word document, without opening the file. Use it for document cataloging, compliance tracking, CMS population, or routing based on metadata. It returns a structured Metadata object instead of a file.

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​

To access the PDF4me Web API through Zapier, every request must include proper authentication credentials. Authentication ensures secure communication and validates your identity as an authorized user, enabling seamless integration between your Zapier workflows and PDF4me's Word metadata extraction services.

Get your API Key

Important Facts You Should Not Miss​

Only File is required
File Name and Culture Name are both optional in the Zapier configuration.
Returns metadata, not a file
The output is a Metadata object with nested properties. There is no File Url in the response, this action does not modify or return the document itself.
Custom properties are included
Any custom document properties added through Word's Advanced Properties dialog appear in the Metadata object alongside the standard fields.
Map File from previous steps

Use the + button next to File and File Name to map from earlier Zap steps (e.g., Google Drive, Dropbox, or a trigger). The Word file must provide full content, not "Exists but not shown" references.

File: (Exists but not shown)

If you see "File: (Exists but not shown)" in the File field and get errors, select the option that provides the full file content instead. See Zapier & Power Automate Tips for details.

PDF4me Extract Metadata Word Zapier - Document, File Name
Only File carries an asterisk. File Name and Culture Name are optional.

What Are the Key Features of Extract Metadata?​

  • Built-in Properties: title, author, subject, keywords, company
  • Date Information: creation date, modification date, last print date
  • Document Statistics: page count, word count, character count
  • Custom Properties: extract user-defined custom document properties
  • JSON Output: structured JSON format for easy integration

Parameters​

Complete list of parameters for the Extract Metadata action. Parameter names match the Zapier configuration UI shown in the screenshot above.

Quick setup checklist
  1. Map File and File Name from a previous step
  2. Optionally set Culture Name if regional date formatting matters
ParameterRequiredWhat it doesExample
FileRequiredWord document to read metadata from. Map from a previous step. Must provide full file content.[4. File from Step 4]
File NameConditionalWord filename with .docx or .doc extension.document.docx
Culture NameConditionalLocale used when interpreting region-specific values in the metadata.en-US

Important: Only File is required. Map File Name from a previous step's filename output when available.

What Does Extract Metadata Return?​

The PDF4me Extract Metadata action returns a Metadata object, not a file, containing document properties. Map individual metadata fields to your next Zap steps for cataloging, compliance, or CMS integration.

Metadata (Object)

JSON object with Title, Author, Subject, Keywords, CreatedDate, ModifiedDate, PageCount, WordCount, and any custom properties. Map nested fields, for example Metadata.Title or Metadata.Author, to next steps.

FieldTypeWhat it contains
Job IdStringUnique identifier for the Zapier job execution.
MetadataObjectJSON object with document properties.
Metadata.TitleStringDocument title.
Metadata.AuthorStringDocument author.
Metadata.SubjectStringDocument subject.
Metadata.KeywordsStringDocument keywords.
Metadata.CreatedDateStringCreation date, in ISO 8601 format.
Metadata.ModifiedDateStringLast modification date.
Metadata.PageCountNumberTotal page count.
Metadata.WordCountNumberTotal word count.

Example JSON output:

{
"Job Id": "...",
"Metadata": {
"Title": "Q4 Financial Report",
"Author": "John Doe",
"Subject": "Financial Analysis",
"Keywords": "finance, Q4, report",
"CreatedDate": "2024-01-15T10:30:00Z",
"ModifiedDate": "2024-01-20T15:45:00Z",
"PageCount": 25,
"WordCount": 5280
}
}

Typical Setups​

Workflow ExamplesCommon Zapier workflow patterns using Extract Metadata.
Document catalog indexing
  1. A trigger fires when a new document is uploaded to a shared library.
  2. PDF4me Extract Metadata reads Title, Author, and Keywords from the file.
  3. The extracted fields are inserted into a catalog database or search index for later lookup.
Compliance audit trail
  1. A scheduled trigger lists controlled documents from a compliance folder.
  2. PDF4me Extract Metadata reads ModifiedDate and Author for each file in a loop.
  3. A filter flags any document whose ModifiedDate or Author falls outside policy for manual review.
CMS metadata population
  1. A document lands in a staging folder ahead of publication.
  2. PDF4me Extract Metadata reads Title, Author, and Keywords from the file.
  3. The fields are posted to a CMS API to pre-fill the content record before the editor reviews it.

Practical Tips​

File: (Exists but not shown) causes errors
Select the mapping option that provides the file's full binary content instead of a reference. See Zapier & Power Automate Tips for the exact steps.
Only File is required
File Name and Culture Name are both optional, there is no need to set them if the defaults are fine.
Empty properties return empty, not an error
A Word file with no Title or Author set simply returns an empty value for that field, the action does not fail.
This returns metadata, not the document
There is no File Url in the output. Use a different PDF4me Word action if the next step needs the actual document content.
Check for custom properties before assuming a field is missing
Fields added through Word's Advanced Properties dialog show up in the Metadata object too, review the full JSON output rather than only the standard fields.

Cheat Sheet​

FieldValue
ActionExtract Metadata
File[Mapped from previous step]
File Namedocument.docx
Culture Nameen-US (optional)
Core outputMetadata.Title, Metadata.Author, Metadata.CreatedDate, Metadata.WordCount, and more

Common Questions​

Does Extract Metadata return the document itself?+
No. It returns a Metadata object containing document properties such as Title, Author, CreatedDate, and WordCount, not the Word file. Use a different PDF4me action if the next step needs the actual document content.
What if a Word document has no title or author set?+
The corresponding Metadata field returns empty for any built-in property that was never filled in. See Microsoft's guide to viewing and changing Office file properties for where these values come from in the source document.
Can I extract custom document properties, not just the built-in ones?+
Yes. Any custom properties added to the Word file through its Advanced Properties dialog are included in the Metadata object alongside the standard fields like Title and Author.
Is Culture Name required to extract metadata?+
No. Culture Name is optional. It only affects how region-specific values in the metadata, such as date formatting, are interpreted, the extraction itself works without it.
How do I map nested metadata fields like Metadata.Title in later Zap steps?+
Use the + button in a later step and select the nested field directly, for example Metadata.Title or Metadata.ModifiedDate, from the Extract Metadata step's output. See this overview of document properties for what each standard field typically represents.

Same Task on Other Platforms​

Industry Use Cases & Applications​

  • Document Audit Trails: extract modification dates and authors for compliance audit evidence
  • Version Control Tracking: monitor document versions using creation and modification timestamps
  • Author Verification: validate document authors match authorized personnel lists
  • Retention Policy Enforcement: check creation dates against retention schedules for archival decisions
  • Controlled Document Management: track document properties for ISO or quality management compliance

Get Help​

Zapier IntegrationGet your API KeyZapier Documentation