What it unlocks
Read team docs
Agents can read the Notion pages and databases you share with the integration. Useful for runbooks, service ownership, and incident procedures.
Write pages and entries
Agents can create pages and add rows to databases you share. Good for RCA publishing and post-mortem workflows.
Scoped by what you share
Notion’s sharing model means the integration can only see what you explicitly share with it. Nothing else.
Evidence back to the source
Anything published includes links back to the RubixKube console so the evidence trail stays intact.
Connect it
Once connected, Notion is available tenant-wide. Every agent across every environment can use it.
How the agents use it
- Agents can look up runbooks, architecture notes, and incident procedures when investigating or answering questions in chat.
- RCA reports can be published to a shared page or database so post-mortem reviews happen where the rest of your knowledge lives.
Build custom workflows with skills
The connection exposes read and write capabilities to agents. Specific workflows (publish every RCA to a specific database, weekly incident digest page, pull runbook content into the agent’s context during an incident) are built as Skills. Skills are where you tailor the integration to your team’s exact workflow.Troubleshooting
Agents cannot find a page
Agents cannot find a page
The integration only sees what you have explicitly shared. Open the page or database in Notion and add the RubixKube connection to it.
Writing to a database fails
Writing to a database fails
The database schema needs to match the fields the skill is writing. Check the properties on the target database and adjust the skill or the schema.
Related guides
Linear
Pair with Notion for ticket-to-doc workflows.
Skills
How to compose Notion capabilities into workflows.