Won't this be far too noisy?

Filter to the handful of features that actually predict expansion; everything else streams to the warehouse without an alert.

Can I spot free users hitting paid features?

The plan field rides along — branch on it to flag free-plan users leaning on paid surfaces, a clean upsell trigger.

How do I roll this up per account?

enrich.entity attaches the account id so usage aggregates cleanly in Postgres by company, not just by user.

ingestlayer/recipes/v0.4

Track feature usage in Email

Watch the features that signal expansion — exports, API calls, integrations — and route the moments that hint a customer is ready for more.

01source

sourcesdk.eventTypeScript SDK

matchfeature.used

02pipeline · 2 steps

01CTLfilter.matchfeature in {export, api, webhook}
02ENRenrich.entityuser → account · plan · owner

03destinations · 1

toemail.outEmail
toalerts@acme.com

the event

You emit feature.used 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.

user_idstring
featurestringfeature key
countnumberuses in window
planstring

emit it

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

emit feature.used

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

await ingest("feature.used", {
  user_id: ctx.user.id,
  feature: "csv.export",
  count:   1,
  plan:    ctx.user.plan,
});

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

Won't this be far too noisy?: Filter to the handful of features that actually predict expansion; everything else streams to the warehouse without an alert.
Can I spot free users hitting paid features?: The plan field rides along — branch on it to flag free-plan users leaning on paid surfaces, a clean upsell trigger.
How do I roll this up per account?: enrich.entity attaches the account id so usage aggregates cleanly in Postgres by company, not just by user.

build this pipeline or read the quickstart →