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 Email

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

toemail.outEmail
toalerts@acme.com

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 Email

Send a transactional email to one or more recipients, addressable from event fields.

01
set the recipient
Enter a fixed address, or reference an event field like $event.payload.email to route per event.
02
write subject and body
Both accept $event.* templates. The body renders as plain text with an optional summary table of the payload.
03
confirm the sender
Mail goes out from mail@notify.ingestlayer.com with SPF and DKIM aligned. Set a reply-to if you want responses to reach you.

in emaildelivered

From:    mail@notify.ingestlayer.com
To:      alerts@acme.com
Subject: Payment failed — acme-inc (€240.00)

A charge failed for acme-inc.
  amount   €240.00
  reason   insufficient_funds
  attempt  2

notes

Outbound email is metered against a monthly quota that scales with your plan; over-quota sends are deferred, not dropped.
Sending from a fixed ingestlayer domain keeps deliverability high, but the From address is not your own domain.
Recipient addresses pulled from event fields are validated at send time; a malformed address dead-letters that delivery.

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 →