How to Use the Notion Connector in Muse

1. The short answer

As of October 25, 2026, Notion is a live connector in Muse. It was named in the Muse for Small Business list on September 29, 2026, named again in the October 7 expanded connector list that shipped with the iPad app, and still listed in the October 15 in app check, which counted 54 connectors in the web app. Connect it and your docs, wikis, and project boards become context Muse can reason from: project background, decisions, and the notes behind them, available in the same conversation where you ask the question.

Here is the honest version. Most tools give Muse data. Notion gives Muse memory. A doc is not just a file to read. It is the record of why a decision was made, who owns what, and what was tried already. When Muse can read that record, its answers stop being generic and start being yours. The rest of this guide covers how to connect it, what to share, what to keep out, and what to watch for.

Muse is invite only right now. Need an invite code? Click here to grab one free from the community pool. Waiting on a launch in your country? Join the waitlist and we will send you a fresh code on launch day. Muse is available in the United States, Canada, and Japan.

2. What you need

• Muse access. You need an account with access first, in the United States, Canada, or Japan, where Muse has launched.
• A Notion workspace you can sign in to. The connector reaches the workspace on the Notion account you sign in with, so use the account that holds the docs that matter.
• A short list of what Muse may read. Decide this before you connect. Start with project docs, roadmaps, and decision notes. Leave HR, salaries, and personal notes out.
• Approvals set to ask me. Anything that edits a page, creates a page, or changes a project board must wait for your tap. Reading can run free. Changing things cannot.
• One project to start with. Pick the project whose docs you reach for most. Connect that first and let the habit form before you share the whole workspace.

3. How to connect it, step by step

The connection takes a few minutes. The sharing decision is the real work, so make it before you sign in.

1. Decide what Muse may read. Write down the three to five pages or databases that matter most: the project doc, the roadmap, the decision log, the meeting notes. Everything else stays out for now. You can share more later.
2. Open Muse and go to Settings. The connectors list lives there. If Notion is not listed, your account has not received it yet, because rollout is staged. There is nothing to install and nothing you broke. Check again in a few days.
3. Find Notion in the connectors list and open it. Sign in with your Notion account when asked and grant the access Muse needs to read the pages you choose.
4. Share only the pages on your list. In Notion, share the pages you decided on and nothing else. A connector that can read everything is a connector you cannot reason about, so start narrow.
5. Set approvals to ask me. In Muse settings, set approvals so that anything that edits a page, creates a page, or changes a board waits for you. Reading and drafting can run free.
6. Test with a question only your docs can answer. Ask Muse something that needs your docs, like what did we decide about pricing in the March notes, or who owns the launch checklist. If the answer matches the doc, the connection is good. If it guesses, the sharing is wrong.
7. Expand slowly. Add one page or database a week, only when a real question needed it and could not be answered. The workspace opens up at the speed of your actual use, not all at once.

Copy this prompt

You are my project assistant. Use my Notion connector only, and only the pages I have shared with you.
Rules: you never edit a page, create a page, or change a board without my explicit approval. You read, summarize, draft, and shortlist. I approve every change.
My project: [name, what it is, who is on it]
Every Monday, do this in order.
1. Read the project doc and the open tasks. Tell me what is done, what is stuck, and what has no owner.
2. Read the decision log. Tell me the last three decisions and what they changed.
3. Draft the week in plain words: the three moves that matter most, in order, with the owner of each.
4. Flag anything in the docs that looks out of date: a date that passed, a task marked done that the notes say is still open, an owner who left.
5. End with the one question I should answer this week for the project to move.

4. What it actually does

The connector earns its place with four uses. Each one is about memory, not storage.

Docs as context for every question

Ask Muse a question about your project and it reads the docs before it answers. What did we decide about pricing? Who owns the launch checklist? What did we try last time this broke? The answers come from your pages, not from general knowledge, which is the whole difference. A generic answer tells you what anyone would do. A doc grounded answer tells you what you already decided to do.

Wikis that answer back

A wiki is a place you search. A wiki connected to Muse is a place you ask. Ask how the refund policy works, what the onboarding steps are, or where the brand assets live, and Muse reads the wiki and answers in plain words with the page behind it. This is the use that saves a team the most time, because the same five questions stop landing on the same one person.

Project tracking without the status meeting

Ask Muse what is done, what is stuck, and what has no owner, and it reads the board and tells you. The Monday status meeting shrinks to the three moves that matter and the one question that needs a human. The board stays the source of truth. Muse just reads it out loud and flags what does not add up, like a task marked done that the notes say is still open.

Meeting notes into tasks

After a call, Muse reads the notes and turns each decision into a task with an owner and a date. The meeting stops evaporating the moment it ends, because the decisions land in the same place the work lives. Ask it to show you the tasks before anything is created, and approve them one by one the first few times.

Briefing a new teammate from your docs

When someone new joins a project, the first week is usually a pile of links and a request to read everything. Ask Muse to brief the new person instead: what the project is, what is done, what is stuck, who owns what, and which three pages to read first. The briefing comes from your docs, so it matches how the project actually runs, not how the handbook says it runs. The new teammate reads the briefing, asks Muse the follow up questions, and starts with context instead of confusion. Review the briefing yourself before you share it, because it will repeat whatever your docs say, including anything out of date. A briefing built on a stale doc is worse than no briefing at all, so this use is also the fastest way to find which pages need updating.

5. What to share and what to keep out

The sharing decision is the whole game with Notion. Share too little and Muse cannot answer. Share too much and you cannot reason about what it can see. Start narrow and expand at the speed of your actual use.

Share these first. Project docs, roadmaps, decision logs, meeting notes, onboarding pages, and the wiki pages your team actually reads. These are the pages that make Muse useful, and they are the pages with the least downside if Muse reads them.

Keep these out. HR notes, salaries, personal notes, customer personal data, passwords, and anything with financial account details. Not because Muse will misuse them, but because there is no reason for an assistant to see them, and every page you share is a page you have to reason about. If a question ever needs one of those pages, share that single page for that single question, then take the sharing back.

Review the list once a month. Open the sharing list and read it like a stranger would. Anything you would not explain to a new hire in one sentence should not be shared. Remove what you no longer use. The list shrinks over time, and that is a good sign: it means you learned which pages actually matter.

6. What to watch for

As of October 25, 2026, Notion is a settled connector for business accounts: named September 29, named again in the October 7 expanded list, and still listed in the October 15 in app check. There is no October update to how it works, so the habits around it still matter.

Stale docs are the first thing to watch. Muse reasons from what it reads, so an outdated page gives an outdated answer with total confidence. A roadmap that still lists a dead launch date will produce a plan built on that date. Keep the pages you share current, and treat the decision log as the one page that must never go stale. When Muse quotes a date or a decision, check it against the page before you act on it.

Permissions are the second thing. Muse sees what your Notion access allows it to see. If you cannot open a page in Notion, Muse cannot read it either. That is a feature: the sharing you set in Notion is the boundary, and Muse respects it. Do not work around it by sharing everything. The boundary is the safety.

Finally, keep edits on approval. The failure mode you want is a draft change waiting for you, not a page already rewritten. Ask Muse to draft the change and show it to you first, every time, until you trust the loop. Trust is earned by the loop, not granted on day one.

Get started

Frequently asked questions

What can Muse do with Notion?

Muse can read the pages and databases you share, then answer questions from them, summarize them, and turn decisions into tasks. Your docs become context Muse reasons from, instead of files you have to search yourself.

Can Muse change my Notion pages?

Treat anything that changes a page as approval first. Ask Muse to draft the change and show it to you, and keep approvals on ask me for anything that edits a page, creates a page, or changes a board.

Which Notion workspace does it connect?

The workspace on the Notion account you sign in with. Use the account that holds the docs that matter, and share only the pages on your short list to start with.

What if my Notion is a mess?

Connect one project first and let Muse show you where the mess hurts: duplicate pages, dead roadmaps, tasks with no owner. Clean the pages that drive the project first. A tidy project doc beats a perfect workspace you never finish.

Can I use it for a team?

Each person connects their own Muse account to Notion. The shared pages are the same for everyone, and each person decides what their own Muse can read. Keep the shared list narrow and review it once a month.

Is my private Notion data safe?

Muse sees what you share and nothing else. Keep HR notes, salaries, personal notes, and customer personal data out of the shared list. If a question ever needs one of those pages, share that single page for that single question.

Built with Muse is an independent community project. Not affiliated with or endorsed by Meta.