ingestlayer/recipes

Monitor usage-limit hits in Slack

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

  • toslackSlack
    channel#alerts

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 Slack

Post to any channel in your workspace. Connect once with OAuth, pick the channel per pipeline.

  1. 01

    connect your workspace

    Authorize the ingestlayer Slack app over OAuth from the destinations page. We hold only a channel-scoped bot token, in-region, in the same KMS as your other credentials.

  2. 02

    pick a channel

    Choose any public channel, or invite the bot to a private one. The channel is set per pipeline, so different events can land in different places.

  3. 03

    map the message

    Reference event fields with $event.* in the message template. The default renders a titled block with the event name and its key fields.

in slackdelivered
┌─ #alerts ──────────────────────────────┐
│  ingestlayer  APP                       │
│  user.signed_up                         │
│  email   ada@acme.com                   │
│  plan    pro                            │
│  source  marketing-site                 │
└─────────────────────────────────────────┘

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 Slack