Turn any email into a webhook

Inbox Bridge gives you a unique email address that instantly forwards every message to your API as a structured JSON payload. No email servers. No polling. Just webhooks.

Free forever on the starter tier. No credit card required.

Migrating? Compare to CloudMailin.

How Inbox Bridge works

Go from zero to receiving webhook payloads in under a minute.

1

Create a bridge

Get a unique email address and configure your webhook endpoint in seconds.

2

Receive emails

Create a forwarding rule or use the address directly. We handle all inbound processing.

3

Get webhooks

Structured JSON payloads hit your endpoint instantly with automatic retries on failure.

Email
Bridge
Webhook
Read the full inbound email webhook tutorial

Example webhook payload

A clean JSON payload posted to your webhook for every inbound email.

{
  "id": "clx9k2p7a0001abcd",
  "receivedAt": "2026-05-12T14:23:01.000Z",
  "from": { "email": "stripe@stripe.com", "name": "Stripe" },
  "to": [{ "email": "a1b2c3d4@webhook.inboxbridge.io", "name": "" }],
  "cc": [],
  "bcc": [],
  "replyTo": null,
  "subject": "Payment received for invoice INV-4829",
  "date": "2026-05-12T14:23:00.000Z",
  "textBody": "Your payment of $249.00 was successful...",
  "htmlBody": "<p>Your payment of $249.00 was successful...</p>",
  "attachments": [
    {
      "name": "receipt.pdf",
      "contentType": "application/pdf",
      "contentLength": 18244,
      "contentId": null
    }
  ]
}

Built for reliability

Everything you need to pipe email data into your application with confidence.

Instant delivery

Emails are parsed and forwarded to your webhook endpoint in seconds, not minutes.

Automatic retries

Failed deliveries are retried with exponential backoff. Never miss a payload.

Secure by default

Payloads are encrypted in transit. Hash-based email addresses keep your endpoints private.

Structured JSON

Every email is parsed into a clean JSON payload — subject, body, headers, attachments, and metadata.

Delivery tracking

See the status, response code, and duration of every delivery attempt at a glance.

Manual replay

Something break downstream? Replay any delivery with one click.

New to this? Learn how email-to-webhook works.

Use cases

Anywhere email meets code, Inbox Bridge fits.

Inbound lead capture

Forward form submission emails to your CRM or database via webhook. No parsing scripts needed.

Transactional email monitoring

Track delivery receipts, bounce notifications, and out-of-office replies in real time.

Support ticket ingestion

Pipe customer emails directly into your ticketing system or Slack channel.

IoT and device alerts

Machines and sensors that email alerts? Turn them into structured data your backend can act on.

Simple, transparent pricing

Start free. Scale as you grow.

Free
Start with the basics, upgrade anytime.
$0/month
  • 1 bridge
  • 1,000 emails/month
  • 3 retries
  • No credit card required
  • Upgrade anytime
Starter
Run your first production email-to-webhook workflows.
$11.20/month

Billed annually at $134.40

  • 5 bridges
  • 2,000 emails/month
  • 5 retries
  • Manual replay
  • JSON viewer
Most Popular
Pro
For apps that rely on email as a data source.
$23.20/month

Billed annually at $278.40

  • 15 bridges
  • 10,000 emails/month
  • 10 retries
  • Everything in Starter
  • Priority support
Business
High-volume pipelines and critical workflows.
$47.20/month

Billed annually at $566.40

  • 50+ bridges
  • 50,000 emails/month
  • 15 retries
  • Everything in Pro

Need something different? Email us

Frequently asked questions

How is this different from SendGrid Inbound Parse or Mailgun Routes?

Inbox Bridge focuses on one job — turning inbound email into a reliable JSON webhook — and gives you a dashboard, retries with exponential backoff, one-click delivery replay, and per-bridge delivery logs out of the box. SendGrid and Mailgun bundle inbound parsing inside large email platforms; for a small team that just needs the webhook, the surface area and pricing here are simpler.

Do I get a custom domain, or just @webhook.inboxbridge.io?

Every bridge gets a unique hash-based address at webhook.inboxbridge.io (for example a1b2c3d4@webhook.inboxbridge.io). Custom domains are not part of the current plans — most teams either point a forwarding rule at the bridge address or use the address directly.

What happens if my webhook endpoint is down?

A non-2xx response moves the delivery into a retry queue. Inbox Bridge retries with exponential backoff (30s, 60s, 2m, and so on, with 20% jitter) up to your plan’s retry limit. You can also manually replay any delivery from the bridge detail page once your endpoint is healthy.

How are attachments delivered?

Attachments are included in the JSON payload as an array of objects with filename, contentType, contentLength, and a downloadable URL. The raw bytes are not posted directly to your webhook — pull them as you need them.

Is there a free tier?

Yes. The Free plan covers 1 bridge, 1,000 emails per month, and 3 retry attempts. No credit card required — sign up and you can be receiving webhooks in a couple of minutes.

How quickly does an email become a webhook delivery?

Typically a few seconds end to end. Postmark accepts the inbound email, Inbox Bridge parses it and POSTs the JSON payload to your endpoint immediately. There is no polling delay.

Stop building email infrastructure

Let Inbox Bridge handle parsing, delivery, and retries so you can focus on what your app does with the data.