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 Email

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

toemail.outEmail
toalerts@acme.com

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 Email

Send a transactional email to one or more recipients, addressable from event fields.

01
set the recipient
Enter a fixed address, or reference an event field like $event.payload.email to route per event.
02
write subject and body
Both accept $event.* templates. The body renders as plain text with an optional summary table of the payload.
03
confirm the sender
Mail goes out from mail@notify.ingestlayer.com with SPF and DKIM aligned. Set a reply-to if you want responses to reach you.

in emaildelivered

From:    mail@notify.ingestlayer.com
To:      alerts@acme.com
Subject: Payment failed — acme-inc (€240.00)

A charge failed for acme-inc.
  amount   €240.00
  reason   insufficient_funds
  attempt  2

notes

Outbound email is metered against a monthly quota that scales with your plan; over-quota sends are deferred, not dropped.
Sending from a fixed ingestlayer domain keeps deliverability high, but the From address is not your own domain.
Recipient addresses pulled from event fields are validated at send time; a malformed address dead-letters that delivery.

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 →