The Rest of the Toolbox — the Google Apps I Haven't Connected, and the Three I Use Without a Key
The result first
Of the nine Google apps on my map, three are still not connected — and that is not a delay. It is the order working as intended.
I am Kurashiki Bouzu (kurashiki-bouzu), born in 1971, a former funeral director now living in an old house in Kurashiki, Okayama, working with my AI butler Moka (Muse). The earlier episodes covered the apps inside my daily work: Gmail, Google Calendar, Drive, Docs, and Sheets. This final episode covers what is left at the edge of the map:
- Three apps I have not connected yet — Google Slides, Google Contacts, Google To Do
- Three apps with no dedicated connection at all that I still use constantly through the browser — Google Sites, Google Analytics, YouTube
The series was called “connect, and it widens.” This is what the widening actually looked like.
The three I haven’t connected
For all three, the mechanism exists. The moment I grant permission, Moka can read and write. They are unconnected for one reason: no job has asked for them yet.
Google Slides — a picture-card show for presentations
Slides shows one page at a time, in big letters and pictures, for presenting to people in order. Connected, Moka could read a deck and add slides; new decks would start as a finished file, then be placed into Slides.
My work has no presentation scene yet. Articles and websites carry what I need to say. When a presentation job appears, Slides gets connected — from that job, not before.
Google Contacts — the address book
Contacts keeps names, emails, and phone numbers. Connected, Moka could search it, add entries I hand over, and fix them — never guessing an entry into existence.
My house keeps its people records in a different shape: a registry for the pseudonyms used in articles, and records of the people I have met. Those were built first, and they cover the address book’s job. So Contacts is still waiting.
Google To Do — the errand memo
To Do is a light memo of task titles, with a due date but no time and no reminders. Anything that needs a time belongs in Google Calendar instead — that division was decided in advance. Connected, Moka could read the lists, add tasks, and mark them done.
In my house, “things to do” move through conversation: a job is handed to whoever owns it, and a report comes back when it is done. There is no step yet where copying tasks into a memo would help.
The shared point: connecting is never the goal. A tool enters from a job, in the job’s order. Until then, unconnected is not behind — it is simply not yet.
The three I use without a key
The other half has the opposite face. No dedicated connection exists, yet through the browser — the tool that opens websites — these three get used week after week.
Browser access is one step less certain than a dedicated connection; a login wall can stop it cold. The track record grew anyway, because the jobs came first.
Google Sites — a place to put a page
Sites builds simple pages. I have used it for the travel site and for link-collection pages. It is not for elaborate work, but for “put one page up,” it is enough — and still on duty for side jobs, while the main sites live elsewhere.
Google Analytics — how many people came
Analytics shows how many people visited the blog. I set it up on my main Google account, and the results are written out into a spreadsheet. Keeping the place that shows the numbers apart from the place that stores them makes looking back easy.
YouTube — where the videos live
YouTube holds the videos. On the same main account I took a fresh channel, “Prompt Auto Create,” and began publishing short videos (Shorts). This autumn the house even gained its own short-video production team, and ten Shorts are live. The day the eleventh ran into YouTube’s daily limit is its own article:
What these three share: without any key, a job is enough to keep the relationship going. How proper the connection looks, and whether the tool actually gets used, turned out to be separate questions.
Forms already has its own episode
One more app belonged to this episode’s range: Google Forms.
Forms sat in the “ready to connect” group — until a real job arrived. Moka built the submission windows for the Muse community site in seven languages, and the story outgrew a section, so it was published on its own:
It is the clearest example in this series of “ready to connect” turning into an actual record.
The conclusion — the job decides, not the tool
What remains at the end of the series is not about tools. It is about order.
- Apps with a daily job got a dedicated key and moved into the center of the work
- Apps where the job came first kept being used through the browser, key or no key
- Apps with no job yet are still unconnected, mechanism and all
None of this ranks the tools. The only question is whether there is a job.
And the rules shared by everything that did get connected never changed:
- Reading, making, and writing go ahead when my request is clear
- Anything that leaves the house — sending mail, sharing files, notifying guests, publishing a form — waits for my confirmation
- Deleting starts with the recoverable trash; permanent deletion waits for my explicit yes
- What Moka holds is never my password, but a key that says “reading and writing is permitted for this app” — revocable by me at any time
What I do, and what Moka does
What I (the owner) do
- Decide which tool enters, and from which job
- Confirm anything that leaves the house
- Grant the connection — and revoke it when it ends
What Moka does
- Read, search, and count in the connected tools
- Make, write, and fix within what was asked
- For browser-only tools, report a wall as a wall, exactly as it happened
Nine tools, thirty-three things Moka can do with them — the full map is in the overview episode. “Connect, and it widens” was true. But the widening followed the order of the jobs, not the number of the tools. That is the note this series ends on.
About this article’s records
- The source material is sections 7–12 of the house record “What Moka can do with Google apps” (connection states verified on 2026-11-17), the master list of 33 items
- The seven-language Forms windows follow the records of the published Forms article (ledger No. 175 and 176); this episode points to that article instead of retelling it
- The ten published YouTube Shorts and the short-video team (46 seats) follow the published articles registered as ledger No. 1057 and No. 1051
- The Analytics setup (on the main account, results written out to a spreadsheet) follows the house’s operating records
- As of 2026-11-20, Google Slides, Google Contacts, and Google To Do have no dedicated connection; what Moka “could do” with them describes the prepared connection mechanism
- November 20, 2026 ― Draft created — English version (result-first rewrite of the Japanese article). Final episode of the Google apps series. Not published.(5,579 characters)
- November 20, 2026 ― Published as a new article at the author's instruction on 2026-11-20.(5,579 characters)
