When should you use it?
- You already rely on a custom Gem for a repeated task
- Your account can open Workspace Studio
- The task starts from a Workspace event
Not for: Free personal Google accounts, which cannot use Workspace Studio; Gems that call external tools beyond your Drive files
What do you need, and what do you get?
You need
- A custom Gem grounded only in Drive files such as Docs, Sheets or PDFs
- Workspace admin approval for Gemini actions, if you are not the admin
- A trigger event and the follow-on apps
You get
- A running flow that invokes your Gem in the background
- Reply drafts waiting in Gmail for your approval
- Summaries in Docs templates and rows in tracking Sheets
How does it work, step by step?
- Check accessOpen studio.workspace.google.com; an error means a personal account or Gemini actions not enabled by your admin.
- Ground the Gem in DriveMake sure the Gem's knowledge comes only from Drive files, or it will not appear in Studio.
- Create a flow with a triggerStart from a template or describe the rule, such as a new email or form submission.
- Add Ask a GemUnder AI actions, choose Ask a Gem, connect your Gem, then chain actions that use its answer.
- Test, then turn onUse Test run to check the output, fix issues, and switch the flow on.
The prompt
Our own prompt, inspired by Amanda Caswell and written to work in Gemini. Values in lime are placeholders.
Gem instructions: You triage incoming [customer / vendor] emails for [team]. Use only the attached Drive files [policy doc, price sheet]. For each email return: category, urgency (high/normal/low), a two-sentence summary, the facts from our files that apply, and a draft reply under 120 words in our tone. If the files do not answer the question, say so and suggest who should reply. Never promise refunds, dates or prices that are not in the files.
Inspired by Amanda Caswell: I turned Gemini Gems into automated Google Workspace agents — here's how. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Keep the Gmail step at drafts so you review before anything is sent.
- Admin permission is the usual blocker at work; ask IT early.
Our take
Amanda Caswell of Tom's Guide shows a practical bridge from chat to automation for teams already on Google Workspace: a trigger such as incoming email runs an Ask a Gem step whose output feeds Gmail draft replies she reviews, summaries in Docs templates or parsed data in Sheets. Two setup gotchas, Drive-only grounding and admin enablement, will save people a confused hour. Judge it on a narrow first flow: one trigger, one Gem, drafts only. Measure whether the drafts need heavy edits before chaining more actions. Keep anything that sends externally behind your review. Confirm your Workspace admin has enabled the required features before investing time. Ground the Gem only in Drive folders that should influence replies. Test with a sample mailbox you control. Document which Gem version each flow uses so upgrades do not silently change tone. Revoke flows you no longer monitor. Log each flow run for a week and skim failures before expanding triggers.
Where the time goes back: A Gem you trust stops being something you open and paste into; the flow runs it on each event and routes the answer to where the work continues.
FAQ
Which Gems can be used?
What can the Gem's answer feed?
Source and credit
Inspired by Amanda Caswell. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- I turned Gemini Gems into automated Google Workspace agents — here's how
- Creator
- Amanda Caswell
- Published on
- Tom's Guide
- Original date
- May 27, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Gemini
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; nothing was sent, filed, purchased or published.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.