Google Drive Integration
Your Playbooks in Google Drive Become Drills. Rory Only Answers From Them.
Made by
Secondbody.ai
Google Drive connector
Category
Documents
Used for
Building drills
Approved answers
Onboarding
Compliance
Users
Enablement
Managers
Field reps
33%
Parkingeye's top-usage division over target by May
8–10 / 10
GBUK cold-call scores for consistent users, vs 6
~1 week
Manager time GBUK gets back every month
0 days
Rentokil reps taken off the road to practise
Real results, real teams
See it in action
The playbook, the price list, the objection sheet, the clinical claims you are allowed to make. It is all in Google Drive already. Connect the folder and Rory reads it. A product document becomes a scored drill. An approved-answers sheet becomes what Rory says when a rep asks on the drive. Rory only knows approved content and refuses anything else. That starts with pointing him at the right folder. Edit the document once and the standard updates everywhere.
What is Google Drive?
Google Drive is the file storage inside Google Workspace. For most sales organisations it is where the enablement material actually lives: decks, playbooks, price lists, battlecards and the compliance documents reps are meant to have read.
Integration
What Data Do Google Drive & SecondBody Share?
Only the Folders You Point Rory At
SecondBody reads the files in the folders you connect and nothing outside them. Documents are used to build drills and to answer rep questions with a source. Your material trains no one else's model. Remove a file from the folder and Rory stops using it. No customer data is involved.
Folder-Scoped
Source-Cited Answers
Your Model Only
How Documents Become Drills
Point: connect the folder with your playbook, price list and approved claims. Build: Rory turns a document into a scenario with a scoring rubric in minutes. Run: reps drill it in WhatsApp, ask Rory questions on the drive, and get answers that cite the document they came from.
Document to Drill
Answers With a Source
