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 Webhook

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

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

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

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 →