Track new subscriptions in Telegram
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
02pipeline · 2 steps
- 01ENRenrich.entitycustomer → company · seats · owner
- 02CTLfilter.matchannual or scale-plan only
03destinations · 1
- totelegramTelegramchat@oncall
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.
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 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.
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
- 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.
new subscriptions, routed elsewhere
- Track new subscriptions in SlackSlack
- Track new subscriptions in DiscordDiscord
- Track new subscriptions in EmailEmail
- Track new subscriptions in WebhookWebhook
- Track new subscriptions in PostgresPostgres
- Track new subscriptions in NotionNotion
more, into Telegram
- Track user signups in Telegramtrack
- Monitor failed payments in Telegrammonitor
- Route support escalations in Telegramalert
- Track waitlist signups in Telegramtrack
- Track canceled subscriptions in Telegramtrack
- Track successful payments in Telegramtrack
- Track trial conversions in Telegramtrack
- Track form submissions in Telegramtrack
- Track feature usage in Telegramtrack
- Track file uploads in Telegramtrack
- Monitor failed logins in Telegrammonitor
- Monitor usage-limit hits in Telegrammonitor
- Monitor error spikes in Telegrammonitor
- Monitor cron-job health in Telegrammonitor
- Monitor CI/CD build status in Telegrammonitor
- Flag high-value leads in Telegramalert
- Catch churn-risk signals in Telegramalert
- everything you can pipe to Telegramhub