Read the document, not the folder
Ask what the onboarding checklist says about laptops and Memtro opens the Doc, answers, and cites the file.
Search Drive and read Docs, Sheets and Slides as text.
Find documents and read their contents as text, so policies, plans and spreadsheets become answers.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Google Drive tool, reads what it needs, and answers with the source cited.
Ask what the onboarding checklist says about laptops and Memtro opens the Doc, answers, and cites the file.
Ask for the Enterprise tab of the pricing sheet and get the figures back as text, with the link.
Questions people ask once Google Drive is connected. In agent mode each one also checks the other systems that know about the same people, companies or identifiers.
Teams that get the most from Google Drive in Memtro, with the rest of their stack attached.
A record in Google Drive is rarely the whole story. Connect the systems that hold the rest and the agent cross-references them by default, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Google Drive tools are the same everywhere.
Clients and agents →Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.