Do I have to change my DNS or MX records?

No. ingestlayer generates the inbound address — you just forward mail to it. There's no MX record, domain verification, or DNS change to set up.

How are attachments handled?

The event includes each attachment's filename and content type so you can branch on them, but the bytes aren't routed — keeping large files out of your chat and your warehouse.

Can it triage email before it reaches a channel?

Yes — classify labels the intent (sales, support, spam) and summarize collapses a long thread to a line, so the channel sees a clean, sorted signal instead of a raw forward.

ingestlayer/recipes/v0.4

Inbound email → Discord

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.

01source

sourceemailInbound email

matchemail.received

02pipeline · 3 steps

01ENRclassifyintent → sales | support | spam
02ENRsummarizelong thread → one line
03MUTredact.piimask PII before posting

03destinations · 1

todiscordDiscord
channel#ops

how events arrive

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.
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.
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.

from inbound emaildelivered

{
  "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"
}

route it to Discord

Send rich embeds to a channel via a connected bot or a channel webhook.

01
connect the bot
Add the ingestlayer bot to your server, or paste a channel webhook URL. Either credential is held in-region.
02
choose the channel
Select the target channel from the picker. Each connected channel is one reusable destination row.
03
shape the embed
The default embed carries the event name as its title and the payload as name/value fields; override with $event.* references.

in discorddelivered

┌─ #ops ─────────────────────────────────┐
│ ▎ payment.failed                        │
│ ▎ customer   acme-inc                   │
│ ▎ amount     €240.00                    │
│ ▎ reason     insufficient_funds         │
│ ▎ attempt    2                          │
└─────────────────────────────────────────┘

notes

Channel webhooks are limited to about 30 messages per minute; sustained volume should use the bot connection instead.
An embed allows at most 25 fields and 6000 total characters; larger events are summarized.
Mentions (@everyone, @role) are suppressed by default — opt in per pipeline if you actually want a ping.

questions

Do I have to change my DNS or MX records?: No. ingestlayer generates the inbound address — you just forward mail to it. There's no MX record, domain verification, or DNS change to set up.
How are attachments handled?: The event includes each attachment's filename and content type so you can branch on them, but the bytes aren't routed — keeping large files out of your chat and your warehouse.
Can it triage email before it reaches a channel?: Yes — classify labels the intent (sales, support, spam) and summarize collapses a long thread to a line, so the channel sees a clean, sorted signal instead of a raw forward.

build this pipeline or read the quickstart →