Can I treat work emails differently?

Yes. enrich.person resolves the email to a company, then a filter or a branch routes business signups somewhere louder than personal ones.

How do I stop duplicate entries?

Pass the email as idempotencyKey; the gate enforces uniqueness, so a double-submit counts once and keeps positions honest.

Can I keep a full copy of the list?

Fan out: send the alert to a chat channel and the same event to Postgres, so the canonical list lives in your own database.

ingestlayer/recipes/v0.4

Track waitlist signups in Email

See who joins the waitlist as it happens — with their position and where they came from — so launch outreach starts the day they sign up, not after the next export.

01source

sourcesdk.eventTypeScript SDK

matchwaitlist.joined

02pipeline · 2 steps

01ENRenrich.personemail → company · role
02CTLfilter.matchskip disposable-email domains

03destinations · 1

toemail.outEmail
toalerts@acme.com

the event

You emit waitlist.joined with this shape. The TypeScript SDK keeps the call type-safe, and the event is stored whole — so every field below is available to the pipeline by name.

emailstring
positionnumberplace in line
referrerstringwhere they came from
created_atstringISO 8601

emit it

From your code with the TypeScript SDK — or any language over the REST endpoint and signed webhook ingress.

emit waitlist.joined

import { ingest } from "@ingestlayer/sdk";

await ingest("waitlist.joined", {
  email:    form.email,
  position: list.length + 1,
  referrer: req.headers.referer,
}, {
  idempotencyKey: form.email,   // one slot per email
});

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

Can I treat work emails differently?: Yes. enrich.person resolves the email to a company, then a filter or a branch routes business signups somewhere louder than personal ones.
How do I stop duplicate entries?: Pass the email as idempotencyKey; the gate enforces uniqueness, so a double-submit counts once and keeps positions honest.
Can I keep a full copy of the list?: Fan out: send the alert to a chat channel and the same event to Postgres, so the canonical list lives in your own database.

build this pipeline or read the quickstart →