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 Notion

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

tonotion.dbNotion
databaseSignups

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 Notion

Append events as rows to a Notion database, or content to a page. Connect once with OAuth, pick the target per pipeline.

01
connect your workspace
Authorize the ingestlayer Notion integration over OAuth from the destinations page, then choose which databases and pages it may touch. We hold only that workspace's access token, in-region, in the same KMS as your other credentials.
02
pick a target
Per pipeline, choose a database to append a typed row to, or a page to append content to. The picker lists exactly what you shared with the integration during authorization — nothing else.
03
map the columns
For a database, match event fields to Notion properties — automatically by column name, or per-column with $event.* templates. The title column falls back to the event name, so a row is never blank. For a page, the rendered body is appended as blocks.

in notiondelivered

┌─ Signups · database ───────────────────┐
│  Name        ada@acme.com               │
│  Plan        ● pro                       │
│  Source      marketing-site             │
│  Signed up   2026-06-03                  │
└─────────────────────────────────────────┘

notes

Notion grants access page by page: the integration only sees databases and pages you explicitly share during authorization. Add the target there, or the delivery dead-letters as object_not_found.
Each column is coerced to its Notion type — number, date, select, checkbox, URL, and so on. Properties an integration can't write (people, relations, files, formulas, rollups) are skipped rather than guessed.
Title and rich-text values cap at 2000 characters per block and are chunked beyond that; a single page append tops out at 100 blocks.
Tokens don't expire, but revoking the integration inside Notion flips the destination to an error state — reconnect from the destinations page to resume delivery.

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 →