How do I avoid alert spam on retries?

Filter on the attempt field, or set a dedupe window so repeated failures for the same charge collapse into one alert.

Can I only alert on high-value customers?

Yes. enrich.entity pulls MRR onto the event, then a filter keeps only the ones above your threshold.

Where does the decline reason come from?

Whatever you put in the reason field — usually the processor's decline code. ingestlayer passes it through untouched.

Monitor failed payments in Notion

Catch failed charges the second they happen, with the customer, amount, and decline reason attached, so a billing problem becomes a message instead of a churn surprise.

01source

sourcesdk.eventTypeScript SDK

matchpayment.failed

02pipeline · 2 steps

01CTLfilter.matchamount ≥ 50.00 only
02ENRenrich.entitycustomer → plan · MRR · CSM

03destinations · 1

tonotion.dbNotion
databaseSignups

the event

You emit payment.failed 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
emailstring
amountnumberminor units
currencystringISO 4217
reasonstringprocessor decline code
attemptnumber

emit it

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

emit payment.failed

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

await ingest("payment.failed", {
  customer_id: charge.customer,
  email:       charge.receipt_email,
  amount:      charge.amount,
  currency:    charge.currency,
  reason:      charge.failure_code,
  attempt:     charge.attempt,
}, {
  idempotencyKey: `${charge.id}:${charge.attempt}`,
});

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 alert spam on retries?: Filter on the attempt field, or set a dedupe window so repeated failures for the same charge collapse into one alert.
Can I only alert on high-value customers?: Yes. enrich.entity pulls MRR onto the event, then a filter keeps only the ones above your threshold.
Where does the decline reason come from?: Whatever you put in the reason field — usually the processor's decline code. ingestlayer passes it through untouched.

build this pipeline or read the quickstart →