Extract Text from Word in Make: Clean Text Retrieval with PDF4me

PDF4me Extract Text from Word is a Make module that pulls the text content out of a Word document, with page range control and options to strip comments, headers, footers, and finalize tracked changes first. Use it to feed clean text into search indexes, translation services, or text-mining pipelines without opening Word.

What this module does

PDF4me Extract Text from Word returns the text content of a .docx file as a single Extracted Text field, optionally limited to a page range and cleaned up by removing comments, headers/footers, or accepting tracked changes first. One action replaces manually opening the document to copy its text.

How Do I Authenticate My Make Scenario?

Every PDF4me module in Make requires a valid Connection. Create or select one that holds your PDF4me API key so the scenario can authenticate text-extraction requests securely.

Get your API Key

Important Facts You Should Not Miss

Accept Changes runs before extraction, not after

Setting Accept Changes finalizes every tracked change in the document first, so the extracted text reflects the edited version. Leave it off if you need the text with revision marks still logically present in the source.

Page range is optional, not required

Start Page Number and End Page Number narrow extraction to a subset of pages. Leave both blank to extract the full document in one call.

The document buffer field is labeled Json File

Despite the name, Json File holds the mapped binary content of the Word document, not JSON text. Map it exactly like a file buffer in any other PDF4me module.

Make PDF4me Extract Text from Word module configured with Connection, File set to Map with Word File Name and Json File mapped, Start Page Number 1, End Page Number 10, and Remove Comments, Remove Header Footer, and Accept Changes toggles — Set File to Map, wire Word File Name and Json File from the prior module, then set an optional page range and the cleanup toggles.

Parameters

Required: Connection and File must always be provided. Word File Name and Json File are required when File is Map. Page range and cleanup toggles are optional.

Parameter	Required	What it does	Example
Connection	Required	PDF4me API connection. Click Add and paste your API key if connecting for the first time.	`TestUser01`
File	Required	Radio button picking how the source Word document arrives. Pick a quick storage option (Dropbox - Download a File) or choose Map to bind Word File Name and Json File from any prior module.	`Map`
Word File Name	Conditional	Sub-field of File, shown when Map is selected. Filename of the source document including its .docx extension.	`annual_report.docx`
Json File	Conditional	Sub-field of File, shown when Map is selected. Binary content of the Word document, mapped from the prior module Data output despite the Json label.	`[Word Buffer]`
Start Page Number	Optional	1-based page number where extraction begins. Leave blank to start from the first page.	`1`
End Page Number	Optional	1-based page number where extraction ends. Leave blank to extract through the last page.	`10`
Remove Comments	Optional	Strips reviewer comments from the extracted text when enabled.	`Yes`
Remove Header Footer	Optional	Excludes running headers and footers from the extracted text when enabled, leaving only body content.	`Yes`
Accept Changes	Optional	Finalizes all tracked changes before extraction when enabled, so the text reflects the edited version.	`Yes`

Output Fields

Field	Type	What it contains
`Extracted Text`	String	Complete text content from the Word document, filtered by the page range and cleanup options selected.

How Do I Set Up Extract Text from Word in Make?

Add PDF4me → Extract Text from Word to your Make scenario.
Select Connection (or click Add to create one with your PDF4me API key).
Under File, choose Map and wire Word File Name and Json File from a previous module (Dropbox, Google Drive, or email attachment).
Optionally set Start Page Number and End Page Number to limit extraction to a page range.
Toggle Remove Comments, Remove Header Footer, and Accept Changes as needed. Run the scenario, the extracted text returns as Extracted Text.

Typical Setups

Workflow ExamplesCommon Make scenario patterns using Extract Text from Word.

Contract clause search index

A trigger fires when a signed contract lands in the repository.
Get File downloads the executed Word contract.
Extract Text from Word runs with Accept Changes and Remove Comments enabled for a clean final version.
The extracted text is written to a searchable database or full-text index.
Downstream regex or NLP steps pull out key terms, dates, and parties.

Translation preparation

A document is marked for translation in a project tracker.
Get File retrieves the source Word file.
Extract Text from Word runs with Remove Header Footer enabled to isolate body content.
The clean text is sent to a translation API.
The translated text is rebuilt into a new document and archived alongside the source.

Legacy content migration

A legacy Word document is pulled from an archive folder for migration.
Extract Text from Word retrieves the full text content in one call.
The scenario parses headings and paragraphs from the returned text.
A CMS Create Entry step imports the content into the new platform.
The original document is tagged as migrated in the archive.

Practical Tips

Enable Accept Changes for a final-version extract

If the source document still has open tracked changes, leaving Accept Changes off can pull ambiguous or duplicated text. Turn it on whenever you want the clean, finalized wording.

Use the page range for large documents

Setting Start Page Number and End Page Number avoids pulling an entire multi-hundred-page manual when you only need a specific section.

Remove Header Footer before search indexing

Repeated headers and footers pollute keyword frequency in search indexes and NLP pipelines. Strip them for cleaner downstream analysis.

Map Json File like any other buffer

The label is misleading, it is not a JSON string. Map the binary Data output from the prior module the same way you would for any PDF4me file input.

Pair with Parse JSON only after your own restructuring

Extracted Text is plain text, not structured JSON. If you need individual fields, run your own regex or AI parsing step against Extracted Text first.

Cheat Sheet

Field	Value
Module	`Extract Text from Word`
Connection	`PDF4me API key`
Document source	`File = Map (Word File Name + Json File)`
Page range	`Start Page Number / End Page Number (optional)`
Cleanup toggles	`Remove Comments / Remove Header Footer / Accept Changes`
Output	`Extracted Text (String)`

Common Questions

How do I extract text from a Word document in Make?+

Add the PDF4me Extract Text from Word module, connect your API key, set File to Map and supply Word File Name and Json File from a prior module, then run the scenario. The module returns the document text as a single Extracted Text field.

Can I extract text from only part of the document?+

Yes. Set Start Page Number and End Page Number to a 1-based page range. Leave both blank to extract the entire document.

What do Remove Comments, Remove Header Footer, and Accept Changes do?+

Remove Comments strips reviewer comments from the extracted text. Remove Header Footer excludes running headers and footers so only body content comes through. Accept Changes finalizes tracked changes before extraction, so the text reflects the edited version rather than the original with revision marks.

Why is the document content field called Json File?+

Json File is the exact label PDF4me's Make module uses for the mapped binary content of the Word document, even though the value itself is a document buffer rather than JSON text. Map it the same way you would map a file buffer in any other PDF4me module.

What text mining and NLP tasks pair well with this module?+

The extracted text feeds directly into sentiment analysis, keyword extraction, translation services, or full-text search indexing. See <a href="https://learn.microsoft.com/en-us/office/open-xml/word/structure-of-a-wordprocessingml-document" target="_blank" rel="noopener noreferrer">Microsoft's WordprocessingML document structure reference</a> for how text content is organized inside a .docx file.