Notion is where the PRD, the research note and the decision log live. Connecting it lets an agent start work when one of those pages changes, and read the page while it runs. Squad never writes to Notion.
Connect
Start the install
Click Connect on the Notion card. Notion’s install screen opens.
Choose the pages to share
That screen asks which pages to share with Squad. Pick carefully, because that choice is the whole of Squad’s access.
Approve
Approve, and you land back on the Notion detail page as Connected.
To share more pages later, run the connect flow again and add them.
Triggers
Notion declares one trigger, Page updated. It fires when a page Squad can see changes.
Unlike most triggers, this one is scoped to a single page. When you add it in the agent builder, a search box lets you pick which page to watch. The agent then runs only for edits to that page, not every page Squad can see.
Pages as sources
A Notion page can also be attached to an agent as a source. Sources are read into the agent’s brief on every run, so the page’s current content is in front of the agent even when something else triggered it. Use this for a spec or a strategy doc the agent should always work against.
Notion databases aren’t available as sources. Only pages are.
With no argument it reads the page that triggered the run. Pass a page ID to read a different one. Notion has none. Squad reads pages and does nothing else to your Notion workspace.
Signals
Nothing from Notion becomes a signal, and nothing imports into knowledge documents. Notion content reaches Squad through the trigger, the source and the read tool, and nowhere else.
A worked example
Your team keeps a live PRD in Notion. Build an agent triggered on Page updated, pointed at that page. On each edit it reads the page, compares the requirements against recent signals, and writes a short note on which parts of the spec the evidence no longer supports. That note lands in Squad, or in a Slack channel if you gave the agent Slack delivery.
Limits
Squad sees only the pages you shared during the install. Databases can’t be watched or used as sources. There’s no write path, so an agent can’t append to a page or tick a checkbox. The trigger reacts to page changes. Comments and property-only edits aren’t separate triggers. 
