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 Webhook

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

towebhook.outWebhook
urlhttps://api.acme.com/hooks

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 Webhook

POST the processed event as JSON to any HTTPS endpoint you control.

01
set the URL
Any HTTPS endpoint. The processed event is delivered as a JSON body on POST.
02
choose auth
None, a bearer token, or HMAC signing. Signed requests carry an X-Ingestlayer-Signature header you verify with your shared secret.
03
confirm receipt
Return a 2xx within the timeout. Non-2xx responses trigger retries with exponential backoff before the delivery dead-letters.

in webhookdelivered

POST /hooks HTTP/1.1
Host: api.acme.com
Content-Type: application/json
X-Ingestlayer-Signature: t=1717000000,v1=9f86d08…

{
  "type": "user.signed_up",
  "payload": { "email": "ada@acme.com", "plan": "pro" }
}

notes

Endpoints must respond within 10 seconds; slower responses are treated as failures and retried.
Retries use exponential backoff for several attempts before dead-lettering — make your handler idempotent.
Verify the HMAC signature before trusting a payload; the raw body is signed, so compute the digest before JSON parsing.

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 →