Bob with Notion: make the company wiki part of the work

Matthew, founder of Bob · Published July 30, 2026

Short answer

Bob's purpose-built Notion connection can search, read a page, query a database, create or update a page, and append blocks. Notion's API models a page as both a set of properties and a place for child content, as described in its page reference.

That makes Notion useful at both ends of a job. Bob can read the policy before acting, then write the result back to a project page after you approve the change.

Five useful Bob and Notion workflows

1. Answer from the actual policy

"Find our travel policy in Notion and tell me the approval rule for an international conference. Cite the page."

Bob can search and read the relevant page instead of inventing a policy from memory.

2. Query a project database

"Query the launch database for blocked items due this month. Group them by owner and blocker."

Database structure makes this more reliable than searching prose across the workspace.

3. Turn a Slack decision into durable documentation

"Draft a Notion decision record from this thread with context, options, decision, owner, and date. Show it to me before creating the page."

Bob preserves the useful outcome without making the team rewrite the conversation by hand.

4. Update a project page

"Append today's approved launch status and the open Linear issues to the Northstar page."

Appending blocks changes Notion, so Bob asks by default.

5. Deliver a weekly change brief

"Every Friday, query the roadmap database and summarize changes in status, owner, or target date."

Bob's scheduler can put the brief in Slack while Notion remains the source of truth.

How the connection works

1. Ask Bob in Slack to connect Notion.
2. Open the hosted OAuth flow and choose the workspace.
3. Review which pages the integration can access.
4. Return to Slack and retry the page or database request.

Bob's purpose-built Notion path is personal. Notion still requires content to be shared with the integration. Connecting the workspace does not automatically expose every private page.

Limits worth knowing

• Sharing controls visibility. Bob cannot read content that is not available to the connected integration.
• Database schemas vary. Property names and types need to match the actual database.
• Writes ask by default. Create, update, and append operations remain reviewable.
• Notion should not become a transcript dump. Save decisions and durable context, not every line Bob produced.

FAQ

What can Bob do with Notion?

Bob can search, read a page, query a database, create or update a page, and append blocks.

Whose Notion access does Bob use?

The person who connected Notion, plus the pages shared with that integration.

Does Bob ask before changing Notion?

Yes. Creating, updating, or appending content asks by default.

Can Bob read every page in the workspace?

No. Notion sharing and integration permissions still apply.

Start with one source-grounded answer

Ask Bob to find and cite a known page. Once retrieval is right, let him draft a small update. Connect Linear, Google Drive, or Google Calendar when the job spans other systems.