📬 Inbound - Email Infrastructure Made Simple

Stop juggling email providers. Start building.

Inbound gives you programmable email addresses that automatically process incoming messages and trigger webhooks in your app. Think of it as email infrastructure that actually works the way you'd want it to.

What does it do?

📨 Send & Receive Emails Programmatically

Sending Emails

import { Inbound } from 'inboundemail'

const inbound = new Inbound(process.env.INBOUND_API_KEY!)

const email = await inbound.emails.send({
  from: 'Inbound User <hello@yourdomain.com>',
  to: 'user@example.com',
  subject: 'Welcome!',
  html: '<p>Thanks for signing up!</p>',
  tags: [{ name: 'campaign', value: 'welcome' }]
})

console.log(`Email sent: ${email.id}`)

Receiving & Replying to Emails

import { Inbound, type InboundWebhookPayload, isInboundWebhookPayload } from 'inboundemail'
import { NextRequest, NextResponse } from 'next/server'

const inbound = new Inbound(process.env.INBOUND_API_KEY!)

export async function POST(request: NextRequest) {
  try {
    const payload: InboundWebhookPayload = await request.json()
    
    // Verify this is a valid Inbound webhook
    if (!isInboundWebhookPayload(payload)) {
      return NextResponse.json({ error: 'Invalid webhook' }, { status: 400 })
    }
    
    const { email } = payload
    console.log(`📧 Received email: ${email.subject} from ${email.from?.addresses?.[0]?.address}`)
    
    // Auto-reply to support emails
    if (email.subject?.toLowerCase().includes('support')) {
      await inbound.reply(email, {
        from: 'support@yourdomain.com',
        text: 'Thanks for contacting support! We\'ll get back to you within 24 hours.',
        tags: [{ name: 'type', value: 'auto-reply' }]
      })
    }
    
    // Auto-reply to thank you emails
    if (email.subject?.toLowerCase().includes('thanks')) {
      await inbound.reply(email, {
        from: 'hello@yourdomain.com',
        html: '<p>You\'re welcome! Let us know if you need anything else.</p>'
      })
    }
    
    return NextResponse.json({ success: true })
  } catch (error) {
    console.error('Webhook error:', error)
    return NextResponse.json({ error: 'Webhook processing failed' }, { status: 500 })
  }
}

Quick Start

1. Install the SDK

npm install inboundemail
# or
bun add inboundemail

2. Initialize with your API key

import { Inbound } from 'inboundemail'

// Get your API key from inbound.new
const inbound = new Inbound(process.env.INBOUND_API_KEY)

3. Add a domain

const domain = await inbound.domains.create({
  domain: "yourdomain.com"
})

console.log("Domain added:", domain.domain)

4. Create an email address

const emailAddress = await inbound.emailAddresses.create({
  address: "hello@yourdomain.com",
  webhookUrl: "https://yourapp.com/webhook/email"
})

console.log("Email address created:", emailAddress.address)

5. Start receiving emails

Send an email to hello@yourdomain.com and watch your webhook fire with the parsed content.

Local Development

# Clone and setup
git clone https://github.com/R44VC0RP/inbound
cd inbound
bun install

# Start local Docker services and run next dev against them
bun run dev:local

# Run the self-contained API end-to-end suite
bun run test:e2e

dev:local runs Postgres, a Neon HTTP proxy, and Redis in Docker and blanks every production credential for the dev server. Outgoing email goes to a local SES stub (http://127.0.0.1:8780/_local/messages) and is looped back into /api/inbound/webhook, so sending to your own local domain shows up as received mail. Billing checks are answered by a local Autumn mock.

• Sign in at http://localhost:3000/login with any email; the magic link is printed in the terminal.
• bun run dev:local seed you@example.com adds a demo domain, address, endpoint, and received emails.
• bun run dev:local api-key you@example.com creates a local user with a verified demo.localtest.me domain and prints an API key.
• bun run dev:local reset wipes all local data (for example after lib/db/schema.ts changes).

Plain bun run dev refuses to connect to a remote database unless ALLOW_REMOTE_DB=true is set.

API Features

• REST API with OpenAPI spec
• Webhooks with signature verification
• Email parsing with HTML/text extraction
• Attachment handling with S3 storage
• Spam filtering and security checks
• Domain verification and DNS management
• Usage tracking and billing integration

Contributing

We're building email infrastructure that doesn't suck. Want to help?

1. Fork the repo
2. Make your changes
3. Test with bun run inbound-webhook-test
4. Submit a pull request

---

Ready to ditch your email provider? Get started →