ingestlayer/recipes

Track new subscriptions in Discord

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

  • todiscordDiscord
    channel#ops

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 Discord

Send rich embeds to a channel via a connected bot or a channel webhook.

  1. 01

    connect the bot

    Add the ingestlayer bot to your server, or paste a channel webhook URL. Either credential is held in-region.

  2. 02

    choose the channel

    Select the target channel from the picker. Each connected channel is one reusable destination row.

  3. 03

    shape the embed

    The default embed carries the event name as its title and the payload as name/value fields; override with $event.* references.

in discorddelivered
┌─ #ops ─────────────────────────────────┐
│ ▎ payment.failed                        │
│ ▎ customer   acme-inc                   │
│ ▎ amount     €240.00                    │
│ ▎ reason     insufficient_funds         │
│ ▎ attempt    2                          │
└─────────────────────────────────────────┘

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 Discord