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 Webhook

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

towebhook.outWebhook
urlhttps://api.acme.com/hooks

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 Webhook

POST the processed event as JSON to any HTTPS endpoint you control.

01
set the URL
Any HTTPS endpoint. The processed event is delivered as a JSON body on POST.
02
choose auth
None, a bearer token, or HMAC signing. Signed requests carry an X-Ingestlayer-Signature header you verify with your shared secret.
03
confirm receipt
Return a 2xx within the timeout. Non-2xx responses trigger retries with exponential backoff before the delivery dead-letters.

in webhookdelivered

POST /hooks HTTP/1.1
Host: api.acme.com
Content-Type: application/json
X-Ingestlayer-Signature: t=1717000000,v1=9f86d08…

{
  "type": "user.signed_up",
  "payload": { "email": "ada@acme.com", "plan": "pro" }
}

notes

Endpoints must respond within 10 seconds; slower responses are treated as failures and retried.
Retries use exponential backoff for several attempts before dead-lettering — make your handler idempotent.
Verify the HMAC signature before trusting a payload; the raw body is signed, so compute the digest before JSON parsing.

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 →