How to Connect Gmail to Meta Muse (and Build Your Own Connector in an Hour)

Short answer: type 'Connect my Gmail' into Muse, or go to Settings → Connectors → Connect → Continue, then sign in with Google. Those are the two paths in Meta's help center, and either works. Before you do it, set Permissions to 'Always ask' so Muse asks before it sends anything. After you do it, know two things Meta's setup screen won't tell you: Muse deliberately can't read one-time codes in your inbox, and disconnecting later doesn't erase what it already learned. The second half of this guide covers building your own connector — which is genuinely an hour's work, with one important caveat about what Meta does and doesn't review.

Step by step

• 1. Lock permissions first. Settings → Permissions → Connectors → Always ask. The alternative, 'Ask for some actions,' asks 'before every write action and important read actions' — fine later, but start strict.
• 2. Connect. Either ask Muse — Meta's own example is 'Connect my Gmail' — or open Settings → Connectors, tap Connect next to Gmail, read the information screen, tap Continue, and complete Google's sign-in.
• 3. Check the read/write split. Meta: 'Many Connectors can also be set up so that Muse is only able to retrieve data, but not take actions.' If you only want Muse to find emails, look for that option during setup. Meta doesn't publish the exact Google permission scopes it requests, so we can't list them here.
• 4. Turn off training while you're in Settings: Data controls → deselect 'help improve our AI models.' It's on by default.
• 5. Test with a read, not a send. 'Find the confirmation email from my dentist' before 'Reply and reschedule.'

What Muse actually gets from Google

Meta's connector page says Muse 'won't download your whole inbox' — it searches when asked. Under the hood, per Meta's engineering post on Muse's security design, 'where the underlying service supports it, Muse separates out read and write access,' and it trims the permissions Google bundles together: 'if you grant Muse the Gmail read-access OAuth scope on the Gmail side, you can remove the ability to access Gmail settings that usually comes along with it.' Your OAuth tokens live in your own Secure VM, 'not in centralized Meta infrastructure,' and Meta commits to Google's Limited Use policy for Workspace data.

Your Google password never enters the picture — the connection is OAuth. For sites that don't support that, Muse keeps logins in a Secure Credentials Store so it can 'complete an authorized action without the AI model seeing your password.'

The one thing Muse can never read: your codes

This is by design and it will bite you. Meta's email connector 'filters out one-time tokens, password reset links, and login magic links via both deterministic filters and a classifier model' — so a hijacked Muse can't use your inbox to take over your other accounts. The consequence: Muse can't complete any sign-up or login that emails you a verification code. Ask it to create a DoorDash account and it will stall at the code step. One early tester's account of a DoorDash login describes exactly this shape of failure — Google kept asking 'is this you?', they kept confirming, 'and the whole process repeated three times after which I gave up.' Do sign-ups yourself; hand Muse the account afterward.

If the connection looks half-finished: Meta has no connector troubleshooting article yet. The one documented hiccup is cosmetic — a Sept 21 hands-on found 'one part still looked like Gmail needed to be connected while another part said it was connected. But it worked.' We've seen people on X describe the Google sign-in window closing before the connector finishes; we couldn't verify a cause or a fix, so the pragmatic move is to complete the connection once on muse.ai in a desktop browser and let it sync to the app.

It's not just Gmail

Meta publishes no connector list, which is why so many people assume it's Google-only. It isn't. Meta's Alexandr Wang listed Gmail, Google Calendar, Outlook, Plaid, OpenTable, Google Docs, Spotify, Function Health, Withings, Tailscale, and Peloton at launch; testers have since seen Outlook mail and calendar, Notion, and Google Forms in the menu. Facebook, Instagram, and Threads connect automatically if they share your Accounts Center. Payments aren't a connector at all — that's your Link by Stripe wallet, handled separately.

Disconnecting — and what Meta keeps

• In Muse: Settings → Connectors → Disconnect. Meta: 'Disconnecting stops Muse from exchanging data with the Connector. Information that Muse previously used to perform tasks with that Connector might still remain in Muse's memories and your conversation history.' Meta does not say it deletes what it already indexed.
• To actually forget: ask Muse to forget the interactions, or Settings → Data Controls → Reset Muse, which 'permanently delete[s] all information including chat history, files and active tasks.'
• On Google's side: myaccount.google.com/connections → Muse → Remove access. Do this too; it revokes the token regardless of what Muse's UI says.

Building your own connector: two very different things

On September 18 Zuckerberg opened the platform: 'You bring the API — Muse brings the agent, the browser, and the context of what the person actually wants.' But 'building a Muse connector' now means one of two things, and the difference is who checks the code.

The hour-long version, step by step

The cleanest public walkthrough is for connecting Muse to the Public.com brokerage, posted by @TarricSookdeo and matching Public's own guide:

• 1. Create an account at muse.ai.
• 2. In a new chat, send: 'Can you create a connection to the public.com API where the docs can be found here: public.com/api/docs'
• 3. Generate an API key in the service's settings and paste it when Muse prompts you — it goes into the Secure Credentials Store, not the chat.
• 4. Verify with a read: 'List my Public.com accounts.'

That pattern generalizes: give Muse a public API doc or an MCP server URL plus a key, and it writes the client. There's no 'add MCP server' setting — one team that pointed Muse at an MCP endpoint reports it 'wrote a client using the official MCP SDK, connected over streamable HTTP, listed the server's tools' and saved the result as a reusable skill. Developers on X report working connectors in about an hour. If you want yours in the directory for other people, that's the reviewed path at muse.ai/platform, and the submission form and terms are behind a login.

Top5Apps' take

The Gmail connection is the easy part; Meta did the security engineering — OAuth, scope trimming, code filtering — that a lot of agent startups skipped. Two things to carry with you: Muse can't do sign-ups for you, ever, and disconnecting isn't forgetting. On connectors, be clear-eyed about the custom kind: code Muse wrote from a random API doc, holding a key you pasted, reviewed by nobody. Use it for read-only services you'd trust a spreadsheet with. For anything that moves money, wait for the reviewed directory version. If you're still deciding whether to connect anything at all, start with Is it safe to connect Gmail and my bank to Muse?