How to Use the Slack Connector in Muse

1. The short answer

As of October 25, 2026, Slack is a live connector in Muse. Slack is team messaging: channels where a team talks in the open, threads where a discussion stays attached to its message, and direct messages between people. Meta named Slack on September 29, 2026, as one of the 15 business tools in the Muse for Small Business announcement, and it was still listed in the October 15 in app check, which counted 54 connectors in the web app. There is no October change to how it works. One honest caveat belongs right here at the top: Meta has not published a detailed list of what the connector can do inside Slack, so this guide describes team chat in plain terms, tells you exactly what is confirmed and what is not, and shows you how to read the permission screen on your own account before you trust it with anything important.

Here is the honest version. The Slack connector matters because team chat is where context lives now. Decisions get made in a channel at 4 pm, a question gets answered in a thread at 9 pm, and by Monday nobody can find either one. Search helps if you remember the words. It does not help if you remember the decision and not the words. A connector that lets you ask in plain words, what was decided in this channel, where did that thread land, and what do I need to know before the meeting, turns chat from a river you wade through into a memory you can ask. The rest of this guide covers how to connect it, the catch up prompt to run first, and the uses that are actually worth your time, with the limits stated plainly where the published record runs out.

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.
• One Slack workspace. The connector works with the Slack workspace you connect, and only that workspace. Pick the one where your team actually talks.
• Your Slack sign in. You connect with your Slack account, the same way you sign in to Slack itself.
• Approvals set to ask me. Before you connect anything, set approvals so nothing is posted, sent, or shared without your tap. This is the single most important step on this page, because a message in Slack is public to the channel the moment it lands.
• The channels that matter. Know the names of the channels where decisions happen. Muse works from what you name, so a wrong channel gets you the wrong conversation, and a vague channel gets you a vague answer. If your workspace restricts which apps can connect, ask your workspace admin before you plan around it.

3. How to connect it, step by step

The connection itself takes a few minutes. The setup around it matters more, because team chat holds other people's words as well as yours, so run the steps in order and read every screen before you accept it.

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 Slack in the connectors list and open it. If Slack 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. Click Connect and review the connection details. Read what Muse is asking for before you accept it. This screen is your source of truth for what the connector can do on your account, so read it slowly. If a scope surprises you, stop and check what it covers before continuing.
4. Sign in to Slack and authorize Muse. Use the Slack account tied to the workspace where your team works. Remember this is the one workspace the connector will use, so sign in with the right one the first time.
5. Open the connector settings and check each action. After you connect, look at the per action settings in Muse. Set anything that posts, sends, or shares to ask you first. If an action is listed that you do not want Muse to have at all, turn it off here rather than hoping you will remember later.
6. Set approvals to ask me. In Muse settings, set approvals so that anything that puts words into Slack waits for you. This is what stops Muse from ever posting a message you have not read.
7. Test with a read only request. Ask Muse what was decided in a channel you read yesterday. Read the answer against the channel. If it matches, the connection is good. Do not ask it to post anything on the first day.
8. Use it read only for a week. Catching up and searching only. Once you trust what it reads and how it describes your team chat, start approving one small post at a time.

Copy this prompt

You are my team chat assistant. Use my Slack connector only.
Rules: you never post or send anything in Slack without my explicit approval. You read, catch up, and summarize. I approve every post.
My channels: [name the channels that matter, e.g. general, product, support]
Every morning, do this in order.
1. Catch me up on each channel from the last 24 hours: the decisions, the open questions, and anything that needs me.
2. Flag anything where someone is waiting on me, and tell me who and what for.
3. If two messages disagree, say so plainly and show me both sides.
4. End with the 3 things I should answer first, in order.
5. If a quote matters, give me the exact words and who said them. Do not paraphrase quotes.

4. What it actually does

The connector earns its place with five uses. Everything else is a variation on one of them. One note of honesty runs through all five: the exact list of actions on your account is the one shown in your connector settings, because Meta has not published a full list for Slack. The uses below describe team chat as it works in practice, and the permission screen is the final word on your account.

Catch up on a channel after time away

Ask Muse what happened in a channel since yesterday, or since last Friday if you were away. This is the use that pays off every single morning, because the alternative is scrolling through hundreds of messages to find the five that matter. A good catch up tells you the decisions, the open questions, and anything that needs you, and it takes two minutes to read. Run it before your first meeting of the day, when yesterday is still close enough to act on. Our Gmail connector guide covers the same habit for your inbox, and our morning briefing guide puts mail, calendar, and chat into one briefing.

Find a decision, weeks later

Ask Muse what was decided about a named topic in a channel, and when. This is the use that ends the argument about what was agreed, because the channel is the record and Muse can find it. It also ends the quieter problem, which is worse: a decision nobody remembers making, so the team relitigates it every month. When a decision comes up again, ask Muse for the original thread first. If the thread shows the reasoning as well as the decision, you get the why back too, which is the part that usually gets lost first. Check the answer against the channel before you quote it as settled, because a summary can flatten a careful decision into a blunt one.

Find where a thread landed

Threads are where Slack hides its answers. A question gets asked in a channel, the discussion moves into a thread, and the answer sits at the bottom of it where nobody looks again. Ask Muse to follow a thread to its end: what was asked, what was said, and where it landed. This is different from searching Slack yourself, because Muse reads the whole thread and tells you the state of it, not just the messages that match a word. Use it when someone points you at a thread and says the answer is in there, and when a thread you started has gone quiet and you need to know whether it ended in a decision or just ran out of replies.

Prep for a meeting from what was actually said

Before a meeting, ask Muse what the channel said about the topic this week: the open questions, the disagreements, and the promises made. This turns meeting prep from a blank page into a short brief built from what your team actually said, which is a better brief than one built from memory. Pair this with the calendar side: our Google Calendar connector guide covers the day briefing, and Slack covers what the team has been saying about the things on it. The combination is a prep note that takes a minute to read and makes you the person who remembers, which is a rarer skill than it sounds.

Draft a post, then read it before it goes out

Ask Muse to draft an update, an announcement, or a reply to a thread, in your voice, from the context of the channel. The draft arrives for your approval, and the approval step is the whole point: you read, you edit, you post. The drafts get better over a few weeks because Muse learns from the edits you make and the posts you actually send. The failure mode to avoid is approving a draft you did not read. A post you did not read is a message you did not write, and in a shared channel the whole team sees it. Keep the approval setting on ask for every post, even the small ones, because the small ones are the ones that slip through with a wrong name or a wrong date in them.

5. What it cannot do

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

• It cannot tell you its full action list from a public page. Meta has not published a detailed list of what the connector can do inside Slack. The permission screen on your own account is the source of truth. If an action matters to you, check that screen before you plan around it, and do not assume a use exists because another connector has it.
• It cannot see channels outside the workspace you connected. Messages in another Slack workspace, another chat app, or a channel you never joined are invisible to it. It reasons from what you connected, nothing more. Our connectors list shows the other messaging tools Muse can reach if your team talks in more than one place.
• It cannot guarantee it caught every message. A catch up can miss a thread, and a summary can smooth over a disagreement. Check anything that touches a decision, a deadline, or an unhappy customer against the channel itself before you act on it.
• It cannot post 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 lands in a shared channel.
• It cannot replace asking the person. Muse can tell you what the channel said, but it cannot tell you what someone meant, or whether they have changed their mind since. When a message matters, ask the person who wrote it. A summary is a starting point for the conversation, not the conversation itself.

6. What to watch for

As of October 25, 2026, Slack is a settled connector: named on September 29 as one of the 15 business tools, 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. The most important habit is the approval habit. A message in Slack is public to the channel the moment it lands, and there is no recall that takes back what people already read. Keep every post on ask, and keep it that way even after you trust the drafts. Trust is not a reason to remove the safety net. It is the reason the safety net can stay quiet in the background.

Be careful with private channels and direct messages. They feel private, and in a sense they are, but a connector that can read them can also summarize them, and a summary forwarded to the wrong place is a trust problem. Set a rule for yourself about what Muse may read: the open channels where the team works, yes, and the private threads where people speak freely, only when you have a reason and you have read the summary first. If your workspace has rules about which apps can read which channels, those rules matter more than the defaults of the tool. A summary you share without that care is a trust problem waiting to happen.

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 team chat. That switch controls whether Meta may use your chats to train future models. And remember the account split when you plan: if your work chat and your personal chat live in different Slack workspaces, choose the work one for Muse and keep the personal one to yourself. That split is also good privacy hygiene.

Finally, verify the quotes. A channel summary is only as good as its quotes, and quotes are where small errors do the most damage. When a decision or a promise matters, open the channel and read the thread yourself before you repeat it to anyone. Muse is good at finding the passage. You are the one who decides whether it means what the summary says it means. That last check takes a minute, and it is the difference between a team that trusts its chat history and a team that argues about it.

Get started

Frequently asked questions

What can Muse do with my Slack workspace?

Muse can catch you up on channels, find decisions and threads, and draft posts in your voice for your approval. The exact list of actions on your account is shown in the connector settings, because Meta has not published a full public list for Slack. Read that screen before you plan around any action.

Which Slack workspace does Muse see?

Only the one you connect. Muse works with the channels available through that Slack workspace and the access you authorize. Messages in another workspace stay invisible to it, and you can manage or disconnect the integration at any time.

Can Muse post in Slack for me?

Only with your approval when your approvals are set to ask me. Set anything that posts or sends in Slack to ask first, and read every draft before it goes out, because a post lands in front of the whole channel the moment it is sent.

Can Muse read my private channels and direct messages?

Only what the connection covers. The permission screen on your account is the source of truth for what Muse can read. Treat private threads with care, and read every summary before you share it anywhere.

Can I use the Slack 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 Slack?

Muse loses access to that workspace. Your messages stay in Slack, and nothing Muse planned is carried out after you disconnect. You can reconnect the same workspace or a different one later.

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