Can I only hear about problems?

Filter to failures and jobs that overran their expected_ms; healthy runs pass silently to the warehouse for the record.

How do I catch a job that never ran?

Pair this with a scheduled check that emits when an expected cron.finished is missing — absence is the signal there.

Can different jobs alert different teams?

Branch on the job name so a failed billing run reaches finance and a failed deploy reaches engineering.

Monitor cron-job health in Notion

Hear about the scheduled jobs that fail or run long — and only those — so a silent backup or a stalled sync becomes a message, not a surprise.

01source

sourcesdk.eventTypeScript SDK

matchcron.finished

02pipeline · 1 steps

01CTLfilter.matchstatus = failed or ran long

03destinations · 1

tonotion.dbNotion
databaseSignups

the event

You emit cron.finished 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.

jobstringjob name
statusstringok | failed
duration_msnumber
expected_msnumbertypical runtime
exit_codenumber

emit it

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

emit cron.finished

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

await ingest("cron.finished", {
  job:         "nightly-backup",
  status:      ok ? "ok" : "failed",
  duration_ms: Date.now() - startedAt,
  expected_ms: 120000,
  exit_code:   code,
});

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 only hear about problems?: Filter to failures and jobs that overran their expected_ms; healthy runs pass silently to the warehouse for the record.
How do I catch a job that never ran?: Pair this with a scheduled check that emits when an expected cron.finished is missing — absence is the signal there.
Can different jobs alert different teams?: Branch on the job name so a failed billing run reaches finance and a failed deploy reaches engineering.

build this pipeline or read the quickstart →