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 Postgres

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

towarehouse.pgPostgres
tableevents.signups

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 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 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 →