How to Use the Figma Connector in Muse

1. The short answer

As of October 25, 2026, Figma is a live connector in Muse. Connect it and Muse can read your interface design files, explain what a screen does, summarize a whole flow, and turn a pile of feedback into a list of fixes. That is the short answer, and it matters because design files are where product decisions go to hide, and the person who needs the answer is usually not the person who made the file.

Figma arrived on September 29, 2026, as one of the 15 business connectors in the Muse for Small Business launch, and it was named again in the October 7, 2026 iPad app launch and expanded connector list. Across Muse as a whole, an in app check on October 15 counted 54 connectors live in the web app, with about 58 to 60 live in total including phone only features, and 18 announced but not yet live. Our full connectors list keeps the dated picture for every connector, so check there before you plan a workflow around any single one.

Here is the honest version. Figma is where the product is designed, and Muse is where the design gets explained. The safe bet is the reading half: Muse can summarize a file you have not opened in weeks, walk through a user flow screen by screen, pull out the copy on the screens, and sort feedback into a punch list. The open question is the editing half. Meta has not published whether Muse can open a frame, edit a component, or change anything inside a Figma file, so nobody outside Meta can say for certain what happens inside Figma itself. Use Muse to read and explain, do the editing in Figma, and test the boundary yourself before you promise anyone a hands free design workflow.

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 Figma account with access to the file. The connector reads the files your Figma account can open, so sign in with the account that actually has access. A link alone is not access, and a file nobody shared with you is invisible to Muse.
• Your Figma sign in. You connect with your Figma account, the same way you sign in to Figma itself.
• Approvals set to ask me. Before you connect anything, set approvals so nothing is edited, moved, or deleted without your tap. This is the single most important step on this page.
• The question you actually need answered. What does this flow do, what changed since last week, what did the client ask for. A file without a question is a tour, and a tour is the slowest way to get an answer.
• Someone to act on the list. A designer to make the changes, or a developer to build them. Our GitHub connector guide covers the code half of the handoff.

3. How to connect it, step by step

The connection itself takes a few minutes. The setup around it matters more, because a design file is shared work and a wrong edit touches other people. 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 Figma in the connectors list and open it. If Figma 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 Figma. Use the account that has access to the files you want Muse to read. If you have a personal Figma account and a work one, pick the work one the first time.
4. Grant the access Muse asks for. Muse needs permission to read your Figma files. 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 anything that edits, moves, or deletes always waits for you. This is what stops Muse from ever touching a shared file without your say.
6. Test with a read only request. Ask Muse to describe one file in a paragraph and list the screens in it. Read the answer against the file in Figma. If it matches, the connection is good. Do not ask it to change anything on the first day.
7. Use it read only for a week. Summaries, explanations, and punch lists only. Once you trust what it reads, test one small editing step if you need it, and watch exactly what it does before you trust a second one.

Copy this prompt

You are my design review assistant. Use my Figma connector only.
Rules: you never edit, move, or delete anything in Figma without my explicit approval. You read, summarize, explain, and list. I approve every change.
My file: [the name of the Figma file, and what it is for]
My product: [what the product does, who uses it]
Do this in order.
1. Summarize the file in one paragraph: what it covers and what it does not cover.
2. List the screens in order, with one line each saying what the screen does.
3. Walk through the main user flow screen by screen, and flag any step that looks confusing or missing.
4. Pull out the words on the screens: button labels, empty states, and error messages, and flag any that sound unclear.
5. End with the 3 fixes that matter most, in order.

4. What it actually does

The connector earns its place with six uses. All six are reads and explanations, and they are the ones to build a habit around. If Muse can also edit, that is a bonus you test later, not the reason you connect it today.

Summarize a file you have not opened in weeks

Ask Muse to describe a Figma file in one paragraph: what it covers, what it does not cover, and how many screens it holds. This is the use that saves the most time, because design files grow quietly and nobody remembers what is inside them. A new teammate, a returning founder, or a client who wants a status update all need the same thing, and it is a summary, not a tour. The summary should name the parts of the product the file covers and the parts it leaves out, because the gap is where the next question lives. Keep the summaries and compare them over time, because a file whose summary keeps changing is a product whose scope keeps moving, and that is worth knowing before the next planning meeting.

Explain a user flow screen by screen

Ask Muse to walk through a flow in order: the screen the user lands on, the choice they make, the screen that follows, and the step where they finish. This is different from clicking through the file yourself, because Muse tells you the logic of the flow in words, and words are what you argue about in a review. The question to ask is where the flow breaks: a step with no way back, a choice with no clear next screen, a dead end that nobody noticed. Flows break quietly, one small change at a time, and a screen by screen walk is the cheapest way to find the break before your users do. Read the walk against the file before you act on it, because a flow Muse misread is a fix aimed at the wrong screen.

Turn feedback into a punch list

Feedback arrives as a pile: a client email, a call transcript, a dozen comments scattered across frames. Paste the feedback into Muse and ask it to turn the pile into a punch list, one fix per line, grouped by screen, with the exact words the client used next to each fix. This is the use that turns a messy review into a morning of work. The rule is that every item on the list traces back to something the client actually said, and anything Muse added on its own gets flagged as its own suggestion, not as client feedback. A punch list that mixes client words with assistant guesses is a punch list that ships the wrong fixes, and the fix for that is to check each item against the source before you hand the list to a designer.

Draft the words on the screens

Buttons, empty states, error messages, and onboarding lines are the words users actually read, and they are usually written last, in a hurry. Ask Muse to pull the words off the screens and rewrite the ones that sound unclear, in the same voice as the rest of the product. The question to ask is not just make this clearer, but make this clearer for a first time user who has never seen this screen. A first time user has no context, and the copy has to carry all of it. Keep the rewrites short, because a button label that runs long is a design that breaks, and a long error message is an error message nobody reads. Read every rewrite on the screen itself before you accept it, because words that read well in a chat can still look wrong in the layout.

Spot what changed since last week

Ask Muse what changed in a file since the last version, and what the change means for the product. This is a question to ask with care, because version comparison is a harder read than a summary, and Muse may miss a change or misread one. Use its answer as a starting point and check it against Figma version history before you report the change to anyone. The value is not a perfect diff. The value is a short list of places to look, instead of opening the whole file and hunting. When a change matters, ask Muse to explain why it matters in plain words, because a list of changed frames is a fact and an explanation of the change is a decision, and decisions are what your team actually needs.

Handoff notes for developers

Ask Muse to write the handoff notes for a flow: what each screen does, what happens when the user taps each button, and what the edge cases are. The notes go to the developer who builds the flow, and they should be specific enough that the developer never has to guess what a screen is supposed to do. This is where the connector pairs with code. Our GitHub connector guide covers the side where the code lives, and the handoff notes are the bridge between the two. Send the notes, not the chat. Copy the notes out of Muse and hand them over as a finished document, because a chat transcript is not a handoff and nobody builds from a transcript.

5. What it cannot do

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

• It cannot be relied on to edit a Figma file until you have seen it do so. Opening a frame, editing a component, and moving an element are editing actions, and Meta has not published whether Muse can take them. Test one small editing step with approvals on ask me and watch what it does before you trust a second one.
• It cannot see files you have no access to. Files nobody shared with your Figma account, files in another workspace, and files in a personal account you did not connect are invisible to it. It reasons from what your account can open, nothing more.
• It cannot guarantee it read the latest version. A file changes while you are asking about it, and a summary can describe the version from an hour ago. Check anything that drives a decision against the file itself before you act on it.
• It cannot replace design review judgment. Muse can explain a flow and flag a confusing step, but it cannot see the design the way your user will. Open the screens yourself and click through the flow with fresh eyes before you sign off on it.
• It cannot export assets or hand off specs by itself. Whether Muse can pull assets or specs out of a file is unverified, so treat exports as work that happens in Figma until you have seen Muse do it.
• It cannot fix a messy file. If the file is a pile of unnamed frames with no structure, Muse will summarize the pile. Tidying the frame names and the page structure first makes every answer after it dramatically better.

6. What to watch for

As of October 25, 2026, Figma is a settled connector: live since September 29, named again on October 7, and still on the list in the October 15 in app check. There is no October update to how it works, so the habits around it matter more than the news. Check every summary against the file for the first week, especially any claim about what a flow does. A wrong read acted on fast is worse than a slow read you verified.

Be careful with shared files. A Figma file is shared work, and a change touches other people. Keep anything that edits, moves, or deletes on ask me, and keep it there even after you trust the loop. The failure mode you want is a punch list waiting for you, not a frame already moved. If Muse ever offers to change a file you did not ask it to change, say no and check what it was trying to do. A connector that touches shared work deserves more caution than one that reads your own notes, not less.

Elsewhere on the list, PayPal was announced on September 22 and its October live status is unverified, so do not plan a workflow around it yet. Amazon has no connector and none is expected. If a tool you need is not on the list at all, ask Muse to build a custom connector: any service with a public API can be connected that way, and Meta does not review custom connectors. Our connectors list keeps the dated status for all of these, so check there before you build on any single claim.

Finally, 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 client design files. Client work deserves that decision made deliberately, not discovered later.

Get started

Frequently asked questions

Can Muse edit my Figma files?

That is the honest gap in this guide. Meta has not published whether Muse can edit frames or components in Figma, so use Muse to read and explain first, and test one small editing step yourself. Do not promise anyone a hands free design workflow until you have seen it work.

Can Muse see a file I only have a link to?

Only if your connected Figma account can open that file. A link alone is not access, so check the file sharing settings in Figma first. If your account cannot open it, Muse cannot see it either.

Does it work with FigJam or only Figma design files?

We could not verify whether the connector covers FigJam boards as well as Figma design files. Ask Muse what it can see and check the answer against your own account before you plan a workflow around FigJam.

Can Muse hand work to developers?

It can draft handoff notes that describe each screen and each interaction in plain words. The building itself happens in code, and our GitHub connector guide covers the side where the code lives.

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

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

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