Can I celebrate only the big ones?

Filter on mrr or plan so a #wins channel sees the deals worth celebrating, while everything still streams to your warehouse.

Who owns the account?

enrich.entity attaches the account owner and seat count in flight, so the alert names a person, not just an id.

How is this different from a successful payment?

A subscription.created fires once when the plan starts; payment.succeeded fires every billing cycle. Track both for different signals.

ingestlayer/recipes/v0.4

Track new subscriptions in Postgres

Know the second a customer starts paying — which plan, how much, monthly or annual — so revenue moments reach the team while they still feel like wins.

01source

sourcesdk.eventTypeScript SDK

matchsubscription.created

02pipeline · 2 steps

01ENRenrich.entitycustomer → company · seats · owner
02CTLfilter.matchannual or scale-plan only

03destinations · 1

towarehouse.pgPostgres
tableevents.signups

the event

You emit subscription.created 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
planstringpro | scale
mrrnumberminor units
intervalstringmonth | year
trialbooleanconverted from trial

emit it

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

emit subscription.created

import { ingest } from "@ingestlayer/sdk";

await ingest("subscription.created", {
  customer_id: sub.customer,
  plan:        sub.plan.nickname,
  mrr:         sub.plan.amount,
  interval:    sub.plan.interval,
  trial:       sub.trial_end != null,
}, {
  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

Can I celebrate only the big ones?: Filter on mrr or plan so a #wins channel sees the deals worth celebrating, while everything still streams to your warehouse.
Who owns the account?: enrich.entity attaches the account owner and seat count in flight, so the alert names a person, not just an id.
How is this different from a successful payment?: A subscription.created fires once when the plan starts; payment.succeeded fires every billing cycle. Track both for different signals.

build this pipeline or read the quickstart →