ingestlayer/recipes

Track new subscriptions in Notion

Know the second a customer starts paying — which plan, how much, monthly or annual — so revenue moments reach the team while they still feel like wins.

01source

sourcesdk.eventTypeScript SDK
matchsubscription.created

02pipeline · 2 steps

  • 01ENRenrich.entitycustomer → company · seats · owner
  • 02CTLfilter.matchannual or scale-plan only

03destinations · 1

  • tonotion.dbNotion
    databaseSignups

the event

You emit subscription.created 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
  • planstringpro | scale
  • mrrnumberminor units
  • intervalstringmonth | year
  • trialbooleanconverted from trial

emit it

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

emit subscription.created
import { ingest } from "@ingestlayer/sdk";

await ingest("subscription.created", {
  customer_id: sub.customer,
  plan:        sub.plan.nickname,
  mrr:         sub.plan.amount,
  interval:    sub.plan.interval,
  trial:       sub.trial_end != null,
}, {
  idempotencyKey: sub.id,
});

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.

  1. 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.

  2. 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.

  3. 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

questions

Can I celebrate only the big ones?
Filter on mrr or plan so a #wins channel sees the deals worth celebrating, while everything still streams to your warehouse.
Who owns the account?
enrich.entity attaches the account owner and seat count in flight, so the alert names a person, not just an id.
How is this different from a successful payment?
A subscription.created fires once when the plan starts; payment.succeeded fires every billing cycle. Track both for different signals.
build this pipelineor read the quickstart →

new subscriptions, routed elsewhere

more, into Notion