ingestlayer/recipes

Route support escalations in Notion

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

  • tonotion.dbNotion
    databaseSignups

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 Notion

Append events as rows to a Notion database, or content to a page. Connect once with OAuth, pick the target per pipeline.

  1. 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.

  2. 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.

  3. 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

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 pipelineor read the quickstart →

support escalations, routed elsewhere

more, into Notion