How to Use the Google Forms Connector in Muse

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

As of October 25, 2026, Google Forms 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 build a form from a description, read the responses as they come in, and tell you what the answers actually say. It is a listening connector, not a writing connector, so it is at its best when the work is hearing from people and making sense of what they told you.

Here is the honest version. The Google Forms connector is the connector for anyone who needs answers from a group of people: customers, clients, students, event guests, and the team you keep meaning to ask. The value is not that Muse can open a form. Any browser can do that. The value is that Muse can do the two jobs around the form that people always skip: building the form well, and reading the answers properly. Our complete connectors list keeps the dated status of every connector, including which ones are announced but not yet live, so you can check Forms 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 forms you actually send out.
• Your Google sign in. You connect with your Google account, the same way you sign in to Forms itself.
• Approvals set to ask me. Before you connect anything, set approvals so nothing is changed in a form or shared with respondents without your tap. This is the single most important step on this page.
• Google Sheets, optional but useful. Form responses land in a sheet, so the Sheets connector is the natural partner when you want to work with the numbers behind the answers. Our Google Sheets 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 Forms in the connectors list and open it. If Forms 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 forms 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 forms and responses and to create forms 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 changes to a form and anything sent to respondents always wait for you. This is what stops Muse from ever changing a live form you have not reviewed.
6. Test with a read only request. Ask Muse to describe a form you know well: how many questions it has, what type each question is, and how many responses it has so far. Check the answer against the form 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 of forms and responses only, no edits to live forms. Once you trust what it reads and how it summarizes answers, start approving edits one form at a time.

Copy this prompt

You are my survey assistant. Use my Google Forms connector only.
Rules: you never edit a live form or send anything to respondents without my explicit approval. You build drafts, read responses, and summarize. I approve every change.
When I give you a form or an idea for one, do this in order.
1. Tell me what the form is trying to learn, in one paragraph.
2. List the questions that are unclear, the questions that ask two things at once, and the questions that can be cut.
3. Summarize the responses so far: the numbers, the patterns, and the three most useful answers in the respondents own words.
4. If a result surprises you, say so and tell me why before you draw any conclusion from it.

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.

Build a form from a description

Describe who you want to hear from and what you need to know, and ask Muse to draft the form: the questions, the question types, and the order they should appear in. This is the fastest way to build a survey, because the blank form is the barrier and the questions are the work. Keep the description concrete: who answers it, what decision their answers will drive, and the five or six things you actually need to know. A form built from a clear description needs light editing. A form built from a vague request needs a rebuild, so spend the time on the description and save it on the fix. When the draft is ready, read every question out loud and answer it yourself. If a question is hard for you to answer, it will be hard for your respondents too, and a hard question is a question people skip. Short forms get finished. Long forms get abandoned halfway through, and the answers you lose are the ones from the people who were too busy to finish.

Fix the questions that confuse people

Ask Muse to read your form and find the questions that will confuse respondents: the question that asks two things at once, the question with no good answer option, and the question that uses a word your audience does not use. This is the use that saves the most surveys, because a confusing question does not produce a confusing answer. It produces a wrong answer that looks clean. The rule to give Muse is simple: one question, one thing. If a question has an and in the middle of it, it is probably two questions wearing one question mark, so split it. If the answer options miss the option most people would pick, add it. A form that is easy to answer is a form that gets honest answers, and honest answers are the only ones worth reading. Test the form on one person before you send it to a hundred. The one person will find the confusing question in two minutes. The hundred will just give you wrong data.

Read the responses in plain words

Ask Muse to read the responses and tell you what they say: the numbers, the patterns, and the answers worth quoting. This is the single highest value use, and it is the one to build a habit around, because responses pile up unread in every business. A good summary tells you what most people said, what surprised you, and what to do next, and it takes five minutes to read. The rule that makes it safe is simple: every claim must name its source. Ask Muse how many people said it, and ask it to quote the three most useful answers in the respondents own words. A pattern backed by twenty answers is a finding. A pattern backed by two answers is a hunch. If a result surprises you, read the raw responses before you act on the surprise. The summary is a map, not the territory, and the answers that matter most deserve your own eyes.

Collect feedback after an event or a purchase

Ask Muse to build a short feedback form for the thing that just happened: the event, the course, the delivery, or the call. This is the use for the feedback you always mean to collect and never do, because building the form feels like work and reading the answers feels like more work. Keep it to five questions or fewer: what went well, what did not, what to change, and whether they would recommend it. Send it while the experience is fresh, not a week later, because the answers you get on the day are the answers you can act on. Our Gmail connector guide covers the other half of this habit, because the form usually goes out as email. The feedback you collect and read is worth more than the feedback you collect and file. Read it the day it arrives, and write down the one change you will make because of it.

Run a simple quiz or sign up

Ask Muse to build a form that does a job, not just a survey: a quiz with right answers, a sign up for a waitlist, or an order form for a small product. This is the use for the form that collects something and gives something back: a score, a place in line, or a confirmed order. Keep the job simple. A form that tries to do three jobs does none of them well, so pick one job per form and build it around that job. Tell Muse what happens after someone submits: what they see, what you receive, and what you do next. A form with a clear next step is a form people finish. A form with no clear next step is a form people abandon, because they cannot tell what their answer was for. Test it yourself end to end once before you share it, and fix the step where you got stuck, because your respondents will get stuck there too.

Track responses over time

Ask Muse to compare this month's responses with last month's and tell you what changed: which answer grew, which answer shrank, and what the trend looks like across the last few rounds. This is the use for the survey you run every month, where the value is not in one round of answers but in the direction they are moving. Use it on customer satisfaction, on team feedback, and on any question you ask more than once. The question to ask is not just what changed, but why it might have changed, and Muse can only answer the first half. The why is yours: the change you made, the event that happened, the season you are in. A trend without a cause is a curiosity. A trend with a cause is a decision. Write the cause next to the number, so the next person who reads it sees both.

5. What can it not do?

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

• It cannot guarantee a summary of responses is right. A summary can overstate a pattern, and a quote can be pulled from the one angry respondent while twenty happy ones go unmentioned. Check any claim that drives a decision against the raw responses before you act on it.
• It cannot see forms you never connected. Forms in other accounts, responses collected in other tools, and surveys run outside Google Forms are invisible to it. It reasons from what you connected, nothing more.
• It cannot replace your judgment on what a question should ask. Muse can draft questions and spot confusing ones, but it cannot decide what you need to learn or what decision the answers will drive. Those decisions are yours, and a form that asks the wrong questions will give you confident answers to questions nobody needed to ask.
• It cannot force people to answer. A form that nobody opens is a form with no data, and no connector can fix a survey nobody wants to take. The invitation matters as much as the form: who you ask, when you ask, and why they should bother.
• It cannot edit a live form or contact respondents 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 reaches the people answering.

6. What should you watch for?

As of October 25, 2026, Google Forms 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 survey around it, because rollout is staged and two accounts can see different lists on the same day. If Forms is not in your settings yet, there is nothing you broke. Check again in a few days.

Be careful with live forms. When a form is already collecting responses, an edit Muse makes is an edit every new respondent sees, and a changed question halfway through a survey splits your data into two sets that cannot be compared. Set a rule for yourself: never edit a live form mid survey. If a question must change, close the form, copy it, fix the copy, and send the new version. The moment you start approving edits to a live form without thinking is the moment the connector stops being an assistant and starts being a risk. This matters most for surveys you run more than once, where a changed question breaks the trend you were tracking.

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 forms and responses. That switch controls whether Meta may use your chats to train future models.

Finally, remember that Forms is a listening tool, not a numbers tool. When you need to work with the response data in depth, that is a Sheets job, because responses land in a sheet, and our Google Sheets connector guide covers it. When you need to turn what you learned into a document, that is a Docs job, and our Google Docs connector guide is the one to read. Keep the three connectors straight in your head: Forms is where answers get collected, Sheets is where numbers get checked, Docs is where words get written. The pairing is what makes each of them useful, and the habit of asking first and deciding second is what keeps your surveys honest.

Get started

Frequently asked questions

Can Muse build a Google Form for me?

Yes. Muse can draft a form from a description you give it, with the questions, the question types, and the order they should appear in. Read every question out loud and answer it yourself before you share the form.

Can Muse read my form responses?

Yes. Muse can read the responses to a form in the account you connect and summarize them in plain words. Ask it how many people said each thing, and to quote the most useful answers in the respondents own words.

Can Muse edit a live form?

It can propose edits, and it can carry them out only with your approval when your approvals are set to ask me. Never edit a live form mid survey, because a changed question splits your data into two sets that cannot be compared.

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

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

Are my form responses 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 forms and responses.

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