Product inboxes
Receive replies, generated aliases, support mail, and approval messages without running your own mailbox stack.
InboundReceive mail as product data
Inbound email routing for product workflows
Point MX records at Sendix and turn replies, aliases, support mail, approvals, and lead-capture addresses into parsed events your application can route.
- Per-domain MX readiness
- Parsed headers, text, and HTML
- Attachment metadata
- Forwarding rules and webhooks
inbound receiver
guided enablementDNSMX
TypeMX
Host@
Valueinbound.sendix.dev
Priority10
event.json
{
"type": "inbound.received",
"mailbox": "support",
"attachments": 2,
"route": "ticket-intake"
}Message accepted
mx accepted
MIME parsed
headers + bodies
Rule matched
support inbox
Event delivered
webhook sink
Parsed summarysupport@
Receiving flow
Treat incoming email as a routed event, not an unmanaged inbox.
Inbound moves a message through domain readiness, MIME preservation, parsing, rule matching, and webhook or forwarding delivery.
01
Domain route
Point MX records
Enable receiving on a verified domain and publish the MX records Sendix shows in the dashboard.
02
Raw + parsed
Preserve the message
Keep a raw MIME path for audit while extracting recipients, headers, subject, body, and attachment metadata.
03
Mailbox logic
Match a rule
Route support, reply, alias, and workflow addresses to a stored inbox, forward target, or webhook sink.
04
inbound.received
Deliver the event
Send structured inbound events to your app so replies can create tickets, trigger approvals, or update records.
Routing table
Rules decide whether a message becomes a forward, a record, or a webhook.
Inbound routes can support human inboxes and product automation at the same time: forward important mail, store the full trail, and notify your app with a structured payload.
Open receiving inboxAddressRuleTarget
Inbound surface
Everything needed to make email input debuggable.
The receiving path keeps DNS state, raw messages, parsed fields, rules, storage, and webhook delivery in the same operational frame.
Attachment metadata
Track attachments as structured objects so your app can decide what to store, forward, or inspect.
Guided enablement
Inbound remains an enablement-gated path so MX, receiver health, and routing behavior can be verified first.
Stored receiving views
Review received messages in Sendix while your app receives the event payload it needs.
Signed workflow input
Connect incoming mail to ticket creation, CRM intake, approvals, or automation triggers through a webhook sink.
Use cases
Useful anywhere replies need to become application state.
Inbound is most valuable when an email address is an input channel for a real workflow.
Customer replies
Route replies from transactional threads into support and product workflows.
Generated aliases
Create unique addresses for projects, tickets, tenants, orders, or lead capture.
Email approvals
Accept structured actions from inbox replies while preserving the original message.
Works with the same Sendix workspace
Sending domains and receiving routes stay in one control plane.
Start with the free account, verify a domain, and enable inbound with the right MX and forwarding checks before production traffic moves.
FAQ
Inbound questions before you point MX records at Sendix.
The main decisions are domain readiness, routing behavior, retention needs, and what your app does with the event.
Do I need to host my own mailbox?
No. Sendix can receive the message on your domain, parse it, store it, forward it, or deliver a structured event to your app.
Is inbound enabled for every workspace?
Inbound is currently guided enablement. That keeps domain MX records, receiver health, and forwarding rules checked before production traffic points at Sendix.
Can I keep the original message?
Yes. The inbound path is designed around parsed fields plus a raw MIME preservation path for audit and troubleshooting.
Can inbound mail trigger product workflows?
Yes. Inbound events can be sent to your webhook endpoint and used by your app to create tickets, approvals, CRM records, or downstream automations.
Ready to send your first email?
25,000 emails free every month. No credit card required. Upgrade only when you outgrow the free tier — and we will let you know when that time comes.
Managed SaaS platform · Native SMTP engine · SOC 2 in progress