What model does the classify step use?

Yours. You bring the model, prompt, and label schema; ingestlayer runs it in flight and returns a typed label the pipeline branches on.

Does every ticket hit the model?

Only if you want it to. classify is per-event and cached by payload hash, so identical tickets reuse one call.

Can the same ticket go to two places?

Yes — fan out to several destinations with different when conditions, e.g. critical to chat and everything to Postgres.

ingestlayer/recipes/v0.4

Route support escalations in Postgres

Classify inbound tickets by urgency in flight and route only the ones that need a human now — so the on-call channel sees escalations, not every ticket.

01source

sourcesdk.eventTypeScript SDK

matchsupport.ticket.created

02pipeline · 3 steps

01ENRclassifyurgency: low | high | critical
02CTLfilter.matchurgency = critical only
03MUTredact.piistrip PII from body before posting

03destinations · 1

towarehouse.pgPostgres
tableevents.signups

the event

You emit support.ticket.created 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.

ticket_idstring
subjectstring
bodystringfree text
customer_tierstringfree | pro | enterprise
channelstringemail | chat | form

emit it

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

emit support.ticket.created

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

await ingest("support.ticket.created", {
  ticket_id:     ticket.id,
  subject:       ticket.subject,
  body:          ticket.body,
  customer_tier: ticket.account.tier,
  channel:       ticket.channel,
}, {
  idempotencyKey: ticket.id,
});

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

What model does the classify step use?: Yours. You bring the model, prompt, and label schema; ingestlayer runs it in flight and returns a typed label the pipeline branches on.
Does every ticket hit the model?: Only if you want it to. classify is per-event and cached by payload hash, so identical tickets reuse one call.
Can the same ticket go to two places?: Yes — fan out to several destinations with different when conditions, e.g. critical to chat and everything to Postgres.

build this pipeline or read the quickstart →