Can I flag unexpected file types?

Branch on the mime field so an executable in a documents bucket reaches the channel while ordinary uploads stay quiet.

How do I watch storage growth?

Land every upload in Postgres with size_bytes and bucket, and aggregate by bucket over time.

Does the file itself pass through?

No — only the metadata you send. The bytes stay in your storage; ingestlayer routes the event, not the object.

Track file uploads in Notion

Keep an eye on what's being uploaded — large files, unusual types, heavy buckets — and route the ones worth a second look.

01source

sourcesdk.eventTypeScript SDK

matchfile.uploaded

02pipeline · 1 steps

01CTLfilter.matchsize ≥ 100 MB only

03destinations · 1

tonotion.dbNotion
databaseSignups

the event

You emit file.uploaded 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
file_idstring
size_bytesnumber
mimestringcontent type
bucketstring

emit it

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

emit file.uploaded

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

await ingest("file.uploaded", {
  user_id:    ctx.user.id,
  file_id:    object.key,
  size_bytes: object.size,
  mime:       object.contentType,
  bucket:     object.bucket,
}, {
  idempotencyKey: object.key,
});

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

Can I flag unexpected file types?: Branch on the mime field so an executable in a documents bucket reaches the channel while ordinary uploads stay quiet.
How do I watch storage growth?: Land every upload in Postgres with size_bytes and bucket, and aggregate by bucket over time.
Does the file itself pass through?: No — only the metadata you send. The bytes stay in your storage; ingestlayer routes the event, not the object.

build this pipeline or read the quickstart →