Postmark Inbound Alternative That Extracts Named Fields from Email
Get the order number, total and customer as fields, not a TextBody string you slice in your own code
Postmark Inbound is a clean way to receive mail in an application. What it hands you is the message: From, Subject, TextBody, HtmlBody, Headers and Attachments. MailParse does the step after that. Name the fields you need, such as order_number, invoice_total or customer_email, and get them back as signed JSON on your webhook, through the API, or as a CSV or Excel export.
Connect a Gmail or IMAP mailbox to parse new mail automatically, or paste an email below to test the converter now.
Create a free account to download. No credit card required.
Postmark Inbound receives email and posts it to your webhook as JSON with From, Subject, TextBody, HtmlBody, headers and base64 attachments. It does not pull business values such as an order number or invoice total out of the body, so that code stays yours. MailParse is the Postmark Inbound alternative for teams that want those values back as named fields in JSON, CSV or Excel.
- Named fields
- order_number, total, customer
- 3 inputs
- Forwarding, IMAP mailbox, API
- JSON / CSV / Excel
- Same record, three outputs
- 3 free parses
- Test on your own emails first
Postmark Inbound does one job well. You point a domain MX record at Postmark or use the inbound address Postmark generates for your server, and every message that arrives is posted to your URL as JSON. The payload is tidy: sender and recipients split into objects, Subject, Date, MessageID, TextBody and HtmlBody, a Headers array that includes the spam score and SPF result, and an Attachments array with each file base64 encoded. There is also StrippedTextReply, which removes the quoted history from a plain text English reply. Postmark lists inbound processing on its Pro and Platform plans, not on Free or Basic, according to the Postmark pricing page.
The gap shows up the day after you wire it in. A supplier confirmation lands in TextBody as one long string, and somebody has to find "PO 44817", "Total due 2,315.40" and the ship date inside it. That somebody is your code, and it keeps changing every time a sender rewrites a template. The Postmark inbound parsing guide describes the message fields only; it does not offer extraction of order numbers, totals or any other value you define.
MailParse is built for that second step. You name each field once, either by the label printed in the email (Order number, Total due, Ship date) or with a regular expression in slashes such as /PO \d+/, and each message comes back as one record with those values filled in. Mail reaches MailParse through your personal forwarding address, a Gmail or IMAP mailbox you connect, or a raw message you POST to the email parser API. The record then goes out as signed JSON to your endpoint (the email to webhook page shows the payload), or into a spreadsheet for the people who never touch the code. If you are weighing other receiving services too, the same comparison runs for the SendGrid Inbound Parse alternative and the CloudMailin alternative.
What the converter does
Everything you need to turn the email your team receives into a spreadsheet it can actually use.
Values you name come back as fields
Postmark gives you TextBody and HtmlBody. MailParse gives you order_number, invoice_total and ship_date as separate keys, matched by the label in the email or by a /regex/ you supply, so your handler stores values instead of searching strings.
Three ways in, none needs DNS
Forward mail to your personal MailParse address, connect a Gmail or IMAP mailbox, or POST a raw message to the API. You can keep Postmark as the receiver and forward the messages you want parsed, or skip the MX change entirely.
Text from PDF and CSV attachments
Postmark passes attachments through as base64 for your code to decode. On the Plus plan and higher MailParse reads the text inside digital PDF and CSV attachments, so a total that only exists in an attached invoice is still found. Scanned images need OCR first.
Signed JSON on your endpoint
Each parsed record is posted to your URL with a MailParse-Signature header, an HMAC-SHA256 of the timestamp and body, so your endpoint can reject anything it did not expect.
A spreadsheet for the ops team
The same records export to Excel or CSV from the browser. Finance or order desk staff can pull last week of supplier confirmations without asking a developer to query the database.
Backlogs as well as live mail
Upload saved .eml or .msg files, a .zip of a folder or an MBOX export and parse months of history with the same field setup, which a live webhook alone cannot do.
How to move parsing off your Postmark webhook
Keep the receiving you already have, or replace it. Either way the extraction code goes away.
Pick the way mail arrives
Forward the relevant messages from your inbox or Postmark stream to your MailParse forwarding address, connect the mailbox over IMAP, or POST raw messages to the API from your existing handler.
Name the fields
Add fields such as order_number, invoice_total and customer_email. Use the label the email prints, or a /regex/ in slashes for codes like /INV-\d+/.
Check a real message
Run a few real emails and look at the record. If a sender prints "Amount due" instead of "Total", add that label rather than rewriting a parser.
Send the record on
Add your webhook URL to receive signed JSON per message, fetch records through the API, or export Excel and CSV for the team.
Who switches from raw inbound JSON to parsed fields
Teams that already receive mail fine and are tired of maintaining the code that reads it.
SaaS teams with an email intake feature
Customers forward receipts, orders or requests into your product. Let MailParse return the fields and keep your own code focused on what to do with them.
Order desks and distributors
Purchase orders and supplier confirmations from dozens of senders, each worded differently. Labels cover the variation without a parser per sender.
Finance and AP
Invoice numbers, due dates and totals from the email body or a digital PDF attachment on Plus, exported to Excel or posted to the system that books them.
Small teams without a backend developer
No public endpoint to run at all. Connect the mailbox, name the fields, and download the spreadsheet, or post to a no-code tool by webhook.
MailParse vs Postmark Inbound in short
What you receive
Postmark posts the whole message as JSON. MailParse posts a record with the values you named, plus the sender, subject and date.
Who writes the extraction
With Postmark you do. With MailParse you list labels or regular expressions in a form.
Failed deliveries
Postmark retries a failed webhook 10 times over up to 6 hours. MailParse records the failure and status code with no automatic retry, and the record stays available through the API and export.
Sending email
Postmark is also a transactional sending service. MailParse does not send your email at all, it only reads it.
MailParse vs Postmark Inbound side by side
Postmark is excellent infrastructure, and if you only need raw mail inside your app it is the cheaper choice. The table shows where each one wins. For the wider field of parsers see the best email parser guide.
| What matters | MailParse | Postmark Inbound |
|---|---|---|
| Main job | Extract the values you name from each email | Receive email and post the full message to your URL |
| Business fields | Order number, total, dates and so on, by label or /regex/ | None; TextBody and HtmlBody for your code to read |
| Attachments | Text of digital PDF and CSV files read on Plus and higher | Base64 files, up to 35 MB in total per message |
| How mail gets in | Forwarding address, IMAP mailbox, API POST, file upload | MX record on your domain or a generated inbound address |
| Webhook retries | Failure logged, no automatic retry | 10 retries from 1 minute up to 6 hours |
| Spreadsheet output | Excel and CSV export in the browser | None; JSON only |
| Pricing | From $24/mo billed yearly for 100 parsed emails; Pro $249/mo billed yearly, unlimited | Inbound on Pro from $16.50/mo with 10,000 emails, $1.30 per extra 1,000 |
| Best for | Teams that need fields, not messages | Developers who want raw mail and will write the parsing |
Postmark details are taken from postmarkapp.com pricing and inbound documentation as of November 2026. Check both before you buy.
Frequently asked questions
Does Postmark parse inbound emails?
Postmark parses the structure of an inbound email into JSON: sender, recipients, subject, text and HTML bodies, headers and base64 attachments, plus a stripped reply for plain text English replies. It does not extract business values such as an order number or a total from the body. That extraction is what MailParse adds on top.
Is Postmark Inbound included in every plan?
No. The Postmark pricing page lists inbound processing on the Pro and Platform plans and shows it as unavailable on Free and Basic. Pro starts at $16.50 a month with 10,000 emails. Check the current table before you buy, because plan contents change.
Can I keep Postmark and still use MailParse?
Yes. Keep Postmark as the receiver for your domain and forward the messages you want parsed to your MailParse forwarding address, or POST the raw message from your Postmark webhook handler to the MailParse API. You then receive named fields instead of writing the extraction.
What does MailParse send to my webhook?
One JSON record per parsed email with the sender, subject, date and every field you named, signed with a MailParse-Signature header you verify with your secret. If your endpoint is down the failure and status code are recorded, and the record can still be fetched through the API or exported.
How much does a Postmark Inbound alternative cost?
MailParse starts at $24 a month billed yearly for 100 parsed emails, Plus is $74 billed yearly for 500, and Pro is $249 a month billed yearly with unlimited parsing. You can run 3 parses on your own emails before paying, so you see the real fields first.
Get the fields out of your inbound email
Paste or upload a real message, name the values you need, and see the JSON record your endpoint would receive.