Skip to lesson
Exit
Use Google Workspace plugins1 / 2

1 min lesson

Read two Google sources, then approve one send

Read one signed-off Drive brief and one current Gmail thread, then review and verify one Gmail send.

Step 1 of 2

Open the official Google Drive and Gmail Marketplace entries. Confirm the creator, verification state, bundled MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. Press Enter for the full definition. actions and intended install scope, then install only those two entries. Connect the intended Google account and inspect the exposed tools and current approval mode. Keep Gmail send, label changes and Drive writes outside automatic approval. Search for the named release brief and customer thread. Open both, then record the file owner, message sender, dates and links. Draft the email without sending it. Check release claims against the merged change and tests, and check the customer answer against both Google sources. Finally, inspect the Gmail recipient, subject and body, approve one send and open the sent copy. Record that no Drive write or Calendar action ran.

Learn more

Full explanation

Official Drive and Gmail plugins, one reviewed write

Read two Google sources, then approve one Gmail send
Official Drive and Gmail plugins, one reviewed write
SayThe release email needs the signed-off Drive brief and the customer's open question from Gmail. It does not need a Calendar connection or permission to edit Drive.
DoOpen the Google Drive and Gmail Marketplace entries. Confirm that Cursor created and verified both entries, inspect their MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. Press Enter for the full definition. actions, choose the intended install scope and leave Calendar uninstalled.
SeeCustomize shows only Drive and Gmail for this workflow, at the scope you chose.
DoConnect the intended Google account to both plugins. Check the exposed tools and the current approval mode. Keep Gmail send, label changes and Drive writes outside automatic approval.
SeeThe account is correct. Search and read tools are available, while external writes still stop for review.
DoSearch Drive for the named release brief and Gmail for the customer thread. Open both sources and record the file owner, message sender, dates and links.
SeeThe brief is the signed-off version and the thread contains the current question. Each claim in the notes points to one of those sources.
DoAsk for an email draft only. Compare its release claims with the merged change and test evidence, then check the customer answer against the Drive brief and Gmail thread.
SeeThe draft is separate from the send action, and no Drive file, label or event changed while context was gathered.
DoOpen the proposed Gmail send arguments. Verify the recipient, subject and full body, then approve that call once. Search Sent and open the delivered copy.
SeeThe sent message matches the reviewed draft. Its Gmail record, source links and the absence of Drive or Calendar changes complete the handoff.
Learn more

Optional practice

Test yourself on Read two Google sources, then approve one send

QWhich result proves the Google Workspace release email was handled safely?