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 Postgres

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

towarehouse.pgPostgres
tableevents.signups

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 Postgres

Insert each event as a row into a table in your own Postgres.

01
add the connection
Paste a Postgres connection string. Connections originate from our EU region — allowlist those egress IPs on your database.
02
point at a table
Name the target table. Top-level event fields map to columns, and the full payload is also available as a jsonb column.
03
map columns
Match event fields to columns with $event.* references, or accept the default mapping into a typed events table.

in postgresdelivered

INSERT INTO events.signups
  (user_id, email, plan, source, payload)
VALUES
  ('u_018f', 'ada@acme.com', 'pro',
   'marketing-site', '{ … }'::jsonb);

notes

The target table must already exist with compatible column types; ingestlayer never runs DDL on your database.
Connections come from fixed EU egress IPs — add them to your firewall, or inserts will time out.
Use a jsonb column for the full payload when your event shape changes often, so a new field never breaks the insert.

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 →