How do I avoid firing this every request?

Send it once per period with a period-scoped idempotencyKey, so a customer over the line all month is one alert, not thousands.

Can it route straight to the account owner?

enrich.entity attaches the CSM, so the upsell nudge reaches the person who owns the relationship.

Can I treat hard and soft limits differently?

Branch on the metric and the used/limit ratio to separate a gentle nudge from a service-blocking limit.

ingestlayer/recipes/v0.4

Monitor usage-limit hits in Telegram

Know the moment a customer bumps a plan limit — the clearest upsell signal there is — with their plan and account owner already attached.

01source

sourcesdk.eventTypeScript SDK

matchusage.limit_reached

02pipeline · 1 steps

01ENRenrich.entitycustomer → MRR · CSM · renewal

03destinations · 1

totelegramTelegram
chat@oncall

the event

You emit usage.limit_reached 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
metricstringseats | api-calls | storage
limitnumber
usednumber
planstring

emit it

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

emit usage.limit_reached

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

await ingest("usage.limit_reached", {
  customer_id: account.id,
  metric:      "api-calls",
  limit:       account.plan.apiLimit,
  used:        account.usage.apiCalls,
  plan:        account.plan.name,
}, {
  idempotencyKey: `${account.id}:api-calls:${period}`,
});

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

How do I avoid firing this every request?: Send it once per period with a period-scoped idempotencyKey, so a customer over the line all month is one alert, not thousands.
Can it route straight to the account owner?: enrich.entity attaches the CSM, so the upsell nudge reaches the person who owns the relationship.
Can I treat hard and soft limits differently?: Branch on the metric and the used/limit ratio to separate a gentle nudge from a service-blocking limit.

build this pipeline or read the quickstart →