Review Gmail follow-ups
Connect Gmail read-only and prepare a weekday review of threads waiting on you and commitments without a follow-up.
The Gmail follow-up review template runs each weekday morning, reads the
threads under one label, and lists conversations where the last message came
from an external party too long ago with no reply, plus commitments made in
sent mail that have no visible follow-up. Each thread is cited by subject and
date with the ask summarized in one line and an owner proposed. It follows the
sales-enablement marketing skill: never let a warm thread go cold, and keep
every reply with a person.
Enable and connect Gmail
Gmail shares the Google Cloud OAuth client and Developer Preview status
described in
Digest source material from Google Drive;
an operator must configure GOOGLE_MCP_OAUTH_CLIENT_ID and
GOOGLE_MCP_OAUTH_CLIENT_SECRET before enabling MANAGED_MCP_GMAIL_ENABLED.
Then connect the Gmail card and authorize with your own Google account. Work
on Repeat requests only https://www.googleapis.com/auth/gmail.readonly, so
the connection cannot send, reply, forward, label, archive, or delete mail.
Google treats gmail.readonly as a restricted scope, so expect Google's app
verification requirements before a production client leaves testing.
Set the variables
| Key | Example | Why it is a variable |
|---|---|---|
mailboxLabel | Sales | Which label holds external conversations varies per mailbox, and it is also the routine's read boundary. |
waitingDays | 3 | How long a thread may wait before it counts depends on the conversation type. |
Reference them in the instructions as {{mailboxLabel}}, {{waitingDays}}.
Current beta boundary
Gmail is connection-only until exact authenticated tool schemas are captured and reviewed, so the packaged routine ships as a preview. Mailboxes contain personal data by definition, which is why even reads stay blocked until the review lands; the reviewed manifest should cover thread, message, and label reads only, and the routine's instructions already cite threads by subject and date and summarize each ask rather than reproducing messages.
Recovery
If authorization expires or is revoked, the connection moves to
reauthorization_required; reconnect the same card to update it in place.
The seven-day refresh-token expiry for a Google Cloud project still in Testing
applies here too.