Skip to main content

Parse Document in Zapier

What this action does

PDF4me Parse Document runs your saved parse template against a PDF inside a Zapier Zap and returns the extracted fields ready to map into the next step. Trigger from any of 6,000+ Zapier apps (Gmail, Dropbox, Slack, Google Drive, OneDrive, webhooks), reference the template by Template Name (TemplateId), and route the parsed values straight into Google Sheets, Airtable, HubSpot, Pipedrive, QuickBooks, or any downstream app.

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

Before you run this action: 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 Zapier action 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 action in Zapier requires a PDF4me account connection. Sign in once with your API key and reuse it across every PDF4me action in your Zap.

Important Facts You Should Not Miss

Template Name accepts the TemplateId GUID
Despite the field label, paste the GUID TemplateId from the dashboard. It is stable across renames and is the safe production value across Zap re-publishes.
Regex for stable patterns, JavaScript for conditional logic
Capture rules live in the template. Use Regex Expression for invoice numbers, dates, amounts. Use JavaScript Expression with the text variable for classification and fallback rules. Each capture key becomes an output field on the action.
Works with any Zapier file input
The File field accepts the binary PDF from any upstream Zapier step (Gmail New Attachment, Dropbox New File, Google Drive, Slack, webhook, Zapier Storage). Same TemplateId works from Make, n8n, Power Automate, and direct REST.
Parse Document action in Zapier

Parameters

ParameterRequiredWhat it doesExample
FileYesBinary PDF from any upstream Zapier step: Gmail New Attachment, Dropbox New File in Folder, Google Drive New File in Folder, OneDrive New File, Slack New File, webhook with file payload. Pick from the prior step output.Attachment from Gmail
Document NameYesSource filename including .pdf extension. Usually mapped from the same upstream step Filename output.invoice.pdf
Template NameYesTemplateId GUID from the PDF4me dashboard. Identifies which parse template (capture keys + extraction rules) the action should apply.12345678-1234-1234-1234-123456789abc

Expression types in your parse template

Regex ExpressionStable patterns
Invoice numbers (INV-\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 classifiers
The capture area text is passed as text; return a string. Multi-marker classification, fallback rules, date normalization. See Prepare Parse Info for Document for two working samples.

Output

The action returns the parsed field data as Zapier output values, with one field per capture key in your template. Pick them from the dynamic field picker in any downstream step.

Parse Document output in Zapier showing the parsed fields

Zap examples

Common Zapier patternsTypical ways to chain Parse Document into a Zap.
Gmail invoice to Google Sheets
  1. Gmail New Attachment triggers on a label such as Vendor Invoices.
  2. Filter passes only files ending in .pdf.
  3. Parse Document runs the Invoice template against the attachment.
  4. Google Sheets Create Spreadsheet Row writes invoiceNumber, totalAmount, invoiceDate into the AP tracker.
Dropbox receipt to Airtable
  1. Dropbox New File in Folder triggers on /receipts.
  2. Parse Document runs the Receipt template.
  3. Airtable Create Record writes vendor, date, total, items into the expense base.
  4. Slack Send Channel Message posts a summary to #finance.
Webhook contract to HubSpot
  1. Webhooks by Zapier Catch Hook receives an inbound contract PDF.
  2. Parse Document extracts the parties, contract value, start date, end date.
  3. HubSpot Create or Update Deal writes the contract data into the deal record.
  4. Outbound webhook notifies the deal owner.

Frequently Asked Questions

What goes in the Template Name field?+
Paste the TemplateId GUID from the PDF4me dashboard. Despite the field label, the GUID is the safer production value. It is stable across renames and identical to the value used by the REST API and the other platform connectors.
Where does the PDF file come from in a Zap?+
Any upstream Zapier step that exposes a file: Gmail New Attachment, Dropbox New File in Folder, Google Drive New File in Folder, OneDrive New File, Slack New File, Webhooks Catch Hook with file payload, Zapier Storage. Pick the file from the prior step output.
Do I have to build a template, or can the Zap parse any PDF?+
Template-based parsing is the supported production mode. Build the template once in the dashboard, then reference its TemplateId. The same TemplateId works in Make, n8n, Power Automate, and direct REST calls.
Can I extract data using JavaScript at parse time?+
Yes. Inside the template add a JavaScript Expression on a capture key. The capture area text is passed as the variable text and your function returns a string. The returned value appears in your Zap as a regular output field you can map into the next step.
How do I see the extracted fields in the field picker?+
Run the Test step at least once. Zapier reads the live response, learns the capture key names from your template, and surfaces them in the dynamic field picker of every downstream step.
What if my template changes (I add a new capture key)?+
Re-test the Parse Document action. Zapier re-reads the output and adds the new field to the picker. Then map it into downstream steps. The TemplateId stays the same so no other Zap step needs to change.

Same task on other platforms

Get Help