Inbound email, parsed to JSON.
Give your product a real address that receives. Drin parses every inbound message — headers, text, HTML, attachments — into structured JSON and posts it to your webhook in milliseconds. Threaded to the original, retained by plan, readable over the API or the dashboard.
Free sandbox to integrate · Production from $3/month
Email is a two-way street. Drin drives both.
Most senders treat receiving as an afterthought — a raw MIME blob dumped on a webhook that forgets after a month. Drin treats inbound as a first-class half of email: a real inbox on your own domain, not a black box.
Every message is parsed to clean JSON — from, subject, plain text, HTML, and attachments broken out — stitched into its thread by references, and kept for as long as your plan allows (7–180 days, longer on Enterprise). Read it over a webhook, the REST API, or hand it to an agent over MCP.
A clean object, not a raw blob.
Point an address at your webhook and Drin does the MIME parsing for you — decoding, charset, attachments, threading — and posts a tidy JSON object your handler can act on immediately.
Read the docs →// POST → https://yourapp.com/inbound { "from": "sarah@gmail.com", "to": "support@yourapp.com", "subject": "Re: your invoice", "text": "Can you resend #8821?", "thread_id": "th_2f9…", "attachments": 2 } # parsed, threaded, retained — no MIME wrangling on your side
The three that make it work.
MIME parsed to JSON — from, subject, text, HTML and attachments broken out. Your handler acts on fields, not a raw payload.
Replies are stitched to the original message by references, so a conversation stays a conversation across both directions.
Kept 7–180 days by tier (longer on Enterprise) and readable over the API — not a webhook that forgets after 30 days.
The surfaces that power it.
Not a bolt-on — this job runs on the same platform as everything else you send and receive. One account, one bill.
Asked about inbound & parsing.
Do I get a real address or just a webhook?+
A real inbox on your own domain. Mail is stored, threaded and readable over the API or dashboard — the webhook is one way in, not the only record.
How is this different from Resend's inbound?+
Resend's inbound is a webhook with a 30-day retention ceiling. Drin gives you inboxes on your domain, parsed to JSON and retained by plan, that you can also read back over the API at any time.
Are attachments handled?+
Yes — attachments are parsed out of the message and made available to your handler; you're not left decoding MIME yourself.
Can an agent read the inbox?+
Yes. The same inbox is reachable over the 54-tool MCP server, so an agent can read, search and reply on the thread.