How do I receive an email as a webhook?

Add an email input to a bucket in Webhook Relay. You get a unique address like @in.webhookrelay-mail.com, and every message sent to it is parsed to JSON and POSTed to your endpoint. No SMTP server or MX setup required.

What does the parsed email payload contain?

A flat JSON object: from, from_name, subject, text, html, to, cc, headers, message_id, spf/dkim/dmarc results, and an attachments array (base64 content). See the payload reference in the docs.

Can I forward inbound email to Slack, a database or my own API?

Yes. Because the email becomes an ordinary event on the bucket, you can transform it and forward it anywhere — Slack, Discord, Teams, Google Sheets, Airtable, Notion, your API, or your database. See the example tutorials.

Receive Emails as Webhooks: Inbound Email Parsing & Forwarding

Receive emails as webhooks

A lot of useful information still arrives as email — support requests, server alerts, order confirmations, vendor notifications, and form submissions from tools that only email you. Acting on it usually means running a mail server, polling an IMAP inbox, or wiring up Zapier.

Now there's a simpler option: Webhook Relay can receive email for you and turn each message into a webhook.

Receiving

Add an email input to a bucket and Webhook Relay gives you a unique address like [email protected]. Point any sender at it — there's no DNS or MX setup, and nothing to host. See Email to Webhook for the overview, or the docs to set one up.

Parsing

Every message is parsed server-side into clean JSON and delivered with Content-Type: application/json:

{
  "from": "[email protected]",
  "from_name": "Jon Snow",
  "subject": "Can't log in to my account",
  "text": "Hi, I can't log in since this morning…",
  "html": "<p>Hi, I can't log in since this morning…</p>",
  "to": ["5519fb0d-…@in.webhookrelay-mail.com"],
  "spf": "pass", "dkim": "pass", "dmarc": "pass",
  "attachments": [
    { "name": "screenshot.png", "content_type": "image/png", "size": 48213, "content": "iVBORw0KGgo…" }
  ]
}

You get the sender, subject, both body parts, all headers, the SPF/DKIM/DMARC results, and attachments (base64-encoded). The full payload reference lists every field, and you can restrict senders and cap attachments per input.

Forwarding

Because the parsed email becomes an ordinary event on the bucket, you can do anything you'd do with a webhook: forward it to your endpoint (public or behind a firewall), fan it out to several destinations, retry on failure, and transform it in flight into whatever shape the destination expects. Build that message visually with the Slack/Discord/Teams formatter.

Examples

Step-by-step tutorials for the common destinations:

Email → Slack — post inbound email into a Slack channel
Email → Discord — route email to a Discord channel
Email → Microsoft Teams — post a Teams card per email
Email → Google Sheets — append a row per email
Email → Airtable — create an Airtable record
Email → Notion — create a page in a Notion database
Email → your API — POST email to your own endpoint
Email → a database — insert every email into your DB

Get started

Create an email input on a bucket, or read the email docs. It works on the free tier — same as any other Webhook Relay input.

Tunnels

Webhooks

User Management