EML Parser — Email to JSON (MIME)
Pricing
from $0.0015 / email parsed
EML Parser — Email to JSON (MIME)
Parse raw .eml / MIME emails into clean JSON — subject, sender, recipients, text & HTML bodies, headers and attachments. For inbox automation and data pipelines.
Pricing
from $0.0015 / email parsed
Rating
0.0
(0)
Developer
hiper soft
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
3 days ago
Last modified
Categories
Share
Turn raw .eml / MIME emails into clean, structured JSON — subject, sender, recipients, text and HTML bodies, headers and attachments — ready for automation and data pipelines.
What it does
- Parses raw
.eml/ MIME email into structured JSON. - Extracts subject, from, to, cc, date, message ID.
- Returns both the plain-text body and the HTML body.
- Lists attachments (filename, content type, size) — and can save their bytes on request.
- Keeps a useful subset of headers for routing and threading.
- Saves each parsed email as a
.jsonfile and returns a link to it.
Use cases
- n8n / Make / Zapier — drop parsed email fields straight into a workflow: create tickets, log leads, route messages.
- Support & CRM — normalize inbound mail into records without writing a parser.
- Data pipelines — batch-convert archived
.emlfiles into JSON for search and analytics. - Compliance & e-discovery — extract headers, bodies and attachment lists from stored messages.
Input
Provide a raw email as text, and/or a list of URLs to .eml files.
| Field | Type | Description |
|---|---|---|
eml | string | A raw .eml / MIME email pasted as text (parses a single message). |
emlUrls | array | Direct URLs to .eml files to download and parse. |
saveAttachments | boolean | Save attachment file bytes (small files only) instead of metadata alone. |
Output
Each email becomes one JSON file plus a summary row in the dataset.
The linked JSON file contains the full parsed message:
Output schema
| Field | Type | Description |
|---|---|---|
subject | string | Email subject line. |
from | string | Sender address. |
date | string | Message date (ISO 8601). |
attachments | integer | Number of attachments found. |
resultUrl | string | Link to the full parsed JSON file. |
ok | boolean | Whether the email parsed successfully. |
FAQ
Can it handle attachments? Yes — attachment metadata (filename, type, size) is always returned, and file bytes can be saved when saveAttachments is enabled (small files only).
Both text and HTML bodies? Yes — both are returned when present in the message.
Can I automate it? Yes — connect it through integrations on the Apify platform and the Apify API, including n8n, Make and Zapier.
Notes
Original clean-room implementation.
