EML Parser

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 .json file 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 .eml files 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.

{
  "eml": "From: [email protected]\r\nTo: [email protected]\r\nSubject: Hello\r\n\r\nHi there",
  "emlUrls": ["https://example.com/message.eml"],
  "saveAttachments": false
}

Output

Each email becomes one JSON file plus a summary row in the dataset.

{
  "subject": "Hello",
  "from": "[email protected]",
  "date": "2026-08-22T10:00:00.000Z",
  "attachments": 0,
  "resultUrl": "https://api.apify.com/v2/key-value-stores/.../records/email-0001.json",
  "ok": true
}

The linked JSON file contains the full parsed message:

{
  "subject": "Hello",
  "from": "[email protected]",
  "to": "[email protected]",
  "cc": null,
  "date": "2026-08-22T10:00:00.000Z",
  "messageId": "<[email protected]>",
  "textBody": "Hi there",
  "htmlBody": null,
  "headers": { "from": "[email protected]", "subject": "Hello" },
  "attachments": [{ "filename": "invoice.pdf", "contentType": "application/pdf", "size": 20481 }]
}

Output schema

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.

You pay only for what the run returns. Set a maximum cost per run and it stops cleanly at that limit.