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.

ingestlayer/recipes/v0.4

Monitor usage-limit hits in Postgres

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

towarehouse.pgPostgres
tableevents.signups

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 Postgres

Insert each event as a row into a table in your own Postgres.

01
add the connection
Paste a Postgres connection string. Connections originate from our EU region — allowlist those egress IPs on your database.
02
point at a table
Name the target table. Top-level event fields map to columns, and the full payload is also available as a jsonb column.
03
map columns
Match event fields to columns with $event.* references, or accept the default mapping into a typed events table.

in postgresdelivered

INSERT INTO events.signups
  (user_id, email, plan, source, payload)
VALUES
  ('u_018f', 'ada@acme.com', 'pro',
   'marketing-site', '{ … }'::jsonb);

notes

The target table must already exist with compatible column types; ingestlayer never runs DDL on your database.
Connections come from fixed EU egress IPs — add them to your firewall, or inserts will time out.
Use a jsonb column for the full payload when your event shape changes often, so a new field never breaks the insert.

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