Use Google Drive with Ottermind: Find the Files and Prepare the Handoff

Bring the files for your next handover into one focused task in Ottermind. With a Google Drive skill configured, your agent can find accessible files, prepare supported exports, and help organize selected materials into a handover folder. You supply the source location and the outcome; the work starts from the files your team already has.

This is useful when “send over the project materials” involves several decisions: which version to use, which documents need a PDF copy, and how the recipient will know where to begin. A useful handover answers those questions as well as collecting the files.

The example below follows a fictional partner-onboarding handover. Its filenames, folder structure, and output tables are illustrative, not results from a connected Drive account.

Connect the account that holds your materials

Use the Google Drive skill published by byungkyu. This third-party skill connects through the Maton gateway. It requires a Maton API key and an active Google OAuth connection; other Drive skills may use different connection methods.

Add, enable, and bind the skill to the agent handling your task, following the Skills setup guide. Complete the selected skill's connection instructions, then give the agent a known folder URL and ask it to confirm the folder it can access.

That first request is particularly useful when the same project name appears in several places. Confirm the source before asking the agent to collect, copy, or rename anything.

Connection and file operations: Google Drive skill setup

Find the materials and make version choices visible

Suppose you need to hand over a partner-onboarding project. The source folder includes an editable brief, a slide deck, an older PDF, and a folder of workshop notes. Two filenames contain “final.” One of them was modified more recently because someone changed its title.

Start with an inventory. Ask for enough metadata to recognize the files and explain why they might belong in the handover. Google Drive supports searches by name, type, folder membership, and modification time, which can help narrow the set.

Finding files and folders: Google Drive search documentation

Prepare an inventory for the partner-onboarding handover from this folder:
[Drive folder URL]. Start with files directly inside it and list subfolders
separately so I can choose whether to include them.

For each candidate, return filename, file type, last-modified time,
and source link. Group similarly named files together and explain the grouping.
Identify version choices that need my decision. Do not assume that a file
is approved because it is newer or has "final" in its name.
Report any incomplete results. Do not move or rename files.

An inventory should help you choose. In the fictional folder, that could mean:

These are example distinctions, not retrieved files. They show why a file list and a version decision are separate parts of the work. Metadata can identify candidates; it cannot establish that a document has been approved by the project owner.

After selecting the source files, continue with a narrower request: “Use this brief and this deck. Exclude the older PDF. Include only the two workshop notes linked below.” That response gives the next step an explicit source set.

If you need to compare the actual contents before deciding, make that a separate reading task and confirm that the available tools can process the formats. The document analysis guide covers what to look for in that stage.

Prepare exports that match how the files will be used

An editable document is useful for the colleague continuing the project. A PDF is useful for a reviewer who needs a stable reading copy. The handover can include both, provided their relationship is clear.

Drive's export operation supports specific output formats for Google Workspace documents. Google Docs and Slides support PDF exports. An existing PDF is downloaded as a file; it does not need the same export operation as a Google document.

Choosing export formats: Google Workspace export formats

Prepare PDF exports of these approved sources:
[Google Docs brief URL]
[Google Slides deck URL]

Keep the source documents unchanged. Name each export after its source,
with today's date so we can identify this handover copy.
Return the files through the available delivery tools and provide an index
with source URL, exported filename, and export result for each item.
Report any failed or unsupported export. Do not share or send the files.

The index is part of the deliverable. It lets you trace the exported copy back to the document used to produce it, even if someone later changes the original.

Once the files are returned, open them. Check the brief's tables, the deck's slide edges, and any links the recipient needs. Some information belongs to the working environment rather than the exported page: a PDF copy should not be assumed to carry every comment or collaboration feature of its source.

If a file is too difficult to read in the chosen format, return to the specific source and decide whether a different export or the editable file is more suitable. Keep the successful exports in the index while resolving the exception.

Assemble a folder someone else can navigate

With the files chosen, organize around what the recipient will do. For this example, three sections are enough: read the brief, consult the reference material, and use the deliverables.

The selected Drive skill supports folder creation and file copying, moving, and renaming. For a handover assembled from active project files, copying can preserve the team's working originals. Name that choice in the request rather than leaving it implicit.

Plan a handover folder for this approved set of Drive files: [file URLs].
Use three sections: Brief, Reference Material, and Deliverables.

Show each source link, proposed destination, and proposed filename.
Plan to copy the selected source files, leaving the originals in place.
Flag ambiguous names and wait for my approval before creating the folders
or making copies. Keep sharing permissions unchanged.
After applying the approved plan, return the destination links and a list
of completed and incomplete operations.

Before approving the plan, look at it through the recipient's eyes. “Brief” should contain the starting point, not several competing versions. “Reference Material” should contain the notes that help explain the work. “Deliverables” should contain the selected project outputs, with names that distinguish their purpose.

For exported PDFs returned locally, confirm how they will enter the handover folder. The workflow above copies existing Drive files; placing a newly exported local file back into Drive also needs an available upload tool. If that is unavailable, keep the PDFs as separate delivered attachments and say so in the index.

A short handover note can then explain the package:

Start with the onboarding brief for scope and decisions. Use the review deck for the presentation. The reference folder contains the two selected workshop notes. PDF copies are listed separately in the export index.

This sample note gives orientation without repeating the contents of every file. Ask for a version tailored to the actual recipient and check that its links point to the completed destinations.

Folder creation and recipient access are separate. Before the handover is sent, confirm that the intended person can open the relevant files, and approve any specific sharing changes that are needed.

Start with one folder and finish with a clear package

A complete handover has a selected source set, readable outputs, and an explanation of where to begin. You can work toward all three in one conversation, reviewing the choices as they become concrete.

Open the Google Drive skill and bring the folder for your next handover. The Skills introduction explains how to make the capability available to your agent. The agent workspace guide connects this file work to the larger project you need to finish.