Give Notion read-only Cooperly context and playbook guidance for docs, decisions, and planning while Notion owns writes.
Why teams connect Notion
Notion is where many teams draft specs, memos, hiring notes, project pages, and operating docs. Those artifacts become stronger when the workspace can reference real team context.
The Notion integration gives that workspace a read-only Cooperly context source without making Cooperly responsible for Notion-side writes.
What the integration does
Cooperly exposes read-only team, member, and candidate context to Notion. It also provides get_notion_agent_playbook so Notion can use Cooperly context appropriately.
Notion remains responsible for Notion-side writes and actions. Cooperly supplies context; it does not become a Notion automation engine.
Why it matters
The integration helps Notion produce more grounded docs and decisions while keeping the boundary clear: Cooperly is the context layer, Notion is the workspace.
Configure
- 01
Enable Notion access in Cooperly
Turn on Notion access and grant it only to the Cooperly teams a Notion custom agent may use.
- 02
Allow custom connections in Notion
Ask a Notion workspace admin to allow custom agent connections if the workspace has not enabled them yet.
- 03
Add Cooperly to the custom agent
Open the custom agent settings, add Cooperly as a connection, and paste the Cooperly server URL from settings.
- 04
Sign in with Cooperly
Complete browser sign-in with the Cooperly account whose team access should power the agent.
- 05
Use the playbook in Notion
Use Cooperly context and get_notion_agent_playbook while Notion handles Notion-side writes and actions.