Forward your email
Get a dedicated inbox address. CC it, auto-forward to it, or set up a rule — Gmail, Outlook, Exchange, any client. Attachments come along for the ride.
system readyemail in, structured data outEmail in.
Email in.
Clean data out.
Automatically.
Forward any email and datahone pulls the data inside — orders, leads, receipts, bookings, tickets — into clean, structured JSON. No rules to write, no templates to maintain. Delivered by webhook, the REST API, or a JSON, CSV, or XLSX download.
No card · 20 free pages / moForward from Gmail · Outlook · ExchangeAttachments parsed too
how it works
Three steps. No rules, no templates.
Point an inbox at datahone and it reads every message that arrives — body and attachments — the way a person would. You only ever touch three surfaces.
AI reads it like a person
List the fields you want, or let the AI infer the shape. It pulls them from the body and attachments — across senders and layouts. Low-confidence fields wait for review; the rest streams.
customerLena Voss
order#BW-10293
total_gbp128.50
confidence0.98
Send it where it belongs
Clean JSON streams to any webhook you run — in real time. Pull it from the REST API, download CSV or XLSX, or read it in the dashboard.
GETapi/v1/exports?format=csv202 queued
GETapi/v1/documents/:id/output200 ok
POST/datahone/webhook200 ok
what you can pull out of an inbox
One parser. Every kind of email.
Whatever lands in the inbox — a confirmation, an enquiry, a receipt, a signed contract — datahone turns it into structured records your tools can use.
Emails to spreadsheets
Every parsed email lands as a row, each field its own column. Download a clean CSV or XLSX export, or have each row POSTed to your webhook — no copy-paste, no fat-finger errors.
Emails to contact records
Turn enquiry, lead, and signup emails into contacts and deals — name, company, and intent already filled in. Delivered by webhook or the REST API, ready for the CRM you already run.
Structure your own search can index
Get inbox content and attachments back as clean, structured JSON your own assistants and search can index — so answers come from real data, not guesswork.
Attachments parsed too
PDFs, CSVs, XLSX workbooks, text files, and image scans attached to a message are read in the same pass as the body — nothing gets left in the attachment.
Tables & line items
Pull a variable number of order lines, bookings, or rows out of a single email into separate structured records — even when the count changes every time.
Normalised, every time
Dates, currencies, addresses, and names come back in one consistent shape — ready to drop straight into your tools, whatever format the sender used.
where teams point it first
An inbox is a data source. Use it like one.
The same parser, pointed at different inboxes, quietly feeds the systems that run sales, operations, and support.
Sales & RevOps
Lead emails become contact records.
Website enquiries, demo requests, and trial signups land in your pipeline with the name, company, and intent already filled in — so follow-up happens while the lead is still warm.
0 leads lost after hours
E-commerce & Ops
Orders and shipping become a live view.
Confirmations, dispatches, and delivery exceptions from every marketplace and carrier come back as one structured dataset your team can actually act on.
1 view, every channel
Support & Knowledge
Inbound mail becomes searchable knowledge.
Support requests come back with priority and category attached, and resolved threads and documents return as structured JSON your team and bots can index and search.
50+ languages read natively
questions
Email parsing, answered.
Q · 01
Order confirmations, lead and enquiry notifications, receipts and invoices, bookings, shipping updates, job applications, support requests — anything with data in the body or an attachment. You describe the fields you want, or let the AI infer them.
Q · 02
You get a dedicated inbox address. Forward manually, set up auto-forwarding, or CC it on the messages you want parsed. It works with Gmail, Outlook, Exchange, and any other client.
Q · 03
Yes. PDFs, CSVs, XLSX workbooks, text files, and image scans attached to an email are parsed in the same pass as the message body — you get one structured record back.
Q · 04
No. There's no rule editor and no per-sender template to maintain. The AI reads each email in context, so layout changes and new senders don't break your workflow.
Q · 05
Datahone POSTs each record to any webhook endpoint you run, serves it from the REST API, and offers JSON, CSV, or XLSX downloads. Read it in the dashboard too. Most teams wire up a destination in minutes.
Q · 06
Every field comes back with a confidence score. Low-confidence fields are flagged and held in a review queue for a human to confirm — the rest streams straight through, so nothing questionable reaches your systems unchecked.
Q · 07
Your messages and the data inside them are encrypted in transit and at rest, scoped to your account, and never used to train shared models. EU-hosted, with GDPR, UK-DPA, and CCPA alignment.
Q · 08
Per page, with a hard cap on every tier. An email body counts as one page; attachments are billed by their own format. When you hit your limit the next item is blocked — never silently billed. See pricing →
get started
Stop copying data out of emails.
Forward an email and watch datahone hand it back as clean data — by webhook, REST API, or CSV download. Free in minutes, no card required.
No rules or templatesBody and attachmentsRouted anywhere