> ## Documentation Index > Fetch the complete documentation index at: https://docs.aperium.apps.hillspire.com/llms.txt > Use this file to discover all available pages before exploring further. # Prep me for my next meeting > Google Workspace: stitch the invite, attendees, recent email, and the relevant doc into a one-page prep — from a single ask. You're two minutes from a meeting. You half-remember who's on it, there's a thread somewhere in your inbox about the topic, and the one doc with the actual detail is buried in Drive. Three separate hunts, under time pressure, right before you're supposed to sound prepared. This walkthrough uses Aperium's live connection to **Google Workspace** — Calendar, Gmail, and Drive at once — to turn those three hunts into one ask. Everything here is **read-only**: nothing is created, sent, or changed. A generic chatbot has never seen any of the three systems, so even if you paste in the invite, it still can't reach your inbox or your Drive to find the rest. For the why, see [Connected AI vs. a generic chatbot](/using/connected-ai). As Aperium works, look for a step showing it searching Calendar, Gmail, or Drive — a tool or action indicator, separate from its written answer. That's the sign each part is grounded in the real system. The exact cue depends on your Aperium build; if you're unsure, ask Aperium what it just did. ## The walkthrough Each step feeds the next — the whole point is that it's one continuous conversation across three systems, not three separate lookups you stitch together yourself. Ask it the way you'd ask a colleague who already had your calendar open: > What's my next meeting, and who's attending? Aperium searches your Calendar and returns the actual meeting — title, time, and attendee list — without you opening the calendar app or clicking into the invite. Reuse the attendees from the last answer without re-typing their names: > Pull the recent emails with those people about this. Aperium already has the attendees from the previous step, and now searches your inbox for the real threads with them on this topic — grounded messages, not a guess at what they probably said. > Find the most relevant doc in my Drive. Aperium searches your Drive for candidates, then opens and actually reads the most relevant one — real file, real content, not a filename guess. If it returns the wrong file, point it once — "try the one about \[topic]" — rather than reopening Drive to hunt yourself. This is the payoff — one ask that pulls all three together: > Put it together into a one-page prep. Aperium stitches the meeting, the email threads, and the doc into a single brief: what it's about, who's who, where things stand, and what's still open. One request reaching across three systems is something no generic chatbot can do, no matter how good the writing is. ## Before you walk in relying on it Because this build is read-only, the safety habit here is **verify before you rely**, not review-before-it-writes. Check the stitched brief against the actual calendar, emails, and doc before you walk in leaning on it. Confident isn't the same as correct — double-check attendee names, meeting times, and any recalled figure specifically, since those are the easiest details to get subtly wrong and the most likely to embarrass you if you repeat them out loud. * **It acts as you.** Aperium only sees what your own Calendar, Gmail, and Drive access allows. A missing thread or doc is probably a permission boundary or simply not shared with you — and the flip side is it can't see anyone else's mail or files either. For the habits that apply across every connector, see [Responsible use](/using/responsible-use). ## Try it yourself Think of a meeting you've walked into cold recently — where a two-minute prep would have changed how it went. Bring your own next real meeting and run this same four-step ask against Aperium before it starts.