Ingest Inbound email events

ingestlayer mints a unique, opaque inbound address for the source. Forward the mail you want ingested to it, and every message is parsed into an event — sender, subject, body, and attachment metadata. Classify, enrich, and redact in flight first — then fan out to any destination, with retries and a dead-letter queue behind every delivery.

how events arrive

1. 01

   mint an inbound address

   Add an inbound-email source; ingestlayer generates a unique, opaque address (an in_… local-part) on its inbound domain. Nobody else can claim it, and there's no DNS or MX record to configure.

2. 02

   forward your mail to it

   Send or forward the messages you want ingested to that address — a forwarding rule, an alias, or a BCC. Only addresses you mint here accept inbound; everything else arriving at the domain is dropped.

3. 03

   optionally restrict senders

   Set a from-domain allowlist so only mail from domains you trust becomes an event; everything else is dropped at the edge before it reaches a pipeline.

{
  "type":    "email.received",
  "from":    "ada@acme.com",
  "to":      "in_7g3k9d2a@inbound.ingestlayer.com",
  "subject": "Demo request — Acme",
  "text":    "Hi, we'd love a demo for a team of 40…",
  "attachments": [
    { "filename": "brief.pdf", "content_type": "application/pdf" }
  ],
  "body_status": "fetched"
}

notes

• —Mail is matched on the exact generated recipient address, case-insensitively. Only addresses you mint here accept inbound; anything else at the domain is dropped.
• —The body is fetched best-effort just after the message arrives, so the event carries a body_status field (fetched, failed, or skipped) — a pipeline can branch on it when the body wasn't available.
• —The event carries attachment metadata — filename and content type — not the bytes; the files themselves aren't routed through the pipeline.

route Inbound email anywhere

• Inbound email → SlackSlack
• Inbound email → DiscordDiscord
• Inbound email → TelegramTelegram
• Inbound email → EmailEmail
• Inbound email → WebhookWebhook
• Inbound email → PostgresPostgres
• Inbound email → NotionNotion