Google Drive integration for Ruby AI
The Ruby AI Google Drive integration is a two-way file connection scoped to the files you pick. Bring your own material into Ruby, a deck, a call summary someone pasted into a Doc, a security questionnaire, a pricing PDF, and send Ruby's output back to Drive when you want it filed where the rest of the team looks.
At a glance
What Ruby AI reads from Google Drive | What Ruby AI writes to Google Drive |
One file at a time, selected by you in Google's own file picker | A file you asked Ruby to save, in the folder you selected |
PDF, DOCX, PPTX, Markdown and plain text | A Ruby document you asked Ruby to export |
Google Docs, exported as text, and Google Slides, exported as PDF | Nothing else. Existing files are never modified |
Nothing you have not explicitly picked | Nothing is ever deleted, moved or renamed |
Why connect Google Drive to Ruby AI?
Analysis quality is bounded by what Ruby knows about your product. Loading five positioning documents once raises every answer after that.
Reps who keep a call summary in a Doc rather than a recorder still get the meeting analyzed.
Ruby cannot browse your Drive. The permission Ruby holds only covers files you explicitly select and files Ruby created.
How does Ruby AI use Google Drive?
Ruby uses the drive.file scope, Google's narrow per-file permission, documented in Google's Drive API scope guide. You pick a file through Google's own file picker and Ruby can then read that file, and only that file. Ruby cannot list, search or open anything else in your Drive.
At connect, Ruby verifies the Google account email matches your Ruby account email and validates the token before saving the connection.
What does Ruby AI put into Google Drive?
Two things, both initiated by you: a file you asked Ruby to save, uploaded to the folder you selected, and a Ruby document you asked Ruby to export, uploaded the same way.
Ruby never deletes, moves, renames or modifies a file that already existed in your Drive.
How do I connect Google Drive to Ruby AI?
In Ruby AI, go to Settings → Integrations → Google Drive.
Approve the drive.file scope on Google's consent screen. This is the narrow permission that covers only files you pick and files Ruby creates.
Choose a file through Google's picker and pick a destination: org knowledge, deal or account context, or a transcript.
Watch the Google Drive setup walkthrough. A short walkthrough of linking Google Drive so you can pull documents into Ruby without downloading and re-uploading them.
What can Ruby AI do with Google Drive?
Import a file into one of three places.
Org knowledge. Your product decks, positioning docs and battlecards become knowledge every agent can draw on across every account. Admin only.
Deal or account context. A file attached to a specific account or deal, so the analysis for that deal reads it.
Transcript. A text document imported as a meeting, which then runs the standard analysis chain: meeting analysis, stakeholder tracking, MEDDIC scoring, deal health, sales strategy.
Formats Ruby reads. PDF, DOCX, PPTX, Markdown and plain text. Google Docs are exported as text and Google Slides as PDF before Ruby reads them, so native Google files work without converting anything first.
Files are chunked and embedded on import, and Ruby returns the document ID, processing status and chunk count so you can see it landed.
Export Ruby documents back to Drive. Save a Ruby document to a folder you choose. Ruby records the export, so the interface shows which documents have already been sent to Drive.
Frequently asked questions
What permissions does Ruby AI need for Google Drive?
One scope, drive.file. It is Google's narrow per-file permission. Ruby can read a file only after you select it in Google's own picker, and can never list, search or open anything else in your Drive.
Can Ruby AI browse my whole Google Drive?
No. The drive.file scope does not allow it. Ruby sees a file only when you hand it over through the picker, plus files Ruby itself created.
What file formats can Ruby AI import?
PDF, DOCX, PPTX, Markdown and plain text. Google Docs are exported as text and Google Slides as PDF automatically, so native Google files work without converting them first.
Does importing a file cost credits?
Importing to org knowledge or deal context does not. Importing a file as a transcript consumes one meeting analysis credit, the same as any other meeting.
Does Ruby AI ever change or delete my Drive files?
No. Ruby only uploads new files you asked for. Files that already existed are never deleted, moved, renamed or modified.
Need help connecting Google Drive?
Open Learn Hub in the Ruby AI app for a step-by-step walkthrough, or use the support widget in the bottom-right corner of the app. You can also email the team at support@heyruby.io.
Related integrations
HubSpot and Salesforce, where deal context imported from Drive is applied
Google Calendar, which triggers the briefs that read your Drive knowledge