Tools
Notion
Pages, databases and blocks, read and written.
Official site: www.notion.so
What it does
- Read and search pages and databases
- Create and update pages and blocks
Reads and writes at both levels — individual pages and the databases that structure them — so a workflow can update a single page or query a database like a table, depending on which shape the source of truth actually has.
Why through Tulina
Most systems now publish their own way for a model to reach them, and that is a good thing — it is what Tulina connects to. The connection was never the hard part. Deciding who may use it, what it is allowed to return, and what the model knows before it asks: that is.
The keys stay in one place
Connect Notion once. The credential is encrypted in a vault, never held in clear, and never pasted into a chat or a workflow file. A person uses their own key where they have one, their team's where they do not, the organisation's after that — so nobody is blocked and nobody is handed more access than they need. Revoke it once and everything running on it stops.
What leaves is filtered before it leaves
Roles decide who can reach Notion at all. Beyond that, a policy on the connector itself decides what comes back: fields dropped, identifiers masked or hashed, people pseudonymised. The data is minimised at the source rather than after it has already reached a model.
Every call is on the record
Runs are logged for the organisation — what was called, by whom, when. That is what makes an automated action reviewable after the fact, and what a security review asks for first.
The run starts knowing your company
A direct connection gives a model access. It does not tell it how your company names things, which accounts matter, or what was decided last quarter. Tulina carries that across every tool, so the same request against Notion returns something usable instead of something generic.
Processes that run on Notion
Call feedback becomes tickets and docs
Every call recorded during the day is distilled overnight, with bugs and feature requests routed to the right team as tickets and docs, plus a Friday digest.
Draft the quarterly LP letter
Portfolio metrics gathered from founder updates and dashboards, drafted into your quarterly letter, with every figure carrying the date it was reported.
Keep your knowledge base current
Every morning, the previous day's activity gets read across your team's tools and synthesized into what changed, automatically and unattended.
Publish the Monday brief
Product usage, pipeline, and customer feedback joined into one executive report, published before the team sits down.