Automated Document Intake

Capture every document, however it arrives

Documents arrive from any channel, in any common format, and land in a mailbox shaped around your workflow.

Sign up for free Book a demo

What's included

PDFs, emails, scans, and 25+ more formats

Parse documents, spreadsheets, presentations, emails, scans, and zip archives all into the same mailbox. A single workflow handles a mix of formats end to end.

  • PDFs, Word, Excel, PowerPoint, OpenOffice, and plain text
  • Emails with their attachments, web files, and calendars
  • Images, photos, scans, and zip archives

Unlimited mailboxes

A mailbox is one self-contained workflow with its own extraction schema, email address, and intake rules. Run as many in parallel as you need at no extra cost.

  • Each mailbox extracts its own customizable schema of fields
  • Unique @in.parseur.com address per mailbox (forward, CC, or BCC)
  • Per-mailbox access control for team members (Pro plan and above)

API and direct uploads

REST API for programmatic uploads with custom metadata, web uploader for ad-hoc drag-and-drop. Both feed straight into the same mailbox processing queue.

  • Drag-and-drop web upload for one-off files
  • Full REST API access on every plan, free tier included
  • Webhooks notify your system when each document finishes processing

Sync via automation platforms

Zapier, Make, and Power Automate connect to Drive, Dropbox, OneDrive, SharePoint, and 10,000+ other apps. Any tool your team already uses can trigger intake.

  • Native connectors for Zapier, Make, and Power Automate
  • Cloud storage triggers from Drive, Dropbox, and OneDrive
  • No code needed to wire up a new source

Per-mailbox intake rules

Each mailbox enforces its own intake policy: which senders can submit, which file formats are accepted, and whether email bodies, attachments, or both are parsed.

  • Whitelist or blacklist sender email addresses
  • Toggle which file formats each mailbox accepts
  • Parse the email body, attachments, or both

Document splitting

A single PDF can be split into multiple records before parsing. Each split runs through extraction as its own document, mapped to the same mailbox schema.

  • Split by single page or by fixed page ranges
  • Split when a keyword or marker text is found
  • Split with AI when document boundaries are unpredictable

How Document Intake works

1

Send

Documents arrive through whichever channel fits the workflow: a forwarded email, an API call, a manual upload, or a trigger from a connected app.

Email
API
Upload
Zapier
Parseur Parseur
2

Receive

Each file is routed to a mailbox based on the inbound address, API call, or upload context. Email bodies and attachments are split into separate records, and the format is detected automatically.

receipts
invoices
contracts
3

Filter

Each mailbox applies its own intake rules. Only documents from allowed senders, in allowed formats, and in the right channel get through.

[email protected]
[email protected]
[email protected]
PDF
JPG
XLSX
ZIP
4

Split

This step is optional. When enabled, multi-document PDFs are chunked into separate records, with boundaries set by page count, page ranges, keyword markers, or AI.

bundled-docs.pdf
doc-1.pdf
doc-2.pdf
doc-3.pdf

What happens next

Multi-Engine Document Parsing

Vision AI, Text AI, templates, or OCR pull structured fields from each document.

Learn more
Back to all features
Get started

Parse documents on autopilot.

Forward an email, hit the API, or drop a file in. The rest is automatic.

Free plan included, no credit card needed
Process your first document in under 2 minutes
Cancel anytime, no commitment
Sign up for free Book a demo

Frequently Asked Questions

Common questions about getting documents into Parseur, from email forwarding and API uploads to filtering, splitting, and supported file formats.

Documents can arrive through four channels: forward an email to a unique mailbox address ending in @in.parseur.com, drag-and-drop files in the web app, push them in via the REST API, or trigger uploads from connected apps like Drive, Dropbox, OneDrive, or SharePoint via Zapier, Make, or Power Automate.

Parseur supports 25+ formats across documents (PDF, Word .doc/.docx, Rich Text .rtf, OpenDocument Text .odt, HTML/.htm/.xhtml, Plain Text, XML/.hl7), presentations (PowerPoint .ppt/.pps/.pptx, OpenDocument Presentation .odp), spreadsheets (Excel .xls/.xlsx/.xlsm, OpenDocument Spreadsheet .ods, CSV), images (JPEG, PNG, GIF, Bitmap, TIFF), email and calendar files (.eml, Outlook .msg, Mbox archives, iCalendar .ics), and zip archives that are unpacked automatically. A single mailbox can mix formats end to end.

Yes. The REST API is available on every plan, including the free tier. You can upload files programmatically with custom metadata, and Parseur fires a webhook back to your system once each document finishes processing.

Yes. Document splitting can be configured per mailbox. Split by single page, by fixed page ranges, by a keyword or marker found in the text, or with AI when boundaries are unpredictable. Each split is then parsed as its own record.

Yes. Each mailbox enforces its own intake policy. You can whitelist or blacklist sender email addresses, toggle which file formats are accepted, and choose whether email bodies, attachments, or both are parsed.

Yes. Each mailbox has its own unique @in.parseur.com address. Forward, CC, or BCC emails to that address and Parseur picks them up automatically. You can choose to parse the email body, attachments, or both.

Forward an email to your mailbox address and Parseur splits the email body and attachments into separate records automatically. Each record runs through extraction independently, and you can choose to parse the body, the attachments, or both per mailbox.

Use Zapier, Make, or Power Automate. Each platform has a native Parseur connector and triggers for Drive, Dropbox, OneDrive, SharePoint, and 10,000+ other apps. No custom code is needed to wire up a new source.

Unlimited. A mailbox is one self-contained workflow with its own extraction schema, email address, and intake rules. You can run as many in parallel as you need at no extra cost.

No. The same mailbox handles forwarded emails, email attachments, direct PDF uploads, scans, and API submissions through one workflow, mapped to one schema.