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 Postgres

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

towarehouse.pgPostgres
tableevents.signups

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 Postgres

Insert each event as a row into a table in your own Postgres.

01
add the connection
Paste a Postgres connection string. Connections originate from our EU region — allowlist those egress IPs on your database.
02
point at a table
Name the target table. Top-level event fields map to columns, and the full payload is also available as a jsonb column.
03
map columns
Match event fields to columns with $event.* references, or accept the default mapping into a typed events table.

in postgresdelivered

INSERT INTO events.signups
  (user_id, email, plan, source, payload)
VALUES
  ('u_018f', 'ada@acme.com', 'pro',
   'marketing-site', '{ … }'::jsonb);

notes

The target table must already exist with compatible column types; ingestlayer never runs DDL on your database.
Connections come from fixed EU egress IPs — add them to your firewall, or inserts will time out.
Use a jsonb column for the full payload when your event shape changes often, so a new field never breaks the insert.

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 →