ingestlayer/recipes

Catch churn-risk signals in Discord

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

  • todiscordDiscord
    channel#ops

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 Discord

Send rich embeds to a channel via a connected bot or a channel webhook.

  1. 01

    connect the bot

    Add the ingestlayer bot to your server, or paste a channel webhook URL. Either credential is held in-region.

  2. 02

    choose the channel

    Select the target channel from the picker. Each connected channel is one reusable destination row.

  3. 03

    shape the embed

    The default embed carries the event name as its title and the payload as name/value fields; override with $event.* references.

in discorddelivered
┌─ #ops ─────────────────────────────────┐
│ ▎ payment.failed                        │
│ ▎ customer   acme-inc                   │
│ ▎ amount     €240.00                    │
│ ▎ reason     insufficient_funds         │
│ ▎ attempt    2                          │
└─────────────────────────────────────────┘

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 Discord