ingestlayer/recipes

Monitor usage-limit hits in Webhook

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

  • towebhook.outWebhook
    urlhttps://api.acme.com/hooks

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 Webhook

POST the processed event as JSON to any HTTPS endpoint you control.

  1. 01

    set the URL

    Any HTTPS endpoint. The processed event is delivered as a JSON body on POST.

  2. 02

    choose auth

    None, a bearer token, or HMAC signing. Signed requests carry an X-Ingestlayer-Signature header you verify with your shared secret.

  3. 03

    confirm receipt

    Return a 2xx within the timeout. Non-2xx responses trigger retries with exponential backoff before the delivery dead-letters.

in webhookdelivered
POST /hooks HTTP/1.1
Host: api.acme.com
Content-Type: application/json
X-Ingestlayer-Signature: t=1717000000,v1=9f86d08…

{
  "type": "user.signed_up",
  "payload": { "email": "ada@acme.com", "plan": "pro" }
}

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 Webhook