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 Telegram

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

totelegramTelegram
chat@oncall

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 Telegram

Message a person, group, or channel through a connected bot.

01
connect a bot
Create a bot with @BotFather and paste its token. We register the webhook and verify it in-region.
02
start a chat
Send /start to the bot from the target chat — or add it to the group/channel — then pick the chat from the list.
03
format the text
Messages use MarkdownV2; the default template bolds the event name and lists fields. Reserved characters in field values are escaped for you.

in telegramdelivered

oncall
*support.ticket.created*
ticket    T-4821
subject   API returning 500s
tier      enterprise
urgency   critical

notes

Telegram caps a bot at roughly 30 messages per second overall, and one per second to a single chat.
The bot must be added to a group — and promoted to admin for a channel — before it can post.
MarkdownV2 requires escaping characters like _ * [ ] ( ); ingestlayer escapes field values, but custom templates are your responsibility.

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 →