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.

ingestlayer/recipes/v0.4

Track canceled subscriptions in Slack

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

toslackSlack
channel#alerts

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 Slack

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

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

Slack rate-limits to roughly one message per second per channel; bursts are queued and retried, never dropped.
The bot must be a member of a private channel before it can post there — invite it explicitly.
Block Kit caps a message at 50 blocks and 3000 characters per text field; oversized events are truncated with a link to the full payload.

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