Extract Attachment From PDF in Make

Extract Attachment From PDF is a Make module that retrieves all files embedded inside a PDF document automatically within a scenario. It handles PDF portfolios, standard PDF attachments, and PDF/A-3 source files, returning each extracted file as a Base64-encoded item in an Attachments array ready for an Iterator to process individually.

What this module does

PDF4me Extract Attachment From PDF retrieves all embedded files from a PDF document or PDF portfolio inside a Make scenario. Supply the PDF as a binary buffer and the module returns an Attachments array where each item carries the File Name and File Data (Base64). Chain a Make Iterator to process each file individually: upload to cloud storage, email to recipients, import data files into a database, or pass to another module.

Use an Iterator to process each attachment separately

The module returns all attachments as an array in a single output bundle. Add a Make Iterator module immediately after to split the array into individual bundles, one per attachment. Each bundle contains File Name and File Data (Base64) so you can route files to different destinations based on type or name.

File Data is Base64-encoded

Each extracted attachment is returned as a Base64 string in the File Data field. Most Make storage integrations (Google Drive, Dropbox, OneDrive) accept Base64 directly. If a downstream module requires binary input, convert using the Make toBinary(File Data, 'base64') function before mapping.

Works with PDF portfolios and PDF/A-3 archives

Beyond standard PDF attachments, this module handles PDF portfolios (multi-file containers) and PDF/A-3 archive documents with embedded source files. For PDF/A-3, the source files (Word, Excel, XML) are extracted while the archive PDF remains intact in compliance storage, per the PDF/A-3 specification.

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 Make, every request must include proper authentication credentials. Authentication ensures secure communication between your Make scenarios and PDF4me's attachment extraction services.

Get your API Key

Map File Name and Document from the prior download step, then chain a Make Iterator to process each extracted attachment.

How to Set Up Extract Attachment From PDF in Make

1. Add PDF4me > Extract Attachment From PDF to your scenario.
2. Select your Connection or click Add to create one with your API key.
3. Map File Name (with .pdf extension) from the prior module or enter a static name.
4. Map Document (binary PDF buffer) from a Google Drive, Dropbox, email, or HTTP download step.
5. Add a Make Iterator after this module and map it to the Attachments array output.
6. Connect downstream modules to the Iterator output: upload to cloud storage, email, import data, or route by file type.

Parameters

Parameter	Required	What it does	Example
File Name	Required	Filename of the source PDF including the .pdf extension. Map from the previous module's file name output or enter a static name.	portfolio.pdf
Document	Required	Binary PDF file content. Map from a Google Drive, Dropbox, email, or HTTP download step. The PDF must contain embedded attachments for the module to return results.	[PDF Buffer]

Output

Field	Type	What it contains
Attachments	Array	Collection of all extracted attachment objects. Feed into a Make Iterator to process each file individually.
File Name	String	Filename of the individual attachment including its extension (e.g. source_data.xlsx).
File Data	Base64	Content of the individual attachment encoded as Base64. Map to a storage upload module or decode with toBinary() for modules that require binary input.

What File Types Can You Extract From a PDF?

Any file type embedded as an attachment is supported: spreadsheets (XLSX, CSV), Word documents (DOCX), images (PNG, JPG), ZIPs, or other PDFs. This includes files in PDF portfolios (Adobe's multi-file container format) and source files embedded in PDF/A-3 archives per the ISO 19005-3 standard. The module preserves original file formats and extensions in the returned File Name field.

Workflow Examples

Compliance Extraction

Extract and organize evidence files from compliance submission PDFs

1. Trigger: Compliance submission PDF received (email attachment or Watch Folder)
2. Download PDF: Retrieve the compliance package
3. Extract Attachments: Retrieve all embedded evidence files
4. Iterator: Process each extracted attachment individually
5. Classify by extension: Route to appropriate compliance folder (spreadsheets, images, docs)
6. Upload: Save each file to the correct folder in SharePoint or Google Drive
7. Log: Record all extracted files in a compliance database
8. Notify team: Alert compliance team of processed submission

Create Scenario

PDF/A Source Recovery

Retrieve editable source files from PDF/A-3 archive documents

1. Trigger: PDF/A-3 archive document needs its embedded source file
2. Download Archive PDF: Retrieve the PDF/A-3 document from compliance storage
3. Extract Attachments: Retrieve the embedded Excel or Word source file
4. Validate: Confirm extracted file is complete
5. Upload Source File: Save to an editable files folder
6. Notify requester: Send extracted source file link

Create Scenario

Portfolio Distribution

Unpack PDF portfolios and distribute files to the right teams

1. Trigger: PDF portfolio received from client
2. Download Portfolio: Retrieve the portfolio PDF
3. Extract All Attachments: Retrieve all embedded files
4. Iterator: Process each extracted file
5. Route by file type: Send each file to the appropriate team folder
6. Email individually: Deliver each file to the designated recipient
7. Confirm: Notify sender that portfolio was processed and distributed

Create Scenario

Frequently Asked Questions

What types of files can this module extract from a PDF?+

The module extracts any file type embedded as an attachment: spreadsheets, Word documents, images, CSVs, ZIPs, or other PDFs. This includes files in PDF portfolios and source files embedded in PDF/A-3 archive documents. Original file formats and extensions are preserved in the returned File Name field.

How do I process multiple attachments returned by the module?+

The module returns an Attachments array. Use a Make Iterator immediately after to split the array into individual bundles, one per attachment. Each bundle contains File Name and File Data (Base64). You can then upload each file to Google Drive, Dropbox, or SharePoint, or apply routing logic based on the file extension.

What is the File Data format and how do I use it?+

File Data is returned as a Base64-encoded string. Most Make storage modules (Google Drive, Dropbox, OneDrive) accept Base64 data directly in their upload fields. If a module requires binary input, use the Make function toBinary(File Data, "base64") to convert before mapping. No separate decoding step is needed for standard storage integrations.

Does this module work with PDF/A-3 source file extraction?+

Yes. PDF/A-3 is the only PDF/A variant that permits embedded file attachments. If your archive workflow produces PDF/A-3 documents with embedded source files such as Word, Excel, or XML, this module retrieves them for editing or reprocessing while the PDF/A-3 archive document remains intact in your compliance storage.

Get Help

Make IntegrationGet your API KeyMake Documentation