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 → Email

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

toemail.outEmail
toalerts@acme.com

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 Email

Send a transactional email to one or more recipients, addressable from event fields.

01
set the recipient
Enter a fixed address, or reference an event field like $event.payload.email to route per event.
02
write subject and body
Both accept $event.* templates. The body renders as plain text with an optional summary table of the payload.
03
confirm the sender
Mail goes out from mail@notify.ingestlayer.com with SPF and DKIM aligned. Set a reply-to if you want responses to reach you.

in emaildelivered

From:    mail@notify.ingestlayer.com
To:      alerts@acme.com
Subject: Payment failed — acme-inc (€240.00)

A charge failed for acme-inc.
  amount   €240.00
  reason   insufficient_funds
  attempt  2

notes

Outbound email is metered against a monthly quota that scales with your plan; over-quota sends are deferred, not dropped.
Sending from a fixed ingestlayer domain keeps deliverability high, but the From address is not your own domain.
Recipient addresses pulled from event fields are validated at send time; a malformed address dead-letters that delivery.

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 →