ingestlayer/recipes

Track canceled subscriptions in Discord

Catch every cancellation with the plan, the tenure, and the reason attached — so the team can reach out while the relationship is still warm.

01source

sourcesdk.eventTypeScript SDK
matchsubscription.canceled

02pipeline · 2 steps

  • 01ENRclassifyreason → price | missing-feature | switched
  • 02ENRenrich.entitycustomer → MRR · CSM

03destinations · 1

  • todiscordDiscord
    channel#ops

the event

You emit subscription.canceled 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
  • planstring
  • mrrnumberminor units lost
  • reasonstringfree text, optional
  • tenure_daysnumber

emit it

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

emit subscription.canceled
import { ingest } from "@ingestlayer/sdk";

await ingest("subscription.canceled", {
  customer_id: sub.customer,
  plan:        sub.plan.nickname,
  mrr:         sub.plan.amount,
  reason:      survey.reason,
  tenure_days: daysSince(sub.created),
}, {
  idempotencyKey: sub.id,
});

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

The reason is free text — can I bucket it?
Yes. classify maps the free-text reason to a typed label your pipeline branches on, so price churn and product churn route to different people.
Can I alert only above a revenue threshold?
enrich.entity attaches MRR; a filter then keeps only the cancellations that actually move the number.
Where do I keep churn history?
Send every cancellation to Postgres in parallel with the alert, so the churn table is complete regardless of who got pinged.
build this pipelineor read the quickstart →

canceled subscriptions, routed elsewhere

more, into Discord