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 Webhook

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

towebhook.outWebhook
urlhttps://api.acme.com/hooks

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 Webhook

POST the processed event as JSON to any HTTPS endpoint you control.

01
set the URL
Any HTTPS endpoint. The processed event is delivered as a JSON body on POST.
02
choose auth
None, a bearer token, or HMAC signing. Signed requests carry an X-Ingestlayer-Signature header you verify with your shared secret.
03
confirm receipt
Return a 2xx within the timeout. Non-2xx responses trigger retries with exponential backoff before the delivery dead-letters.

in webhookdelivered

POST /hooks HTTP/1.1
Host: api.acme.com
Content-Type: application/json
X-Ingestlayer-Signature: t=1717000000,v1=9f86d08…

{
  "type": "user.signed_up",
  "payload": { "email": "ada@acme.com", "plan": "pro" }
}

notes

Endpoints must respond within 10 seconds; slower responses are treated as failures and retried.
Retries use exponential backoff for several attempts before dead-lettering — make your handler idempotent.
Verify the HMAC signature before trusting a payload; the raw body is signed, so compute the digest before JSON parsing.

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 →