Won't this be far too noisy?

Filter to the handful of features that actually predict expansion; everything else streams to the warehouse without an alert.

Can I spot free users hitting paid features?

The plan field rides along — branch on it to flag free-plan users leaning on paid surfaces, a clean upsell trigger.

How do I roll this up per account?

enrich.entity attaches the account id so usage aggregates cleanly in Postgres by company, not just by user.

ingestlayer/recipes/v0.4

Track feature usage in Notion

Watch the features that signal expansion — exports, API calls, integrations — and route the moments that hint a customer is ready for more.

01source

sourcesdk.eventTypeScript SDK

matchfeature.used

02pipeline · 2 steps

01CTLfilter.matchfeature in {export, api, webhook}
02ENRenrich.entityuser → account · plan · owner

03destinations · 1

tonotion.dbNotion
databaseSignups

the event

You emit feature.used 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.

user_idstring
featurestringfeature key
countnumberuses in window
planstring

emit it

From your code with the TypeScript SDK — or any language over the REST endpoint and signed webhook ingress.

emit feature.used

import { ingest } from "@ingestlayer/sdk";

await ingest("feature.used", {
  user_id: ctx.user.id,
  feature: "csv.export",
  count:   1,
  plan:    ctx.user.plan,
});

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

Won't this be far too noisy?: Filter to the handful of features that actually predict expansion; everything else streams to the warehouse without an alert.
Can I spot free users hitting paid features?: The plan field rides along — branch on it to flag free-plan users leaning on paid surfaces, a clean upsell trigger.
How do I roll this up per account?: enrich.entity attaches the account id so usage aggregates cleanly in Postgres by company, not just by user.

build this pipeline or read the quickstart →