Moka Builds the Form — Google Forms and a Submission Window in Seven Languages
The result first
My community site has a submission window in seven languages — and Moka built every one of the forms.
The site collects real-world practice with Muse and Google apps, and readers can send in their own. The window for that is a Google Form: eight items, no email address collected, no sign-in needed. The first form was Japanese. Then Moka created the English, Chinese, Spanish, Korean, French, and German versions, same structure, wording remade naturally in each language.
I am Kurashiki Bouzu (kurashiki-bouzu), born in 1971, a former funeral director now living in an old house in Kurashiki, Okayama, working with Moka (Muse), my AI butler. After Gmail and the calendar, this third article is about the “question sheet” — and what Moka can do with it.
This episode is a rewrite. The article was originally planned as part of a later episode of the series, and was published on its own first, at my request. Now that the series’ overview episode is out, this version is aligned with the series as it stands. The map of the whole series is in the overview episode, “Everything Moka Can Do Across Google Apps.”
What a form is
A form is a sheet of questions.
Picture the application forms at a government office, or a survey on paper: a field for a name, choices to circle, a space to write freely. You fill it in and hand it to the window. That is a form.
Google Forms is that sheet kept on the internet:
- The sheet of questions is shared by a link
- Answers arrive and gather by themselves
- The gathered answers can be read one by one, or as a list, each tied to its question
It is free to use with a Google account. “Survey” sounds stiff; at heart, it is simply a sheet that asks what you want to ask and receives the answers.
What Moka can do in Google Forms
Moka connected to Google Forms with my permission on November 17, 2026.
Build a form
Moka can start from the title and line up the questions, choosing the shape of each:
- Short-answer and long-answer fields
- Pick one (radio buttons) or pick several (checkboxes)
- Choose from a fixed list (dropdown)
Each question can be set as required or optional.
Fix it afterwards
Questions can be added, and wording can be changed after the form is live. This actually happened: the first item originally used a word meaning “pseudonym,” and I had Moka change it to “Name (the name you would like to be called)” — my decision, so the window would never look like it was asking for a real name. Moka also added a short writing example to every item’s description, because “I don’t know what to write” is the biggest wall for a first-time submitter.
Publish — and stop
A form only accepts answers once it is published. Publishing and closing are operations Moka can do, but publishing faces outward, so it happens only after my confirmation.
Read the answers
Moka reads the responses tied to their questions — as a list, or one response at a time. That means “has anything new arrived?” is a question I can simply ask.
One honest limit: the header image and color theme of a form are beyond what Moka’s tools can touch. Those I set myself, on screen, in each language. A clear border between what Moka can and cannot do is, to me, a reassuring thing rather than a flaw.
The real example: the seven-language window
The community site is a place where practice with Muse and Google apps is gathered and kept. Its submission form has eight items:
- Name (the name you would like to be called — no real name needed)
- Shelf (which of the five shelves the practice belongs to)
- Title
- What you did
- Result or impressions
- Consent to be published
- A pass-word field, to show the form was read
- Site address (only for those who want a link)
There is deliberately no field for an email address, and no sign-in. A name you like is enough. And nothing that arrives is published automatically: every submission stops at my confirmation first. That “stop at confirmation” shape is the same house rule as checking an email before it is sent. The window still runs in the same shape as the day it was built.
What I do, and what Moka does
My part
- Decide what the window asks — the core of the items
- Confirm publication
- Set the parts Moka’s tools cannot touch, like the header image
- Confirm every submission before it is published
Moka’s part
- Build the form, line up the questions, fix the wording
- Remake the same structure in each language
- Read the gathered answers, tied to their questions
Building and fixing a sheet of questions takes more small work than it looks. When Moka carries that work, what remains in my hands is only the judgment: what to ask, and whether something may be published. A window is the entrance to a site — and Moka prepared that entrance in seven languages. That is the Google Forms combination.
- November 20, 2026 ― Re-draft created — English version (result-first rewrite of the Japanese article). The previous version (ledger No.176) was published on 2026-11-18. Not published.(3,906 characters)
- November 20, 2026 ― Published as a new article at the author's instruction on 2026-11-20. The previously published version remains untouched.(3,906 characters)
