ingestlayer/recipes

Catch churn-risk signals in Slack

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

  • toslackSlack
    channel#alerts

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 Slack

Post to any channel in your workspace. Connect once with OAuth, pick the channel per pipeline.

  1. 01

    connect your workspace

    Authorize the ingestlayer Slack app over OAuth from the destinations page. We hold only a channel-scoped bot token, in-region, in the same KMS as your other credentials.

  2. 02

    pick a channel

    Choose any public channel, or invite the bot to a private one. The channel is set per pipeline, so different events can land in different places.

  3. 03

    map the message

    Reference event fields with $event.* in the message template. The default renders a titled block with the event name and its key fields.

in slackdelivered
┌─ #alerts ──────────────────────────────┐
│  ingestlayer  APP                       │
│  user.signed_up                         │
│  email   ada@acme.com                   │
│  plan    pro                            │
│  source  marketing-site                 │
└─────────────────────────────────────────┘

notes

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

churn-risk signals, routed elsewhere

more, into Slack