> ## 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.

# Catch up on what I missed

> Google Workspace: summarize recent email and its action items, then find the latest relevant doc in Drive.

You're back from time away — PTO, travel, a heads-down stretch — and the inbox is buried. It's not that any single message is hard to read; it's the volume, and the one email that actually needed a reply is somewhere in it. Then there's the document everyone kept referencing while you were out, sitting somewhere in Drive.

This walkthrough uses Aperium's live connection to **Google Workspace** — your own Gmail and Drive — to cut through both. It's the first connector everyone already has: your inbox. A generic chatbot can summarize an email you paste in, but it can't see your inbox or your Drive, and when the problem is *too many messages to read*, pasting them one at a time defeats the point. For the why, see [Connected AI vs. a generic chatbot](/using/connected-ai).

<Info>
  As Aperium works, look for a step showing it searching your mail or Drive — a tool or action indicator, separate from its written answer. That's the sign it's reading the real thing, not guessing. The exact cue depends on your Aperium build; if you're unsure, ask Aperium what it just did.
</Info>

## The walkthrough

<Steps>
  <Step title="Summarize yesterday's email and pull the action items">
    Ask exactly what you'd ask a person — don't scroll your inbox first:

    > Summarize the emails I got yesterday about \[topic or from a person] and list the action items.

    Aperium searches your Gmail, reads the actual messages, and returns a summary plus a short action-item list — grounded in the real threads, not a guess at what an inbox like that usually contains.
  </Step>

  <Step title="Narrow to what actually needs you">
    Same conversation, one follow-up:

    > Which of these actually needs a reply from me?

    It doesn't restart — it narrows the batch it already has, separating the messages genuinely waiting on you from the FYIs and CCs. This is the moment it stops being a one-shot report and becomes a conversation over your real data.
  </Step>

  <Step title="Find the latest doc in Drive and summarize it">
    Different system, same pattern — no hunting through folders:

    > Find the latest version of \[document] in my Drive and give me a 5-bullet summary.

    Aperium searches your Drive, opens the file it finds, and summarizes what's actually in it. Spot-check a bullet against the document to confirm it found the right one.
  </Step>

  <Step title="(Optional) Draft a reply — then send it yourself">
    If one message needs a response, ask Aperium to draft it:

    > Draft a reply to \[the one that needs it].

    Aperium shows you a draft. **Nothing sends until you read it and send it yourself.** If the tone, a detail, or the addressee is off, correct it before you send — a draft is a draft.
  </Step>
</Steps>

## Before you trust or forward it

<Warning>
  A summary is a strong starting point, not a substitute for reading the actual message before you act on it or pass it along. Verify before you forward.
</Warning>

* **It acts as you.** Aperium only ever sees your own mail and Drive — never anyone else's. A missing result is usually a permission boundary, not a miss.
* **A draft is a draft.** Nothing sends and nothing gets created without your explicit send or confirm, every time — not just the first time.

For the habits that apply across every connector, see [Responsible use](/using/responsible-use).

## Try it yourself

Think of one email from this week you'd rather have summarized than read start to finish — then bring a real buried-inbox moment to Aperium and run this same pattern on it.