Drop-in support inbox
Give your tiny app a real support@ that triages and AI-drafts replies — without buying Zendesk.
Inbound email, handled at the edge
Your app's emails
finally reply back.
The inbound email webhook API for developers.
Sending email is solved. Receiving it isn't. Point a domain at ReplyFlow and every reply arrives as clean, threaded, intent-tagged JSON — quoted history and signatures stripped — ready for your webhook. No SMTP, no DNS rabbit-hole, no helpdesk.
Made for people shipping apps on Lovable, Bolt, v0, Cursor & Replit.
Free plan, no card. Built in the Netherlands by Dutchcode B.V. — blinkof.ai runs its inbound mail on ReplyFlow.
Live demo · runs in your browser
A messy reply in. Clean JSON out.
Pick an example (or paste a real reply), then watch ReplyFlow strip the noise and tag the intent.
This is the actual cleaning & intent step, running client-side. In production it happens at the edge the instant the email lands — then hits your webhook in milliseconds.
Or try it for real
Email this address — watch the JSON appear.
Send a reply (quote some history, add a signature) to your one-time address below. ReplyFlow catches it at the edge and the parsed payload shows up here in seconds.
demo-…@replyflow.com
Generating your address…
// Your parsed reply will land here.
The gap nobody warns you about
You shipped the app. A user hit reply. It vanished.
You wired up Resend to send a notification in ten minutes. Then a customer replied to it — and the message fell into a void, or a personal Gmail that never gets checked.
Handling inbound mail means MX records, SPF/DKIM, an inbound parser, stripping quoted history, threading by Message-ID, storing attachments, filtering spam. That's a week of plumbing for something that should be one line.
ReplyFlow is that one line.
How it works
Three steps. Zero infrastructure.
1
Point your domain
Add one MX record (or use a @replyflow.com address). We handle SPF, DKIM & spam at the edge.
2
We clean every reply
Our edge parses the message, strips quotes & signatures, threads it, and tags the intent.
3
You get JSON
A signed webhook hits your app with structured data. Or read everything back via the message log & API.
Recipes
The things you actually want to build.
Reply-to-confirm
“Reply YES to approve.” Turn a plain-English reply into a clean webhook event your app can act on.
Two-way threads
Marketplace messages, comments, support — let users reply by email and pipe it straight back into your app.
Human-in-the-loop
Email a human mid-workflow, pause, and resume when they reply. Approvals for your agents & automations.
The payload
What lands on your webhook
{
"from": { "name": "Sarah Chen", "email": "sender@example.com" },
"subject": "Re: Confirm your demo time",
"thread_id": "thr_9f2c…",
"text": "Yes, that works for me — let's do Friday at 2pm.",
"intent": "confirm",
"signature_removed": true,
"quoted_removed": true,
"attachments": []
}
Pricing
Starts free. Scales on usage.
Free
€0
Start free- 100 replies / mo
- 1,000 API calls / mo
- Up to 10 addresses
- Cleaning, intent + threading
- Webhook + dashboard
Most popular
Pro
€19/mo
Get started — Pro- 2,000 replies / mo
- 20,000 API calls / mo
- Everything in Free
Same pipeline on every plan — cleaning, intent, threading, signed webhooks with automatic retries, the read API, and full message history. Plans differ only in volume; see the docs for exact limits. Prices exclude VAT.
AI agent or procurement tool? Machine-readable pricing →
FAQ
Questions, answered.
What is ReplyFlow?
ReplyFlow is an inbound email webhook API. Point a domain at it and every reply comes back as clean, threaded, intent-tagged JSON on your webhook — quoted history and signatures stripped, with no SMTP server to run.
Do I need to run a mail server?
No. ReplyFlow receives email at the edge and delivers it straight to your webhook. There's no SMTP server, DNS rabbit-hole, or helpdesk to maintain.
What counts as a reply?
Any inbound email received at one of your ReplyFlow addresses — whether it's a reply to a message you sent or a direct email. Each message counts as one reply, regardless of size or attachments.
Is there a free plan?
Yes. The Free plan is permanent: 100 inbound replies per month, no card required. Paid plans start at €19/month for 2,000 replies.
How are webhooks secured?
Every webhook is signed with HMAC-SHA256 over the timestamp and body, so your endpoint can verify each request genuinely came from ReplyFlow before trusting it.
Who's behind ReplyFlow?
ReplyFlow is built and operated by Dutchcode B.V., a software company registered in the Netherlands — the same team behind blinkof.ai, which runs its own inbound mail on ReplyFlow. Questions go to support@dutchcode.com and a human answers.
What happens to the email you receive for me?
It's parsed on Cloudflare's edge network and stored so your dashboard and API can read it back — nothing else. No advertising trackers, no selling personal data, and you can delete a message, an address, or your whole account yourself at any time. The full GDPR privacy statement is public.
Get started
Stop losing replies.
Sign in, grab your inbound address, point your webhook at it. Free to start — no card, no SMTP, no servers to run.