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 Email

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

toemail.outEmail
toalerts@acme.com

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 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

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 →