ingestlayer/recipes

Monitor usage-limit hits in Discord

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

  • todiscordDiscord
    channel#ops

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

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

usage-limit hits, routed elsewhere

more, into Discord