Open Source on GitHub

"A Huge Time-Saver"

– Early tester

You didn't become an automation builder to debug email parsers

ParseMyMail turns messy emails — body and attachments — into clean JSON, sent straight to your webhooks. Set it up in minutes. Forget about it forever. Free, open source, and self-hostable.

Open Source on GitHub

Works with the tools you already use

You already know this feeling

You built a clean scenario. Modules connected, data populating, client happy.

Then one Tuesday morning, it stops. An invoice layout changed. A client replied inline instead of forwarding. A PDF attachment came through as a scan instead of text.

Now you're back in there — rewriting scenario, adding regex and error handlers, patching things together hoping it holds until next month.

There has to be a better way.

What if the parser just... handled it?

No regex. No rules to maintain. No separate steps for attachments.

Just one parser that reads the entire email — body, PDFs, images, all of it — understands what's inside, and gives you a clean JSON with exactly the fields you asked for.

Every time. Even when the format changes. Even when a field is missing.

HOW IT WORKS

Set it up before your coffee gets cold.

Three steps. That's it.

1. Get your email address.

Create a parser and we generate a unique email address for you, or customize it to whatever you want. Forward a sample email to get started.

2. Tell it what you need.

Create your fields in plain English — describe what to extract, and test on your sample email for free. Iterate until the JSON is exactly right.

No regex. No code.

Create your fields in plain English — describe what to extract, and test on your sample email for free. Iterate until the JSON is exactly right.

No regex. No code.

Create your fields in plain English — describe what to extract, and test on your sample email for free. Iterate until the JSON is exactly right.

No regex. No code.

3. Connect your webhook.

Paste your Make, Zapier, or any webhook URL. From now on, every email sent to that address is parsed and the JSON is fired to your automation. Automatically.

"The simple setup is a big win for my client projects"

– Early tester

Messy emails? That’s the whole point.

ParseMyMail reads the email body and all attachments in a single pass, so it understands the full context before extracting a single field.

Ugly HTML?

You get clean data. We deal with the ugly source code.

Ugly HTML?

You get clean data. We deal with the ugly source code.

50 different vendors?

One parser to rule them all, as long as the data goes to the same webhook.

50 different vendors?

One parser to rule them all, as long as the data goes to the same webhook.

Email body + PDF invoice?

One pass. One JSON. No extra modules to download, OCR, or merge.

Email body + PDF invoice?

One pass. One JSON. No extra modules to download, OCR, or merge.

Human-written emails?

If you can read it, we can parse it.

Human-written emails?

If you can read it, we can parse it.

Built for production. Not just demos.

Other tools work great on the first test. Then they break in week two when something unexpected happens.

ParseMyMail is built to keep your automations running no matter what.

A field is missing?

The key stays in the JSON, the value is null. Your scenario keeps running.

A field is missing?

The key stays in the JSON, the value is null. Your scenario keeps running.

A format changes?

The parser adapts automatically. No rules to update, nothing to fix.

A format changes?

The parser adapts automatically. No rules to update, nothing to fix.

Something fails?

You get a webhook alert before your client even notices.

Something fails?

You get a webhook alert before your client even notices.

COMPARISON

You have options. Here's how they compare.

You could build it yourself with GPT modules and duct tape. You could write regex rules and hope the format never changes.

Or you could use a tool that was built specifically for this problem.

Legacy Tools

Alternatives

DIY AI Modules

Setup Time

Minutes

Hours of rule-building

Hours of prompt engineering

Hours

Regex or code required

Yes

Yes (prompt crafting)

Yes

Handles format changes

Automatically

Breaks, need manual fix

Unpredictable

Breaks or unpredictable

Body + attachments together

One pass, one JSON

Separate steps

You build the logic

Separate steps or DIY

Guaranteed JSON schema

Always, every key present

Depends on rules

No guarantee

Maintenance needed

None

Constant rule tweaking

Constant prompt tweaking

Constant tweaking

ParseMyMail

Alternatives

Setup Time

Minutes

Hours

Code needed

Yes

Format changes

Adapts

Breaks

Attachments

One JSON

Separate steps

JSON schema

Guaranteed

No guarantee

Maintenance

None

Constant

FOUNDERS NOTE

“ Extracting clean data from emails shouldn't be painful. So I built ParseMyMail — and now I'm giving it away. The full source is on GitHub: fork it, self-host it, contribute to it. „

Robin, Founder

FAQ

Still have questions?

Do I need to know regex or code?

No. You describe what to extract in plain English. No code, no patterns.

What if my email format changes?

The parser adapts automatically. No rules to update.

What if a field is missing from an email?

The key stays in the JSON, the value is null. Your automation keeps running.

Can it handle PDF attachments?

Yes. ParseMyMail reads the email body, PDFs and images in a single pass. You get one JSON output, not separate pieces to merge.

Do I have to manually forward every email?

It's up to you. Most users set up an auto-forwarding rule (in Gmail or Outlook) to let the parser run 24/7 in the background. But you can absolutely forward emails manually if you prefer to hand-pick which ones to process. Both methods work instantly.

What automation tools does it work with?

Anything that accepts a webhook — Make.com, Zapier, n8n, and more.

Do I need to know regex or code?

What if my email format changes?

What if a field is missing from an email?

Can it handle PDF attachments?

Do I have to manually forward every email?

What automation tools does it work with?

Free, open source, and self-hostable

Clone it, deploy it, own it. The full code is on GitHub.

Open Source on GitHub