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
02pipeline · 2 steps
- 01ENRenrich.entitycustomer → company · seats · owner
- 02CTLfilter.matchannual or scale-plan only
03destinations · 1
- tonotion.dbNotiondatabaseSignups
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.
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.
- 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.
┌─ 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 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.
new subscriptions, routed elsewhere
- Track new subscriptions in SlackSlack
- Track new subscriptions in DiscordDiscord
- Track new subscriptions in TelegramTelegram
- Track new subscriptions in EmailEmail
- Track new subscriptions in WebhookWebhook
- Track new subscriptions in PostgresPostgres
more, into Notion
- Track user signups in Notiontrack
- Monitor failed payments in Notionmonitor
- Route support escalations in Notionalert
- Track waitlist signups in Notiontrack
- Track canceled subscriptions in Notiontrack
- Track successful payments in Notiontrack
- Track trial conversions in Notiontrack
- Track form submissions in Notiontrack
- Track feature usage in Notiontrack
- Track file uploads in Notiontrack
- Monitor failed logins in Notionmonitor
- Monitor usage-limit hits in Notionmonitor
- Monitor error spikes in Notionmonitor
- Monitor cron-job health in Notionmonitor
- Monitor CI/CD build status in Notionmonitor
- Flag high-value leads in Notionalert
- Catch churn-risk signals in Notionalert
- everything you can pipe to Notionhub