Can I keep spam out of the channel?

classify labels the intent and a filter drops spam before it's ever posted — no rules to maintain by hand.

Different forms, different places?

Branch on form_id so a demo request reaches sales and a bug report reaches support.

Is PII safe in transit?

redact.pii masks sensitive fields per destination, so the chat copy is clean while the warehouse keeps the full record.

Track form submissions in Notion

Route contact, demo, and feedback forms the instant they're submitted — classified by intent and stripped of PII before they reach a channel.

01source

sourcesdk.eventTypeScript SDK

matchform.submitted

02pipeline · 3 steps

01ENRclassifyintent → demo | support | spam
02CTLfilter.matchdrop intent = spam
03MUTredact.piimask email + phone per destination

03destinations · 1

tonotion.dbNotion
databaseSignups

the event

You emit form.submitted 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.

form_idstringwhich form
emailstring
fieldsobjectraw form values
pagestringpage URL

emit it

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

emit form.submitted

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

await ingest("form.submitted", {
  form_id: form.id,
  email:   form.values.email,
  fields:  form.values,
  page:    location.pathname,
});

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 keep spam out of the channel?: classify labels the intent and a filter drops spam before it's ever posted — no rules to maintain by hand.
Different forms, different places?: Branch on form_id so a demo request reaches sales and a bug report reaches support.
Is PII safe in transit?: redact.pii masks sensitive fields per destination, so the chat copy is clean while the warehouse keeps the full record.

build this pipeline or read the quickstart →