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 Notion

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

tonotion.dbNotion
databaseSignups

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 Notion

Append events as rows to a Notion database, or content to a page. Connect once with OAuth, pick the target per pipeline.

01
connect your workspace
Authorize the ingestlayer Notion integration over OAuth from the destinations page, then choose which databases and pages it may touch. We hold only that workspace's access token, in-region, in the same KMS as your other credentials.
02
pick a target
Per pipeline, choose a database to append a typed row to, or a page to append content to. The picker lists exactly what you shared with the integration during authorization — nothing else.
03
map the columns
For a database, match event fields to Notion properties — automatically by column name, or per-column with $event.* templates. The title column falls back to the event name, so a row is never blank. For a page, the rendered body is appended as blocks.

in notiondelivered

┌─ Signups · database ───────────────────┐
│  Name        ada@acme.com               │
│  Plan        ● pro                       │
│  Source      marketing-site             │
│  Signed up   2026-06-03                  │
└─────────────────────────────────────────┘

notes

Notion grants access page by page: the integration only sees databases and pages you explicitly share during authorization. Add the target there, or the delivery dead-letters as object_not_found.
Each column is coerced to its Notion type — number, date, select, checkbox, URL, and so on. Properties an integration can't write (people, relations, files, formulas, rollups) are skipped rather than guessed.
Title and rich-text values cap at 2000 characters per block and are chunked beyond that; a single page append tops out at 100 blocks.
Tokens don't expire, but revoking the integration inside Notion flips the destination to an error state — reconnect from the destinations page to resume 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 →