How to Use the Google Slides Connector in Muse

1. What does the Google Slides connector do in Muse?

As of October 25, 2026, Google Slides is listed as a live connector in Muse. It entered the in app list by September 29, 2026, after the September 8 launch, and that September 29 listing is the latest named check for this connector, so the live status here rests on that September source. There has been no October announcement changing how it works: connect it and Muse can read your decks, draft new slides from an outline, and write speaker notes for the story you want to tell. It is a presentation connector, not a design tool, so it is at its best when the work is the story, not the pixels.

Here is the honest version. The Google Slides connector is the connector for anyone who has to present and hates the blank deck: the pitch, the team update, the client review, and the talk you keep putting off until the night before. The value is not that Muse can open a deck. Any browser can do that. The value is that Muse can work on the story with you, in plain words: outline it, draft the slides, write what you will actually say, and cut the slides that do not earn their place. Our complete connectors list keeps the dated status of every connector, including which ones are announced but not yet live, so you can check Slides against the rest of the list in one place.

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 do you need first?

• Muse access. You need an account with access first, in the United States, Canada, or Japan, where Muse has launched.
• One Google account. The connector signs in with Google, so use the account that owns the decks you actually present from.
• Your Google sign in. You connect with your Google account, the same way you sign in to Slides itself.
• Approvals set to ask me. Before you connect anything, set approvals so nothing is changed in a deck without your tap. This is the single most important step on this page.
• Google Docs, optional but useful. The story usually starts as a document before it becomes a deck. Our Google Docs connector guide covers that half.

3. How do you connect it, step by step?

The connection itself takes a few minutes. The setup around it matters more, so run the steps in order and do not skip the approvals step at the end.

1. Open Muse and go to Settings. The connectors list lives there. What is printed there is what your account has, because rollout is staged and two accounts can see different lists on the same day.
2. Find Google Slides in the connectors list and open it. If Slides is not listed, your account has not received it yet. There is nothing to install and nothing you broke. Check again in a few days.
3. Sign in with Google. Use the Google account that owns the decks you want Muse to work on. Pick the right one the first time, because switching accounts later means disconnecting and starting over.
4. Grant the access Muse asks for. Muse needs permission to read your presentations and to create and edit them on your behalf. Read the permission screen before you accept it. If a scope surprises you, stop and check what it covers before continuing.
5. Set approvals to ask me. In Muse settings, set approvals so that edits to a deck always wait for you. This is what stops Muse from ever changing a slide you have not reviewed.
6. Test with a read only request. Ask Muse to summarize a deck you know well: how many slides it has, what each section covers, and what the story is in one paragraph. Read the summary against the deck itself. If it matches, the connection is good. Do not ask it to edit anything on the first day.
7. Use it read only for a week. Summaries and drafts in chat only, no edits to live decks. Once you trust what it reads and how it structures a story, start approving edits one deck at a time.

Copy this prompt

You are my presentation assistant. Use my Google Slides connector only.
Rules: you never edit a live deck without my explicit approval. You read, outline, and draft in chat. I approve every edit.
When I give you a deck or an idea, do this in order.
1. Tell me the story of the deck in one paragraph: what the audience should think, feel, and do after it.
2. Outline the deck slide by slide, one idea per slide, with the point of each slide in one line.
3. Draft the speaker notes for each slide in plain words I can actually say out loud.
4. List the slides that can be cut, and tell me why each one does not earn its place.

4. What can you actually do with it?

The connector earns its place with six uses. Everything else is a variation on one of them.

Draft a deck from an outline

Give Muse a rough outline and ask for a slide by slide draft. This is the fastest way to beat a blank deck, because the outline is the thinking and the slides are the typing, and Muse does the typing. Keep the outline short: the point of the talk, who is in the room, and the three or four things they must remember when they leave. A deck built from a clear outline needs light editing. A deck built from a vague request needs a rebuild, so spend the time on the outline and save it on the edit. When the draft lands in Slides, read it once for story before you touch a single slide. If the story is right, the slides are easy to fix. If the story is wrong, no amount of slide polishing will save it. One idea per slide is the rule that keeps a deck readable. A slide with three ideas is a document pretending to be a slide, and the audience will read it instead of listening to you.

Turn a document into a deck

Ask Muse to read a document and turn it into a deck: the argument becomes the story, the key points become the slides, and the detail stays in the document where it belongs. This is the use for the report, the proposal, or the brief that now needs to be presented to a room. Our Google Docs connector guide covers the document half of this habit. The rule to give Muse is simple: the deck is not the document. A deck that copies every paragraph from the document is a document on slides, and nobody can read it and listen at the same time. Ask Muse to cut hard, keep one idea per slide, and put the numbers that matter on the slide in big type. The detail lives in the document. The deck carries the decision.

Write speaker notes you can actually say

Ask Muse to write speaker notes for each slide in plain words you can say out loud. This is the use that saves the most talks, because the difference between a good talk and a bad one is rarely the slides. It is whether the speaker knows what to say when each slide appears. The trick is to tell Muse how you talk: short sentences, plain words, no jargon you would never use in a room. Read the notes out loud once before the talk. If a sentence trips you up when you read it, it will trip you up in front of the room, so rewrite it until it reads like something you would actually say. Notes that sound like a script will make you sound like you are reading a script. Notes that sound like you will let you talk like you.

Tighten a deck that grew too long

Long decks hide their point under their own weight. Ask Muse to cut a deck by a third and keep every idea that matters. This is the use for the deck that has been edited by four people and now has forty slides for a twenty minute talk. Ask Muse to list the slides that can be cut, and to tell you why each one does not earn its place. A good cut reads like the same talk with the air let out. A bad cut reads like a talk that lost its argument halfway through. If the tightened version loses the slide your audience actually needs, put that slide back in and cut something else instead. Short is a means, not the goal. Clear is the goal. The audience remembers the talk, not the slide count, and a talk that ends early is a talk people thank you for.

Rehearse with questions from the room

Ask Muse to read your deck and play the audience: what will they ask, what will they push back on, and which slide is weakest. This is the use that turns a deck from a performance into a preparation, because the hard question is easy to answer when you have heard it once before the room asks it. Use it the day before the talk, not the morning of it, so you have time to fix the weak slide instead of just worrying about it. The rule is simple: a question Muse asks in rehearsal is a question you can answer with confidence. A question you first hear in the room is a question that owns the next five minutes. Write the answers in the speaker notes, not on the slides, so the room sees the story and you carry the answers.

Repurpose one deck into many

Ask Muse to take one deck and reshape it for a different room: the investor version, the team version, and the client version, each with the same story told at a different depth. This is the use for the deck you built once and now present five times a year to five different audiences. The story stays the same. The detail changes. The investor version leads with the numbers. The team version leads with the plan. The client version leads with the outcome. Tell Muse who the new audience is and what they care about, and ask it to say which slides to keep, which to cut, and which to rewrite. A deck that is reshaped for its audience is a deck that lands. A deck that is presented the same way to every room is a deck that lands in none of them.

5. What can it not do?

The limits are honest and worth knowing before you lean on the connector.

• It cannot design a beautiful deck for you. Muse can structure the story, draft the slides, and write the notes, but the visual design is still yours: the theme, the images, and the layout that makes a slide look good. A well structured deck with plain design beats a badly structured deck with beautiful design, but do not expect Muse to be your designer.
• It cannot see decks you never connected. Decks in other accounts, files on your computer that were never uploaded, and presentations in other tools are invisible to it. It reasons from what you connected, nothing more.
• It cannot guarantee it read a deck right. A summary can miss a slide, and a rewrite can soften a claim that needed to stay sharp. Check anything that touches money, a promise, or a number against the original deck before you present it.
• It cannot fix a talk with no clear point. If you do not know what the audience should think, feel, and do after the talk, Muse will produce smooth slides around a missing idea. The story comes first, and no connector can write it for you.
• It cannot edit a deck without your approval when approvals are set right. That is a feature, not a bug. If you turn approvals off, you lose the safety net, so keep them on for anything that changes a deck you will present.

6. What should you watch for?

As of October 25, 2026, Google Slides is a newer connector than Docs, Drive, and Sheets: it entered the in app list by September 29, 2026, and that September listing is the latest named check for this connector. Treat it as live, but check your own account before you plan a talk around it, because rollout is staged and two accounts can see different lists on the same day. If Slides is not in your settings yet, there is nothing you broke. Check again in a few days.

Be careful with shared decks. When a deck is shared with your team or a client, an edit Muse makes is an edit they see, and a changed slide in a shared deck is a changed slide everyone now presents from. Set a rule for yourself: Muse drafts in chat, you read, you approve, and only then does anything change in the shared deck. The moment you start approving edits without reading them is the moment the connector stops being an assistant and starts being a risk. This matters most for decks other people rely on, like the pitch and the client review, where a small change can create a big misunderstanding in the room.

Check your data controls. In Muse settings, open Data controls and look at the switch for helping improve the models. If you do not want your chats used for training, turn it off before you start asking Muse to read your decks. That switch controls whether Meta may use your chats to train future models.

Finally, remember that Slides is a story tool, not a design tool. When you need the numbers behind a slide, that is a Sheets job, and our Google Sheets connector guide covers it. When you need to find the deck in the first place, that is a Drive job, and our Google Drive connector guide is the one to read. Keep the three connectors straight in your head: Slides is where the story gets presented, Sheets is where numbers get checked, Drive is where files get found. The pairing is what makes each of them useful, and the habit of story first and slides second is what keeps your decks from becoming documents on a screen.

Get started

Frequently asked questions

Can Muse create a Google Slides deck for me?

Yes. Muse can draft a deck from an outline you give it, with one idea per slide, and save it to Slides in the account you connect. Give it a clear outline first, because a clear outline makes a far better first draft.

Can Muse edit my existing slides?

Yes. Muse can read a deck, tighten it, restructure it, and rewrite the speaker notes. Nothing is changed without your approval when your approvals are set to ask me, so every edit waits for your tap.

Can Muse write my speaker notes?

Yes. Muse can write speaker notes for each slide in plain words you can say out loud. Read the notes out loud once before the talk, and rewrite any sentence that trips you up.

Can I use the Google Slides connector outside the United States, Canada, and Japan?

Not yet. Muse itself has launched in the United States, Canada, and Japan only. Join the waitlist and we will send you a fresh code on launch day in your country.

What happens if I disconnect Google Slides?

Muse loses access to your decks. Your presentations stay in Google Slides, and nothing is changed after you disconnect. You can reconnect the same account or a different one later.

Is my deck content used to train Muse?

There is a Data controls switch in Muse settings for helping improve the models. If you do not want your chats used for training, turn it off before you start asking Muse to read your decks.

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