ingestlayer/recipes

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

sourcesdk.eventTypeScript SDK
matchsubscription.created

02pipeline · 2 steps

  • 01ENRenrich.entitycustomer → company · seats · owner
  • 02CTLfilter.matchannual or scale-plan only

03destinations · 1

  • totelegramTelegram
    chat@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.

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 Telegram

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

  1. 01

    connect a bot

    Create a bot with @BotFather and paste its token. We register the webhook and verify it in-region.

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

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

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 pipelineor read the quickstart →

new subscriptions, routed elsewhere

more, into Telegram