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 Telegram

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

totelegramTelegram
chat@oncall

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 Telegram

Message a person, group, or channel through a connected bot.

01
connect a bot
Create a bot with @BotFather and paste its token. We register the webhook and verify it in-region.
02
start a chat
Send /start to the bot from the target chat — or add it to the group/channel — then pick the chat from the list.
03
format the text
Messages use MarkdownV2; the default template bolds the event name and lists fields. Reserved characters in field values are escaped for you.

in telegramdelivered

oncall
*support.ticket.created*
ticket    T-4821
subject   API returning 500s
tier      enterprise
urgency   critical

notes

Telegram caps a bot at roughly 30 messages per second overall, and one per second to a single chat.
The bot must be added to a group — and promoted to admin for a channel — before it can post.
MarkdownV2 requires escaping characters like _ * [ ] ( ); ingestlayer escapes field values, but custom templates are your responsibility.

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 →