Turn the emails you receive into structured data
Give each sender its own address. Describe its emails once, and every order, booking, receipt or report arrives as JSON at your webhook, as rows in Google Sheets, or as a message in Slack or Discord.
Free: 50 emails a day and 20 parsed attachment pages a month. No credit card. Email needs an account, because anyone who knows a guest endpoint's link can read what it captured. Or browse the layout gallery.
- From
- Acme Store <orders@acme-store.example>
- Subject
- [Acme Store] Order #1042 placed by Jane Doe
Jane Doe placed order #1042 on Oct 29 at 10:14 am. Order summary Linen shirt × 2 $78.00 Canvas tote × 1 $24.00 Subtotal $102.00 Shipping $6.00 Total $108.00 USD Shipping address Jane Doe 1 Main Street Springfield
{
"parsed": {
"status": "matched",
"layout": {
"id": "shopify-orders",
"name": "Shopify orders"
},
"fields": {
"order": "1042",
"customer": "Jane Doe",
"subtotal": "102.00",
"shipping": "6.00",
"total": "108.00",
"currency": "USD"
},
"lineItems": [
{
"product": "Linen shirt",
"quantity": "2",
"price": "78.00"
},
{
"product": "Canvas tote",
"quantity": "1",
"price": "24.00"
}
]
}
}How it works
Step 1
An address for every sender
Each endpoint gets an address like acme-orders@mailhooks.cc. Forward a mailbox to it with a rule in Gmail or Outlook, or give it to the sender. A +tag after the name tells sources apart.
Step 2
Describe the email once
A layout picks out the values you need, turns order lines into line items and parses CSV, Excel and PDF attachments. Try it on a real email as you type, before it touches anything.
Step 3
Deliver it where it is needed
Signed JSON to your webhook, a row per order or per line in Google Sheets, a message in Slack or Discord. Failed deliveries are retried, and you can replay any email.
Ready-made layouts
Start from a sender you already get email from, then adjust it to your own emails in the preview.
Shopify
order notifications
WooCommerce
new-order emails
Etsy
sale notifications
Amazon Seller Central
sold, ship now emails
eBay
item sold emails
Stripe
payment receipts
PayPal
payment received emails
Booking.com
new booking emails
Built for mail that matters
Line items
An order with three products becomes three rows, from the email's text or from an attached sheet.
Attachments
CSV, TSV, Excel, OpenDocument and PDF text parsed in a sandbox; files also go along as signed links or inline.
Alerts
An email when a field stops matching, when no layout fits, when mail stops arriving, or when a destination keeps failing.
Replay
Fix a pattern, then read earlier emails again and send them to their destinations once more.
Retention you choose
Kept 7, 31 or 90 days by plan, stored in the EU, or deleted as soon as every destination has its copy.
API, SDKs and MCP
The same parsed JSON from the REST API, the TypeScript, Python and Go SDKs, the CLI and the MCP server for AI agents.
More features
Google Sheets
A row per email or per line item, in a spreadsheet you pick.
File drops
CSV, XML or JSON files on your SFTP, FTP or S3 server.
Your own domain
Mail to orders@inbound.acme.com, sent to the endpoints you choose.
AI setup
Patterns for fields and layouts, drafted from emails you pick.
Zapier and Make
Start a Zap or a Make scenario with each parsed email.
Pricing
Free
$0
- 50 emails or webhooks a day
- 20 parsed pages a month
- 5 AI assists every 30 days
Pro
$8 a month
- 100,000 emails or webhooks a month
- 100 parsed pages a month
- 20 AI assists every 30 days
Business
$29 a month
- 250,000 emails or webhooks a month
- 2,000 parsed pages a month, 50 layouts
- Your own domain and file drops
Questions
The mail-first side of webhooks.cc. It is the same account, the same endpoints and the same plans, for people who receive their data by email. Sign in on either site and you see the same endpoints.
A guest endpoint on webhooks.cc is readable by anyone who knows its link, and mail often holds codes, receipts and personal details, so email addresses only exist for endpoints that belong to an account. Signing up is free and takes an email address.
No. Forward the emails you want read to your endpoint's address with a forwarding rule in Gmail, Outlook or your mail server, or give the address straight to the sender.
CSV, TSV, Excel (XLSX and XLS), OpenDocument spreadsheets, the text of PDFs (no OCR) and plain text files. Each started 1,000 rows of a sheet, each PDF page and each text file is one parsed page: Free includes 20 a month, Pro 100 and Business 2,000.
It is still captured and delivered, marked with no matching layout, and an alert can tell you. Add or fix a layout and replay the emails it missed.
Emails and their attachments are stored in the EU and deleted after your plan's retention: 7 days on Free, 31 on Pro, 90 on Business. Any endpoint can keep them for less, or delete each email once every destination has its copy.
Yes: the REST API, SDKs for TypeScript, Python and Go, a CLI that forwards emails to localhost, and an MCP server so AI agents can read and wait for emails. The parsed result is part of every email's JSON.
Start with one sender
Free: 50 emails a day and 20 parsed attachment pages a month. No credit card.