◆ PostMoney Integrations

Home / Notion

The fund's wiki, both directions

Notion: notes in, live numbers out.

If a fund keeps meeting notes and portfolio pages in Notion, PostMoney can read them as it reads an emailed update, and can keep a Notion database current with the metrics it extracts. The 2026 developer platform makes both far cheaper than they used to be.

Why this matters

Bigger than the classic read-a-database API

The research asked one question: if a fund keeps meeting notes and company updates in Notion, what could a PostMoney integration do? Its one-line answer: yes, and it is substantially bigger than the classic read-a-database API. Notion shipped a full developer platform in May 2026 (Workers, External Agents, CLI, MCP, Admin API), and the data API itself gained a markdown surface that removes most of the historical pain of reading Notion content.

That markdown surface is the headline for PostMoney. Reading a Notion page used to mean walking an arbitrarily nested tree of typed blocks and writing your own serializer. Now a whole page arrives as text, so a fund's meeting-note page can be handed to the existing extraction pipeline the same way an emailed update or an uploaded document is. For notes, no schema mapping is needed at all: unstructured text is what the pipeline already handles well. Mapping only matters for structured property columns in a portfolio database.

What if

Seven things a Notion connection could do for a fund

The research lays out five integration directions, A through E, roughly in order of obviousness. Here they are as experiences, with the onboarding hook and the portfolio database split out on their own.

Near-term ranked first, cheap, or immediate Needs research open questions or approval gating Later deeper placement, larger build

Meeting notes flow in without a mapping step

Near-term

A fund keeps a page per company with meeting notes as child pages. When a note changes, PostMoney reads the page as markdown, pre-signed media links included, and treats it as a source input beside email and uploaded documents. Toggles, callouts, tables, and transcription blocks all arrive as text.

Unstructured text is what the pipeline already handles well. No schema, no mapping, the same extraction the fund already trusts.

Your portfolio database, understood

Needs research

A fund has a "Portfolio" database, one row per company, with properties for ARR, runway, stage, and last check-in. PostMoney reads the schema and proposes a mapping from the schema plus sample rows; the user confirms it. Or the fund duplicates PostMoney's template at install and the schema is known from the first second.

Structured columns become tracked metrics without a manual field-by-field setup. The fund's own tracker starts feeding the record.

Open question: do target funds actually keep updates in databases, or mostly in free-form pages? That decides whether property mapping matters at all.

Start from our template, not your chaos

Near-term

During connect, the OAuth flow can offer a Notion template the fund duplicates instead of selecting existing pages, and a documented post-install flow can create databases, pages, and views in the workspace right after install. A PostMoney portfolio tracker appears with a schema we already know.

This inverts the hardest UX problem, "where is your data." Point-at-existing-Notion becomes the advanced path rather than the only path.

PostMoney's numbers stay live in Notion

Near-term

A Notion database kept current with PostMoney's extracted metrics, an optional "Latest Update" child page per company, and board and chart views created alongside it. The fund keeps living in Notion while the numbers are ours. The research calls this direction underrated and stickier.

PostMoney becomes the source of truth without asking anyone to change tools. One authoritative direction per field, never bidirectional sync.

Paste a PostMoney link, see current metrics

Needs research

A partner pastes a PostMoney company link into their meeting notes and a Link Preview unfurls the current metrics inline. Because the source service pushes updates to Notion when the underlying data changes, the preview stays fresh; the research cites a GitHub pull request preview updating when it merges.

Small build, high perceived value. Gated on Notion approving PostMoney as a Link Preview partner.

Open question: what is Notion's actual approval bar for a Link Preview partnership?

PostMoney inside the fund's own agents

Later

A Notion Worker exposes a tool, "look up this company in PostMoney," that the fund's Custom Agents call on demand while someone drafts an investment memo in Notion.

A very small surface that lands PostMoney inside their AI workflow. No one has to switch apps to ask us a question.

A PostMoney analyst in the Notion sidebar

Later

The External Agents API registers PostMoney as a native workspace participant. It appears in the workspace's agent list, chats in Notion, and answers portfolio questions with our data. The research calls this a real shipping shape rather than a metaphor.

The deepest placement of the five directions. Also the largest build.

Two more shapes worth knowing

Not integration directions, but they change the math

Notion MCP

Notion runs an official hosted MCP server, plus an open-source version for local hosting. If PostMoney's AI layer should reason over a fund's Notion during a chat session, MCP is the cheaper path than building ingestion for that use case.

Notion's own guidance: MCP for broad, flexible connectivity; Workers when you need deterministic execution and custom logic.

The meeting-notes endpoint

Notion can generate AI meeting notes from uploaded audio or video, and the transcript is readable back through the markdown API when requested.

The research leaves this as an open question: does it open a path for funds recording portfolio calls?

A day with it

How notes get from Notion into the record

The research's flow for direction A, Notion to PostMoney ingestion, in five steps.

1

The fund connects and chooses what we can see

OAuth connect. The page picker is where the fund tells PostMoney where to look, or they duplicate our template instead. Access is opt-in per page tree, never workspace-wide.

2

PostMoney reads the schema and proposes a mapping

For a portfolio database, PostMoney reads the data source schema and presents a mapping step, or lets its AI propose the mapping from schema plus sample rows and asks the user to confirm. For meeting-note pages this step is skipped entirely.

3

PostMoney subscribes to changes

Webhook subscriptions for data source content changes, new pages, page content edits, and page property edits. Events also say whether the author was a person or an agent, so an AI rewrite can be treated differently from a human edit.

4

A note changes, PostMoney reads and extracts

Events are thin and only signal that something changed, so a job fetches the page as markdown and feeds it into the existing extraction pipeline. Notion becomes another source input type alongside email and uploaded documents.

5

A periodic sweep catches anything the webhooks missed

Notion delivers webhooks at most once, so a reconciliation sweep runs as a backstop. Webhooks are never the only path to correctness.

Where PostMoney is different

Notion has AI. It does not have the portfolio model.

Notion ships its own AI and its own agents, and the fund will use them. PostMoney's part is the portfolio model: extraction with provenance, reporting periods, metric schemas, and the cross-source comparison with written updates, meetings, and the CRM. Notion is where the fund reads and writes. PostMoney is what makes the numbers trustworthy.

Open questions the research raises

What we would need to learn from funds

  • Do our target funds actually keep updates in Notion databases, or mostly in free-form pages? The answer decides whether property mapping matters at all.
  • Would funds prefer duplicating a PostMoney template over pointing at their existing structure? The template path is dramatically cheaper for us.
  • Is sync out (direction B) more valuable than ingest (direction A)? B makes PostMoney the source of truth without asking anyone to change tools.
  • Does the create-meeting-note endpoint (audio or video in, AI notes out, transcript readable) open a path for funds recording portfolio calls?
  • What is Notion's actual approval bar for a Link Preview partnership?

Under the hood

Platform facts, from the research

Verified against developers.notion.com on 2026-09-01. Anything marked beta is flagged as public beta by Notion's own docs. The cross-integration requirements live on Foundations.

Surfaces

  • REST API version 2026-03-11, sent as the Notion-Version header
  • GET /v1/pages/:id/markdown to read a page as markdown, PATCH /v1/pages/:id/markdown to write
  • POST /v1/data_sources/:id/query for rows, POST /v1/search for what we can see
  • Webhooks with an HMAC-SHA256 signature: page.*, data_source.*, comment.*, file_upload.*, view.*
  • Notion Workers: syncs, tools, and webhooks hosted by Notion
  • CLI ntn, available on all plans
  • Agent APIs and External Agents API (beta)
  • Notion MCP, Link Previews, Admin API

Limits

  • About 3 requests per second per connection, with some burst allowance
  • A separate per-workspace limit, shared with the customer's other connections and invisible to us
  • Exceeding returns 429 or 529; respect Retry-After
  • 1,000 block elements and 500KB payload per request; 100 elements per array per request
  • Query pagination at 100 rows per page
  • Workers on Business and Enterprise plans only, and they consume Notion credits
  • Marketplace review takes 5 to 10 business days; listing is optional

Caveats

  • The 2025-09-03 breaking change: a database is now a container of data sources. Store database_id and data_source_id separately. Migration deadline September 30, 2026.
  • Webhooks are at-most-once, thin, out of order, and aggregated. Reconciliation is mandatory.
  • Tokens are per user, not per workspace: many connections per organization, routed via accessible_by
  • Installation scope (Any workspace vs Selected workspaces) is permanent; only Any workspace is Marketplace eligible
  • Changing capabilities forces every existing user to re-authenticate
  • Rollups and formulas come back opaque; relations return bare page IDs
  • "I can no longer see this" must not delete already-extracted data

Cross-cutting requirements, things to flesh out, and open product questions across all five integrations: Foundations →

← Previous: Slack Next: Zapier →