Can I tune how sensitive the alert is?

Adjust the score threshold in the filter. Raise it for only the clearest risks, lower it to catch more early.

enrich.entity attaches the CSM and renewal date, so the warning reaches the person who can actually save the account.

Can I combine several signals?

Emit each signal as it happens and dedupe by customer in a window, so one at-risk account is one alert, not three.

Catch churn-risk signals in Notion

Turn the small signals — a downgrade, a usage drop, a support spike — into one scored alert that reaches the account owner while there's still time to act.

01source

sourcesdk.eventTypeScript SDK

matchchurn.signal

02pipeline · 2 steps

01ENRenrich.entitycustomer → CSM · renewal · MRR
02CTLfilter.matchscore ≥ 0.7 only

03destinations · 1

tonotion.dbNotion
databaseSignups

the event

You emit churn.signal 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.

customer_idstring
signalstringdowngrade | usage-drop | support-spike
scorenumber0–1 risk
mrrnumberminor units at risk

emit it

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

emit churn.signal

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

await ingest("churn.signal", {
  customer_id: account.id,
  signal:      "usage-drop",
  score:       risk,
  mrr:         account.mrr,
});

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.

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

Notion grants access page by page: the integration only sees databases and pages you explicitly share during authorization. Add the target there, or the delivery dead-letters as object_not_found.
Each column is coerced to its Notion type — number, date, select, checkbox, URL, and so on. Properties an integration can't write (people, relations, files, formulas, rollups) are skipped rather than guessed.
Title and rich-text values cap at 2000 characters per block and are chunked beyond that; a single page append tops out at 100 blocks.
Tokens don't expire, but revoking the integration inside Notion flips the destination to an error state — reconnect from the destinations page to resume delivery.

questions

Can I tune how sensitive the alert is?: Adjust the score threshold in the filter. Raise it for only the clearest risks, lower it to catch more early.
Who gets the alert?: enrich.entity attaches the CSM and renewal date, so the warning reaches the person who can actually save the account.
Can I combine several signals?: Emit each signal as it happens and dedupe by customer in a window, so one at-risk account is one alert, not three.

build this pipeline or read the quickstart →