How to Connect Multiple Notion Workspaces to Grok
Grok has a real, first-class Notion connector. It is native OAuth: no personal access token to paste, no MCP server to run, and xAI says “connectors are available to all Grok users”. You add it at grok.com/connectors in about a minute, and both search and edit are claimed. That is a good starting position, and the catch is not where people expect it. Many pages and databases inside one workspace are fine. A second workspace runs into a limit that Notion, not xAI, has written down. Carly holds your Gmail and Outlook mailboxes and every calendar on both sides in the same place.
One orientation note first. “Grok” now names three products: the consumer assistant at grok.com and in the mobile apps, Grok Bot for Slack and GitHub, and the Grok API. This page is about the first one only.
Notion is a built-in connector, not a catalogue row
xAI’s May 2026 connector launch post names Notion on day one, next to SharePoint, Outlook, OneDrive and Google Workspace, and describes it as “Work directly in your Notion workspace. Search or edit pages, databases, and wikis across you and your team’s docs.”
The shipped grok.com app agrees. Notion carries one of the lowest connector type ids in the same internal list as Gmail, Slack, SharePoint and custom MCP, and the client keeps those built-in types separate from the wider catalogue of apps it looks up by id. Round-ups often file Notion with that long tail of niche apps; it sits a tier above them. The interface strings match: “Give Grok access to your Notion pages”, then “Search for pages, summarize documents, and ask questions about your Notion workspace.” A tour of the whole set is in our Grok connectors overview.
One connection means one workspace, and Notion is the one saying so
Notion’s connections documentation is blunt: “Connections are workspace-specific!” Its setup instructions tell you to “click the workspace name at the top right to switch to another workspace if needed”, then press Select pages. On changing one later: “to change the associated workspace, you’ll have to create a new connection.”
The authorization shape says the same thing. A Notion OAuth grant carries a single required workspace_id, documented as “the ID of the workspace where this authorization took place”. One grant, one workspace.
On the Grok side there is nothing at all. The word Notion does not appear once in the machine-readable index of xAI’s whole documentation site, and while there are connector pages for Gmail and Google Calendar, Google Drive, OneDrive, Outlook, SharePoint, Teams and Salesforce, none covers Notion. No capability table, no scope list, no statement about adding the connector twice.
So keep the two halves apart. Notion documents a workspace-scoped connection. xAI documents nothing either way about a second one. Two signals lean singular without settling it, both inferences: every documented Grok connector delegates access to the signed-in user, with the Outlook page saying “Grok can only access the mailbox of the signed-in user”; and the app resolves a connector by taking the first match for its type, in three separate places. Even if the backend stored two Notion connections, the client would address one.
One decay timer. That type field is literally named as deprecated, connections already carry their own ids, and id-keyed lists appear elsewhere in the code: the shape of a migration from type-keyed connectors to id-keyed ones, which is the groundwork multiple instances would need. Inference, not a roadmap, and a reason to retest in a few months.
Which verbs xAI actually names
There is no published capability table for Notion, so this is the place to resist filling in blanks. Gmail gets a documented scope ladder from read to modify to send. Notion gets marketing and interface copy.
| Action | Status |
|---|---|
| Search pages, databases and wikis | Named by xAI: “search or edit pages, databases, and wikis” |
| Read and summarize pages | Named: “summarize documents, and ask questions about your Notion workspace” |
| Edit existing pages | Named: “Grok can search, read, and edit your pages” |
| Read databases | Named, as part of “pages, databases, and wikis” |
| Create a new page | Not documented |
| Update database properties | Not documented |
| Comment on a page | Not documented |
That copy has a tension in it. Grok’s consent screen is read-flavoured, titled “Access your pages” and describing search, summarize and ask, while the upsell and the launch post both say edit. Unlike SharePoint, Notion has no separate read-write variant in the connector list, so whether writes are gated progressively by an administrator the way calendar writes are is unverified in both directions. A granted scope is not an exposed action, and here the scope list has not been published at all. Test one low-stakes edit before trusting it with a live spec.
Nothing fires when a Notion page changes
Grok closed part of the event gap in July 2026. Scheduled automations are open to everyone and email triggers come with SuperGrok, matching on sender, recipient, or subject. The limit is that the inbox is the only thing it watches, so anything that happens in another app still has to be noticed by a person first.
Get the distinction the right way round. A Notion connector can be pulled into an automation: xAI documents typing @ to mention a connector so Grok uses it on every run, so a scheduled 8am job that reads a Notion database and mails you a summary is buildable today. See Grok Automations for the mechanics. What cannot happen is Notion starting the work.
The gap is sharp here, because Notion emits exactly the events Grok will not listen to. Notion publishes documented webhooks for page.created, page.content_updated, page.properties_updated, page.moved, page.deleted, database.content_updated and database.schema_updated, and describes them in its own words: “Instead of repeatedly polling the Notion API to check if anything has changed, Notion will tell you the moment something important happens.” The signal is public and real time, and Grok has no way to subscribe. A new row in an intake database, a status flipping to Approved, a colleague rewriting a spec: silent until you ask.
The “Grok + Notion” pages you find first are a different product
Search this topic and the first results are usually Zapier, Pabbly or Albato pages pairing “Grok by xAI” with Notion. Those wire the Grok API in as a model step inside somebody’s workflow. They are not the grok.com assistant reaching your workspace.
Two more to discount. A widely quoted article about an upcoming xAI connector bringing Notion support to Grok is a pre-launch piece from 2025, so read it as history. And several listicles assert that Grok “respects Notion’s permission model”. xAI has never written that; the narrower documented truth is that a connection only reaches pages added to it. Notion does not mention Grok anywhere in its developer documentation or list it as an MCP client.
Two admin gates stack on a work plan
Most guides mention one. There are two, and either can be why the button is missing. xAI’s gate is the cloud console at console.x.ai, under Grok Business then Connectors, where an admin uses Add Connector with Team Read-Write permission. Notion’s gate is separate: “workspace owners manage all connections in a workspace”, and on Enterprise plans owners can restrict which connections members may install. Clearing one does not clear the other.
Why the Google Calendar trick has no Notion equivalent
On the calendar side of this lane there is a workaround: share a second account’s calendar into the connected account and it turns up in the same list. That does not transfer, and the reason is structural rather than a missing feature. Notion has no cross-workspace page sharing, and guest access adds a person to a workspace rather than a workspace to a connection. Treat that as an inference from Notion’s model, then plan for it: consolidating what you need into teamspaces inside one workspace is the only real single-connection path. The multiple Google Calendars page has the contrast.
1. Sort your case
| What you have | Native path in Grok |
|---|---|
| One workspace, many pages and databases | Yes, grant a parent page and children follow |
| A teamspace you already have access to | Yes, if it is added to the connection |
| Two Notion workspaces at once | Notion documents connections as workspace-specific; xAI is silent |
| Switching which workspace Grok sees | Yes, redo the authorization, about a minute |
| Editing an existing page | Claimed by xAI, with no scope table published |
| Creating a page or setting properties | Not documented |
| Reacting when a page or database changes | No Notion trigger of any kind |
2. Connect Notion in Grok
- Go to grok.com/connectors on the web, or Settings then Connectors on iOS and Android.
- Click New Connector and select Notion.
- Sign in with the Notion account that holds the workspace you want.
- On Notion’s authorize screen, check the workspace name at the top right before going further.
- Press Select pages and choose what Grok may reach.
- On Grok Business or Enterprise, ask an admin to provision the connector in the cloud console first.
There is no token step anywhere in this flow. A guide telling you to generate a Notion integration token is describing a different product.
3. Grant access at the right page
- Pick the top page of each area you care about rather than individual documents.
- Notion states that “if a connection is added to a page, then the connection can access the page’s children”, so a parent grant covers the tree beneath it.
- Add the connection to any page outside those trees, one by one.
- Skip anything confidential; a page you do not add is a page Grok cannot see.
- If Grok cannot find a document you know exists, this is almost always why. Notion calls it the number one support issue with connections.
4. Switch workspaces when you need the other one
- Open grok.com/connectors and remove or re-authorize the Notion connector.
- Start the Notion sign-in again.
- Click the workspace name at the top right of Notion’s authorize screen and pick the other workspace.
- Press Select pages and grant the parent pages you need there.
- Ask a question about a page unique to that workspace to confirm the swap landed.
This is the useful non-obvious part: repointing Grok at the other workspace is supported and takes a minute. What no product documents is holding both at once, and Notion’s workspace-scoped connection is the reason one grant cannot cover them.
5. Connect every Notion workspace to Carly
- Sign in at carlyassistant.com.
- Open carlyassistant.com/integrations.
- Find Notion and click Connect.
- Authorize the first workspace.
- Repeat for every other workspace: personal, company, client.
- Check each one appears in the connected list before you rely on it.
6. Add Carly to Grok
- Go to grok.com/connectors.
- Click New Connector, then select Custom.
- Enter
https://carlyassistant.com/mcp/. - Complete the authentication step.
- Sign in to the Carly account holding the connections above.
Grok discovers the tools Carly exposes and offers them in conversation alongside its built-in connectors. On Grok Business and Enterprise a team admin provisions connectors in the cloud console first.
7. Test each workspace, then both at once
One workspace per prompt until the routing is reliable:
In my company workspace, find the launch checklist and list every item still marked Not started.
In my client workspace, summarize the last three meeting notes pages and pull out anything assigned to me.
Then the question that needs two live connections rather than a switch:
Compare the pricing page in my company workspace with the one in my client workspace and list every figure that differs, naming which workspace each came from.
Grok versus Carly on Notion
| Need | Grok | Carly |
|---|---|---|
| Search and read one Notion workspace | Yes | Yes |
| Free connector on the entry tier | Yes | Yes |
| Native OAuth, no token to paste | Yes | Yes |
| Hold two workspaces as separate connections | Not documented, and Notion scopes a connection to one | Yes |
| Edit an existing page | Claimed, no scope table | Yes |
| Create a page or set database properties | Not documented | Yes, pages and properties both |
| Act when a page or database changes | No Notion trigger | Yes |
Grok’s Notion connector is free on every consumer tier and is set up by signing in rather than pasting a developer token. One authorization covers one workspace, so a client’s workspace has nowhere to go.
Carly is built for the part that is left. It authorizes per workspace, so a company workspace and a client workspace sit side by side as separate connections and one question can span both, with no consolidation project and no re-authorizing to switch. It also acts on the change rather than on a clock: the row appears, the status flips, the work starts. That is the half of the problem Notion’s webhooks describe and Grok cannot yet hear.
Free Zapier-style workflows; AI agents from $35/month. Connect it on the integrations page, or start with Notion.
Quick fixes
| Problem | Fix |
|---|---|
| Grok cannot find a page you know exists | It was never added to the connection; add the connection to that page or its parent |
| Notion is not in the connector list | On Business and Enterprise an admin must provision it in the cloud console with Team Read-Write permission |
| Notion is missing from the authorize screen | Your Notion workspace owner may have restricted which connections members can install |
| A guide tells you to create an integration token | Wrong product; Grok’s Notion connector is OAuth and asks for no token |
| The Zapier “Grok by xAI + Notion” page does not help | That uses the Grok API as a model step, not the grok.com assistant |
| The second workspace has nowhere to go | Notion scopes a connection to one workspace; switch the connection, or use a tool that authorizes per workspace |
| Nothing happens when a database row changes | There is no Notion trigger; schedules run on a clock and email triggers watch the inbox |
Frequently asked questions
Does Grok work with Notion?
Yes. Notion is a built-in connector, named in xAI’s launch post alongside SharePoint, Outlook and Google Workspace, and set up at grok.com/connectors by signing in with Notion. Connectors are available to all Grok users, and on Business or Enterprise an admin provisions them first.
Can I connect two Notion workspaces to Grok?
Not as two live connections, and the constraint is Notion’s rather than xAI’s. Notion documents that connections are workspace-specific and that changing the associated workspace means creating a new one, and each authorization carries a single workspace id. xAI has published nothing either way about adding the connector twice.
Do I need a Notion API token for Grok?
No. The connector is native OAuth, so you sign in and choose pages. Anything asking you to generate a personal access token is describing a different integration path.
Can Grok edit my Notion pages?
xAI says it can, in its launch copy and its upsell text. It has published no scope table and no read-write variant of the connector, and its own consent screen is read-flavoured, so treat editing as claimed rather than specified and try one small change first.
Does Grok react automatically when a Notion page changes?
No. Automations run on a schedule for everyone, and on SuperGrok they fire on an incoming email matching a filter. Notion publishes webhooks for page and database changes, but Grok has no way to subscribe, so nothing starts because a page was edited.
Related: Multiple Google Calendars in Grok · Multiple Gmail accounts in Grok · Multiple Notion workspaces in ChatGPT · Multiple Notion workspaces in Claude · Grok connectors · Notion integration
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
