a founder
A week of replies drafted, none sent.
whyForty threads wait, and most need two lines.
asksDraft replies to this week's customer threads. I send them.
instibrain / works with / google apps script
Your Workspace, as you, through your script.
One script, deployed from your own Google account as a web app. It sees what you see, nothing more.
team/tools/google-apps-script/google-apps-script.md ids and key namesasked · an exampleDraft a reply to the Northwind thread with the latest invoice attached.
the AI, from the pageRead the thread, found invoice-0931.pdf in Drive, and saved a draft. It goes out when you say send.
who uses it, and why
Who hands the Workspace to the AI.
Mail, sheets and calendar, for people with no time for them.
the finance lead
The board sheet, filled by label.
whyMonthly numbers are copied in by hand.
asksAdd October's revenue to the Revenue row of the board sheet.
an assistant
A noisy sender, cleared out.
whyAn old supplier's notices bury the inbox.
asksTrash every mail from the old supplier.
what you can ask
Your AI runs your mail, sheets, Docs, Drive and calendar through one script.
Each action is one function, named for its service. Gmail, Sheets, Docs and Drive each have a page of their own.
Read and search your mail
Inbox, Gmail search, threads, SPF and DKIM verdicts, attachments to Drive.
Draft a reply, send on your go
A draft leaves only after you say send.
Read and write a sheet
Ranges found by label, dates as real dates, layout read first.
Edit a Doc without rewriting it
Insert after an anchor, fill one field, place an image.
Drive and shared drives
Search, sharing, folder copies, OCR, and conversions to native files.
Calendar events, listed and made
The coming days' events; a new one with guests, a place and a description.
where the credential stays
The script runs as you.
The script is yours, deployed by you, with a key you made.
in your Google account, and in your secret store
Deployed at script.google.com, as a web app that runs as you. Paste the new script, then make a new version of your existing deployment. The URL and the key stay.
in your brain
A page names the deployment id and the key's name, never its value.
what instibrain never touches
What the script never does.
The deployment runs in your account. Our server stores its id and key name.
- The key on a visible command line.
Read from the secret store inside the call.
- A send without your go.
It drafts, then waits until you say send.
- A retried write.
A doubtful response gets a read-back, never a second write.
the limits
Your AI stops where your Workspace admin says no.
It decides whether the script answers at all.
| Limit | What it means |
|---|---|
| An admin can forbid "Anyone" access | Then use a personal account, or Claude's Google connectors in Claude Code started in another folder. |
before you connect it
Your AI reaches what your Google account reaches, through a script you own.
Does instibrain have a Google integration?
No. You deploy the script, and it runs as you. The system carries only its source.
Can the AI send mail as me?
Only a draft you saw, and only after you say send.
What does the script reach?
What your account reaches. For raw files, the Drive folder is faster.
Your Workspace, no vendor in between.
Deploy once and name the key. Claude Code and Codex then work your mail and sheets as you.
documents and filesGmail
Search, threads, drafts and cleanup, a send only on your go, through your own script.
documents and filesGoogle SheetsFormats, formulas, tabs and real dates, through your own script.
documents and filesGoogle DocsDocs edited in place, the writer's text untouched, through your own script.
documents and filesGoogle DriveFiles, sharing and shared drives, through the folder and your own script.
documents and filesNotionPages and databases you can open, under your own token.
every kindWorks withEvery system by kind, and the rule each page shares.