Connect Multiple Notion Workspaces to Perplexity
Perplexity’s native Notion connector is listed for Max, Enterprise Pro and Enterprise Max, and one Notion authorization holds exactly one workspace, so reaching a personal workspace and two client workspaces from one chat runs through Carly. Authorize each workspace in Carly, add Carly to Perplexity once as a custom remote connector, and every answer names the workspace it came from. Carly holds your Gmail and Outlook mailboxes and every calendar on both sides in the same place.
What one chat can do afterwards
- Search your own workspace and a client’s in the same question.
- Show which workspace every matching page lives in.
- Create a page or update a property in the workspace you name.
- Add a database row in one workspace and log the date in another.
- Reach Notion from the entry paid tier instead of waiting for Max.
- Act when a row lands rather than at the next hourly poll.
Nothing is merged. Each workspace keeps its own authorization, and every one stays individually addressable.
The plan boundary comes first
Perplexity’s Notion documentation, updated 16 July 2026, lists the connector for Perplexity Max, Enterprise Pro and Enterprise Max. Plain Pro is not on that list, while custom remote connectors reach down to Pro. The omission looks deliberate: Perplexity’s Slack connector documentation names Pro explicitly in its availability line, and the Notion article does not.
Read is documented, write is only permitted
The connector is managed at Settings → Connectors and queries Notion live rather than copying it. Perplexity’s documentation says only the specific results needed to answer each query are retrieved, and that Perplexity does not store or index the entire workspace, unlike its file connectors, which sync selected files into AWS S3. Access is bounded by your own Notion permissions, and on Enterprise an admin can disable it for everyone.
The permissions it requests include mirroring your page and database access, viewing the workspace’s users and their emails, and taking actions on your behalf based on your access level. That third one reads like a write capability. It is not the same thing as one, and Perplexity’s own connector index makes the point:
| Connector | Perplexity’s own summary |
|---|---|
| Asana | ”Search, create, and manage” tasks, projects and teams |
| Confluence | ”Search, create, and manage” pages and spaces |
| Linear | ”Query, create and update” Linear issues |
| Microsoft Teams | ”search, message, and collaborate” across chats and channels |
| Notion | ”Unlock smarter answers by combining Notion and Perplexity” |
Every neighbour names its write verbs. Notion names none, and the Notion article’s own worked examples are all retrieval. Permission granted is not the same as action exposed.
Two workspaces stops at Notion, not at Perplexity
Perplexity is silent on this. Its Notion article never uses the words switch, multiple, second, or disconnect. One connector card, one Enable button, one sign-in, no workspace picker.
The real constraint sits on Notion’s side, and it is not silent at all. Notion’s help documentation carries a blunt callout that connections are workspace-specific, and tells you to click the workspace name at the top right to switch. Notion’s developer documentation reinforces it at the MCP layer: after you authorize, the client can read and update content you can access in the selected Notion workspace. Selected, singular. The plumbing agrees, since Notion’s OAuth token response carries a single workspace_id.
One grant, one workspace. Notion’s own hosted MCP server does not rescue this either, since pointing any client at it still authorizes one workspace per grant. The wall is the same on every host in this lane, described in multiple Notion workspaces in Claude and in ChatGPT. Everything inside one workspace still comes along: teamspaces, databases, pages you were added to.
1. Sort your case
| What you have | Native path in Perplexity |
|---|---|
| Many teamspaces in one workspace | Yes, one connection covers them |
| A Pro plan rather than Max | Connector not listed for Pro |
| Creating or updating pages | Not documented natively |
| Personal workspace plus a company one | One grant per workspace |
| Several client workspaces | No documented path |
| Anything firing when a page changes | No |
The Pro row is the one that stalls people, and it is the reverse of what they expect. On Slack, Pro is enough. On Notion it is not.
2. Connect every workspace to Carly
- Sign in at carlyassistant.com.
- Open carlyassistant.com/integrations.
- Find Notion and click Connect.
- Authorize the first workspace, checking the name on Notion’s screen.
- Return to the integrations page and click Connect on Notion again for the next workspace.
- Confirm which workspace each connection landed in before adding the next.
Notion preselects whichever workspace you used last, so read the name on its authorization screen every time. Grant access to the pages and databases the work needs rather than the whole workspace. Widening later is one click.
3. Add Carly as a custom remote connector
Perplexity shipped Bring Your Own Connector for Pro, Max and Enterprise subscribers in March 2026, which is how Perplexity reaches the workspaces you just authorized:
- Open Settings → Connectors.
- Click + Custom connector, then select Remote.
- Enter a name and
https://carlyassistant.com/mcp/as the MCP server URL. - Choose the authentication option and acknowledge the third-party connector risk.
- Add the connector and finish authorization.
Perplexity’s remote connector guide supports HTTPS servers over Streamable HTTP or SSE. Enterprise administrators can share a connector across the organization and decide whether members may add their own; that member permission is disabled by default. An older Perplexity article still says remote MCP is “coming soon”, while the custom connector article updated 14 August 2026 documents it as shipped, and the newer one matches the current interface. Notion MCP and the wider MCP servers overview cover the protocol itself.
4. Test each workspace read-only
One workspace per prompt until routing is reliable:
In the Company workspace, list the five most recently edited pages and who edited them. Do not change anything.
In the Client workspace, find the current onboarding checklist and tell me which items are unassigned. Read only.
Then the question a single grant cannot answer:
Search the Company and Client workspaces for pages mentioning “renewal” updated in the last 30 days, and show the source workspace on every row.
5. Reuse this routing prompt
Treat my own workspace as Personal, my employer’s as Company, and the Databricks delivery workspace as Client. Always state the target workspace before creating a page, updating a property, or adding a database row. Never write to a workspace I have not named.
Then name the target per action:
Add the kickoff notes as a new page in the Client workspace under Engagements, and log the date on the Company projects database.
Hourly polling has a price tag here
Perplexity can run unattended, and its Scheduled Tasks documentation names Notion among the connectors a task can use. What it cannot do is start because something changed: scheduled tasks support any recurring cadence as long as it runs no more often than once per hour, and sub-hourly cadences are unsupported.
There is no such thing as an MCP trigger. The protocol's own working group states plainly that clients find out about server-side changes by polling for them, and a real event mechanism remains unshipped.
The cost is concrete here. Every scheduled run consumes Computer credits, and if credits run out the run is skipped. Each conversation can own up to 15 scheduled tasks, and there is no paused state: stopping a task removes it permanently.
Notion already emits the change event. Its developer documentation describes webhooks in plain terms: whenever a page or database changes, Notion sends a secure HTTP POST to your endpoint, free, the instant it happens. Perplexity has nowhere to receive it, so the closest it gets is spending credits every hour to ask whether anything happened, and paying the same on the 23 hours when nothing did.
Perplexity versus Carly on Notion
| Need | Perplexity | Carly |
|---|---|---|
| Search pages and databases from a chat assistant | Yes | Yes |
| Live query with nothing indexed or stored | Yes | Yes |
| Reach Notion on the entry paid tier | No | Yes |
| Create and update pages | Not documented natively | Yes |
| Hold two workspaces at once | One grant, one workspace | Yes, each one named |
| Answer across two workspaces in one reply | No | Yes |
| Act when a database row lands | No, hourly at best | Yes |
| Cost of watching for a change | Credits per poll | Runs on the event |
Carly authorizes each workspace separately, so a personal workspace, an employer’s and two client workspaces sit side by side and every answer names which one it came from. It starts on the event rather than on a clock: a row lands in the intake database, the owner gets assigned, the kickoff page gets created, and the client gets an email.
Free Zapier-style workflows; AI agents from $35/month. Connect the workspaces at carlyassistant.com/integrations, then point Perplexity at carlyassistant.com/mcp.
Quick fixes
| Problem | Fix |
|---|---|
| No Notion option in Settings → Connectors | It is listed for Max, Enterprise Pro and Enterprise Max, not Pro |
| Connector is enabled but returns nothing | Open Set sources for search in the session and select Notion |
| Notion is greyed out on an Enterprise account | An organization admin has disabled it for all users |
| Perplexity will not write to a page | Writes are not documented on the native connector; route them through Carly |
| A guide says Perplexity has no remote MCP | That is the stale article; the August 2026 one documents it as shipped |
| No + Custom connector button | On Enterprise, the member permission for custom connectors is off by default |
| The connector answers from the wrong workspace | One grant holds one workspace; check which one you authorized |
Frequently asked questions
Can Perplexity connect to two Notion workspaces?
Not natively. Notion’s own documentation states that connections are workspace-specific and that a client reads content in the selected workspace, with one workspace ID per OAuth grant. Authorize each workspace in Carly and add Carly once as a custom remote connector, and one chat reaches all of them.
Which Perplexity plan do I need for the Notion connector?
Perplexity’s Notion documentation lists Max, Enterprise Pro and Enterprise Max. Pro is not named, which is notable because the Slack connector page does name Pro. Custom remote connectors are available from Pro upward, so Pro subscribers reach Notion through Carly.
Does anything happen automatically when a Notion page changes?
Not in Perplexity. Scheduled tasks run no more often than once per hour, sub-hourly cadences are unsupported, and every run spends credits whether or not anything changed. Notion does emit a webhook on every page and database change, and Carly acts on that event.
Related: Multiple Notion workspaces in Claude · Multiple Slack workspaces in Perplexity · Multiple Gmail accounts in Perplexity · Notion MCP · Best Notion integrations · Notion
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."
