Give each source its own inbox.
Create several addresses in one project for teams, suppliers, or document types. Each inbox keeps its own sender controls and pause state.
Email PDF parser
Email PDFs in. Structured records out.
Give every team or document source its own project inbox. PdfParse receives attached PDFs, routes them through your project, and puts the extracted records in your tables.
The actual inbox workspace
Several inboxes. One project.
Current product interface · synthetic project data
From attachment to database
A direct path from email to project records.
Route every attached PDF.
Send a trusted source directly to one destination table or use the project's classifiers when an inbox receives mixed document types.
Process it through the existing workflow.
Accepted attachments become project documents and continue through routing, extraction, and human review when a result needs attention.
Use the resulting data.
Review source-linked fields and line items in your tables, then query them or export CSV, JSON, and SQLite for downstream work.
Guides and product news
Set up the workflow, then automate the documents you receive most.
Product announcement
Introducing Email Inboxes: PDF Attachments to Project Tables
See what project inboxes add, when to create more than one, and how to verify your first attachment.
Read article ↗Invoice automation guideHow to Extract Invoice Data from Email Attachments
Create an accounts-payable inbox and verify one invoice record with its related line items.
Read article ↗Purchase-order automation guideHow to Automate Purchase-Order Email Processing
Route emailed purchase orders into a project and check the resulting order and item rows.
Read article ↗Before you forward your first PDF
- Can one project have more than one inbox?
- Yes. A project can have several inboxes. Use distinct addresses for sources or teams that belong in the same project; each inbox has its own sender controls and pause setting.
- Does this connect to Gmail or Outlook?
- You send or forward messages to a PdfParse inbox address. This is attachment intake, with no mailbox sign-in or historical mailbox sync. Your email provider manages any forwarding rule you choose to create.
- Can it extract an email body or a download link?
- This workflow processes attached PDF files. Include the PDF itself in the message. Email body text, shared-drive links, and supplier-portal links are not converted into documents by the inbox.
- Does an accepted email mean extraction is complete?
- No. Receipt, attachment intake, document routing, and extraction are separate stages. Inspect attachment status and the resulting document or job, then review the extracted rows before using them.
- What can I do with the extracted data?
- Use the same project tables as other PdfParse documents. Export reviewed records as CSV or JSON, download SQLite, or work with existing API and webhook integrations. Keep parent and child identifiers when exporting related tables.
One address away from structured data.
Create your project inboxes, send one representative PDF, and verify the resulting records before you automate forwarding.