Parse a Document in Make
PDF4me Parse a Document runs your saved parse template against a PDF inside a Make scenario and returns the extracted fields ready to map into the next module. Pipe File Content from Dropbox, Google Drive, OneDrive, or HTTP, reference the template by Template Name (TemplateId), and route the parsed values straight into Airtable, Google Sheets, a database, or a downstream email. The template carries the extraction logic, so one module call covers invoices, contracts, receipts, and any custom layout you have configured.
Before you run this module: create a parse template in the PDF4me dashboard. Define your capture keys and pick Regex Expression for stable patterns or JavaScript Expression for conditional logic. The Make module references that template by TemplateId. See Prepare Parse Info for Document for full setup, Regex examples (INV-\d{6,10}, \d{2}/\d{2}/\d{4}), and two working JavaScript Expression classifier samples.
Authenticating Your API Request
The PDF4me module in Make requires a valid Connection. Create or select one that holds your PDF4me API key so the scenario can authenticate parse requests securely.
Important Facts You Should Not Miss
text variable for classification and fallback rules.
Parameters
| Parameter | Required | What it does | Example |
|---|---|---|---|
| Connection | Yes | PDF4me connection that authenticates the module. Click Add to create one with your API key, or pick an existing connection from the dropdown. | PDF4me production |
| File Content | Yes | Binary PDF mapped from a previous module: Dropbox Download a File, Google Drive Get a File, OneDrive Download a File, HTTP Get a File, Gmail Get an Attachment, or any module that returns a file. | 1. Data |
| File Name | Yes | Source filename including .pdf extension. Usually mapped from the same upstream module File Name output. | 1. File Name |
| Template Name | Yes | TemplateId GUID from the PDF4me dashboard. Identifies which parse template (capture keys + extraction rules) the module should apply. | 12345678-1234-1234-1234-123456789abc |
Expression types in your parse template
Regex ExpressionStable patternsINV-\d{6,10}), dates (\d{2}/\d{2}/\d{4}), amounts ($?\d{1,3}(?:,\d{3})*(?:.\d{2})?). Around 80% of production capture keys.JavaScript ExpressionConditional logic and classifierstext; return a string. Multi-marker classification, fallback rules, date normalization. See Prepare Parse Info for Document for two working samples.Output
The module returns one Bundle per execution with the trace identifier plus the parsed key/value data ready to map into the next module.
| Field | What it contains |
|---|---|
Trace-Id | Unique identifier for the parse operation. Useful for audit logs and error troubleshooting. |
Parsed fields | One field per capture key defined in the template (for example invoiceNumber, totalAmount, invoiceDate). Pick them directly in the visual mapper of any downstream module. |
Scenario examples
Common Make scenario patternsTypical ways to chain Parse a Document into a Make flow.
- Gmail Watch Emails fires on new vendor invoices.
- Iterator loops over each PDF attachment.
- Parse a Document runs the Invoice template against the binary attachment.
- Airtable Create a Record writes invoiceNumber, totalAmount, invoiceDate into the AP table.
- Dropbox Watch Files fires on new uploads in /receipts.
- Dropbox Download a File loads each PDF binary.
- Parse a Document extracts vendor, date, items, total using the Receipt template.
- Google Sheets Add a Row appends the parsed values to the expense tracker.
- HTTP Webhook receives an inbound PDF.
- Parse a Document runs a template with a JavaScript Expression key returning the document type.
- Router branches on the type field (invoice / order / receipt) to a type-specific downstream branch.
- Each branch posts the parsed values to its destination system.