Your schema
Choose the fields and types your application expects.
Maail Extract · AutomationPlanned
Turn email content into fields your software can use.
Define the data you need from invoices, orders or appointments. Keep source evidence alongside the result.
What you can build
Email Data Extraction API for Invoices & Orders
Move information out of inboxes. Explore the planned capabilities below.
Business documents
Plan extraction for invoice, order, appointment and contact details.
Source evidence
Inspect the text or document location supporting a field.
Missing values
Keep absent or uncertain fields null instead of inventing content.
Attachment handling
Scope PDF, CSV and table parsing with explicit file and size limits.
Workflow delivery
Connect incoming mail, extraction and a signed result event.
Three steps
A workflow your team can follow.
- Define your JSON schema
- Extract supported fields
- Review before taking action
In practice
An invoice becomes a review task
Extract a candidate invoice number, amount and due date. Compare the source evidence, validate supplier details and approve the record before posting it.
Plan invoice intakeWhat is included in the wider product direction?
Optional OCR and expanded PDF, CSV and XLSX workflows follow supported file types and processing limits.
Does the extraction API handle scanned documents?
OCR is part of the expansion scope, not an assumption for every attachment. Confirm supported document types, size limits and OCR needs when scoping an integration.
Can I integrate this product today?
This product scope is planned. Discuss your requirements with us to confirm available components, processing terms and integration timing. The public DNS tools can be used without an account.
Start with the task you want to simplify.
Tell us which messages, systems and decisions need to connect.