Forwarding breaks
Auto-forward rules silently fail, get rate-limited, or strip attachments. One mailbox change quietly takes a whole pipeline down.
Connect any domain, receive every message as an inbox item, API object, or webhook event, and route email into the systems your team already uses.
{ "event": "message.received", "to": "invoices@acme.com", "from": "vendor@…", "subject": "Invoice #1042", "attachments": [{ "file": "invoice-1042.pdf", "size": 184203 }], "rule": "invoices-to-erp" }
Built around the primitives operations teams actually need
Leads, invoices, support replies, applications, approvals, and customer documents still arrive by email. Most teams forward them manually, lose context, or glue together brittle rules across Gmail, Outlook, and Zapier. InletOps turns inbound email into structured, observable workflows.
Auto-forward rules silently fail, get rate-limited, or strip attachments. One mailbox change quietly takes a whole pipeline down.
Critical steps live in someone's personal inbox. There's no audit trail, no status, and no way to see what was handled or dropped.
Encodings, nested parts, inline images, charset edge cases. Teams burn weeks on a parser instead of shipping the workflow that matters.
Add a domain, drop in the records, and we verify MX and DNS. No mailbox migration required.
Every message lands as a clean, parsed object — headers, body, and attachments included.
Match on sender, recipient, subject, or content. Forward, tag, parse, or branch — no code needed.
Fire signed webhooks, call your API, or push to the tools your team already runs on.
A complete toolkit for receiving, routing, and acting on email — without standing up your own mail infrastructure.
Send any domain or subdomain to InletOps and route by recipient.
Unlimited aliases and wildcard addresses without provisioning mailboxes.
Match, branch, and transform messages with a visual rule builder.
Durable delivery with automatic retries and one-click replay.
Read messages, manage domains, and configure routing programmatically.
Files extracted, scanned, and served over signed, expiring URLs.
Structured headers, text, and HTML — the MIME mess handled for you.
Forward to any address with full, searchable delivery records.
Shared web inbox with assignment, status, and threaded context.
Inbound filtering and attachment scanning before delivery.
Configure how long messages and attachments are stored.
Every route, forward, and delivery recorded and exportable.
Stop writing MIME parsers. Every inbound message arrives as a clean, predictable JSON payload — delivered to your endpoint the moment it lands.
{ "event": "message.received", "domain": "acme.com", "to": "invoices@acme.com", "from": "vendor@example.com", "subject": "Invoice #1042 attached", "attachments": [ { "filename": "invoice-1042.pdf", "content_type": "application/pdf", "size": 184203 } ], "routing_rule": "invoices-to-erp", "received_at": "2026-05-10T14:22:31Z" }
Capture replies to transactional email and thread them back into your app.
Pull invoices and attachments into your ERP or accounting system automatically.
Manage inbound for dozens of client domains from a single workspace.
Route, tag, and assign inbound support mail without a heavyweight helpdesk.
Collect applications and resumes as structured, searchable records.
Turn inbound demo and contact emails into CRM leads in real time.
Inbound email touches sensitive data. We give you verification, signed delivery, audit logs, and retention controls so you stay in control of every message.
Prove ownership before any mail is accepted for a domain.
Guided setup and checks so your domains authenticate correctly.
Verify every payload with a signature before you trust it.
A complete, exportable record of what arrived and where it went.
Decide how long messages and attachments are stored — then enforce it.
Throttling and abuse protection keep inbound flows healthy.
Files are scanned before delivery, with results attached to each event.
Slide to your monthly inbound volume. Every plan includes the web inbox, parsing, signed webhooks, and audit logs.
$0.00 due today. No card required.
$0.00 due today. No card required.
Lifetime license. No recurring fees.
Need more than 10M messages a month, SSO, or custom retention? Talk to the founder →
No. InletOps is infrastructure for inbound email automation. We receive, parse, route, and forward messages for domains you connect — we don't host mailboxes or replace your email provider.
Yes. Most teams point a domain or a few addresses at InletOps for automation while keeping Gmail or Microsoft 365 for everyday mail. The two run side by side.
InletOps is focused on inbound. We forward messages and trigger workflows, but we're not a bulk sending or marketing platform — pair us with your existing sending provider when you need to send.
Yes — that's the point. Connect any domain or subdomain, verify ownership with DNS records, and start receiving inbound mail as inbox items, API objects, or webhook events.
Attachments are extracted, scanned for malware, and made available over signed, expiring URLs. Each webhook event includes filename, content type, and size so your systems can fetch only what they need.
Absolutely. A single rule can forward a message to a human, tag it, and fire a webhook to your API at the same time — with full logs of every action.
Yes. Use wildcard and catch-all addresses to capture every message sent to a domain, then route them by recipient, sender, or content with the rules engine.
Both. Operations teams build routing visually in the web app; developers reach for the REST API, signed webhooks, and raw MIME. Inbound email becomes a workflow everyone can see and control.
Connect your first domain in minutes and start routing inbound email into the systems your team already uses. Free to start — no card required.