Documents and wikis connectors
Policies, specifications and runbooks, read where they live, with the thread that corrected them attached.
- Google DriveSearch Drive and read Docs, Sheets and Slides as text; write a Doc when you ask.Google sign-inHourly sync
- NotionSearch pages and query databases.Integration secretHourly sync
- ConfluenceSearch and read wiki pages.Site, email and API tokenHourly sync
- SharePoint and OneDriveRead the documents your company actually works in.Microsoft sign-inHourly sync
- GuruYour verified company knowledge, on handAPI keyHourly sync
- DropboxFind and read the files your team keeps in Dropbox.OAuth
- CodaRead your Coda docs, pages and tables without opening them.API key
The questions that cross systems
Most documents and wikis questions are only half answerable inside documents and wikis. These pairs are where the rest of the answer lives.
Who asks for this
- People and onboardingThe answers a new hire would otherwise ask around forPolicies, who owns what, how things are done and why: Memtro learns them from documents, conversations and the systems you connect, and keeps personal matters personal.
- OperationsMonitors and digests that run themselvesJobs are prompts the agent runs on a schedule with the same tools as their owner. Create them in plain language, get the report in a chat, pause or change them in a sentence.
- ProductHear what customers actually ask forFeature requests are scattered across tickets, call notes, Slack threads and issues. Memtro reads them where they live, links them to the customers who raised them, and remembers which decision closed each one.
Other categories
Connect one and ask it something
Seven days free. Connectors, jobs and memory are never metered, and model usage stays on your own provider keys.