How to Connect Muse to Your Apps

Muse is useful in a chat window, but it becomes something else once it can reach your apps. Meta calls these integrations connectors: each one you set up gives Muse a new ability, like reading your calendar, writing an email, or checking a storefront. Connecting an app takes a few minutes. The choices that matter are the permission ones, which is why this guide starts there.

Set Permissions Before You Connect Anything

Open Settings, then Permissions, before you connect your first app. For connectors, “Always ask” makes Muse check with you before acting; “Ask for some actions” only asks before write actions and important reads. While you are learning how the agent behaves, “Always ask” is the safer choice. You can loosen it later, connector by connector, once you have seen what each one does.

Many connectors can also be set so Muse only retrieves data and cannot take actions. A calendar connector can read your schedule without being allowed to send invites. An email connector can search messages without being allowed to send. Meta says Muse will not take many important actions, like sending an email, without your approval by default, and you can change when it asks in Settings. Start each connection at the least powerful setting that still lets you test the task you have in mind. (Our full walkthrough of these settings: Muse’s Sentinel Permissions, Explained.)

The Two Ways to Connect

The conversational route is one sentence. Tell Muse “Connect my Gmail” or “Connect my Shopify” and it starts the flow.

The manual route, from Meta’s help center, is four steps:

1. Go to Settings, then tap Connectors.
2. Tap Connect next to the connector you want and read the information.
3. Tap Continue to authorize the connection.
4. Follow any additional login or authorization steps, such as signing in to the app.

Step 2 is the one people skip. Each connector’s info screen tells you what you are granting: what data Muse will exchange, and whether the connector shares information proactively. Meta gives the calendar example: some calendar connectors update Muse automatically when your schedule changes, and the screen identifies connectors that do this before you connect them. Meta also says it designed connectors to exchange only the data needed for the task, so connecting email lets Muse search your mail without downloading your whole inbox unless you ask it to.

One more thing to read: the connector’s own terms and privacy policy. The connector is a third-party service, and its policies govern how it uses the information it receives. This is worth a minute, especially for apps that hold customer data or financial records.

Connecting Shopify, Notion, and Slack

These three are good examples because they cover the three shapes of connector, and Meta supports all of them. Notion arrived as a connector at Connect on September 23; Shopify and Slack came on September 29, when Meta added fifteen business connectors including Asana, QuickBooks, and Stripe under the Muse for Small Business banner. The setup flow is the same for each: Settings, Connectors, Connect, read the screen, authorize. What differs is what you are handing over and how you should scope it.

Shopify: the storefront. Connecting your store gives Muse context about what you sell and how orders are going. A sensible first task: “Summarize yesterday’s orders and flag anything that looks unusual.” Keep write actions approval-gated at first. Meta’s rule for the business connectors is that nothing publishes, sends, or spends without your approval, and a store is exactly the kind of place where you want that rule tested early, on small things, before anything touches inventory or customer records.

Notion: the knowledge base. This is the read-only showcase. Start with Muse only able to retrieve, and try: “What did our notes say we decided about the holiday hours?” Read-only keeps the risk profile simple while you learn how the agent interprets your pages. If you later want Muse to create or edit pages, raise the permission and watch the first few edits.

Slack: other people’s words. A Slack connector reads team communication, which means Muse will act on things your colleagues wrote. Start read-only with summaries: “Summarize what happened in #general today.” Be careful about scope creep here: a summary that names who said what is fine, but any action based on a Slack message deserves your explicit approval, because Muse cannot tell a joke from an instruction from a tired teammate.

For all three, the exact options vary by connector, so treat the setup screen as the source of truth for what each one can do and which permissions it offers.

Disconnecting and Starting Over

Every connection is reversible. In Settings under Connectors you can disconnect any connector at any time, and disconnecting stops Muse from exchanging data with it. Two things survive disconnection: anything Muse already used stays in your conversation history and its memories, so if you want that gone too, ask Muse to forget the interactions. This is also how you recover from over-connecting: add one app, use it for a week, and drop anything that did not earn its place.

A weekly review keeps the connector list honest. Open Settings, Connectors, and ask yourself two questions per entry: did Muse use this in the last week, and did the permission level match what it actually needed? Downgrade or remove the ones that do not have good answers.

When Your App Is Not Listed

If the app you want is not in the connector list, you can ask Muse to create a custom connector, and it will guide you through the process, which involves pulling API information from the service. Muse stores the credentials in its Secure Credentials Store. One caution straight from Meta: the company does not review custom connectors or how they use your information, so grant access with caution and review the provider’s privacy policy. For business apps with customer data, this is a decision worth making slowly.

Connect one app this week. Learn the approval rhythm with something low-stakes, check that the permission level matches what you actually use, then add the next one. The connector is the easy part. The settings around it are the whole game. Once you have a few connected, skills bundle them into reusable recipes. Meta’s connector platform is where developers are racing to add more.