Rules that fit your app
Match recipients, senders, subjects or attachment presence. Choose which incoming messages reach each workflow.
Receive messages and attachments as structured data, then route them into the workflows you build.
Inbound Email is Preview.
Receiving-domain setup is arranged with us.
The sender uses email. Your app receives the fields it needs to do something useful.
A message arrives at your configured receiving address.
support@in.yourapp.exampleExtract the message fields and attachments, then match the rules you choose.
Use the sender, subject and message body to start a conversation in your app.
{
"messageId": "msg_example_01",
"envelope": {
"from": "alex@example.com",
"to": [
"support@in.yourapp.example"
],
"subject": "I need a hand with my workspace"
},
"bodies": {
"text": "Hi! I cannot open the project my teammate shared. Can you help?"
},
"attachments": []
}Verify webhook signatures before processing messages. Deliveries can repeat; use the message ID to recognize a message you've already handled.
Route the message, retrieve its files, and inspect what happened when your app received it.
Match recipients, senders, subjects or attachment presence. Choose which incoming messages reach each workflow.
Get file metadata with the message. Retrieve the file through an authenticated API when your app needs it.
Inspect webhook delivery history. Replay parked webhook deliveries through the API when you're ready to try again.
Example interfaces for your app. Inbound Email is Preview.
Send structured messages to a webhook, forward to a verified address, or read stored messages through the API.
Choose a receiving subdomain for your app while keeping your existing mailboxes. We'll work through domain and DNS setup during Preview onboarding.
Add Inbound Email on its own. Your existing sign-in, backend and application workflows can stay in place.
Tell us what you want incoming mail to do in your app.
Preview · Setup by arrangement.