How to Connect Multiple Google Drive Accounts to Grok
Grok has a real Google Drive connector, it is free and self-serve on every consumer tier, and xAI documents writes as well as reads: search, read contents, create Google Docs, make folders, upload files. Set it up at grok.com/connectors in about a minute. Drive also escapes the caveat that catches its Microsoft cousins, since it is not in xAI’s “requires additional admin setup” table. The catch is narrower than the usual one: one Google account is well covered, while a second Google account is something xAI does not document at all. Carly holds your OneDrive accounts, and every mailbox and calendar on both sides, in the same place.
One orientation note first. “Grok” now names three products: the consumer assistant at grok.com and in the mobile apps, Grok Bot for Slack and GitHub, and the Grok API. This page is about the first one. There is also a fourth surface that confuses Drive searches specifically, covered two sections down.
Gmail, Calendar and Drive are three connectors, not one
This trips up more people on Drive than on anything else. xAI’s connector documentation treats Google Drive as its own built-in connector with its own OAuth sign-in, picked separately in the New Connector list alongside Gmail and Google Calendar. Connecting Gmail gives Grok your mail and nothing else.
The reason this bites hardest on Drive is a stale xAI post. The May 2026 connectors announcement says “Google Workspace: Connect Gmail, Drive, Docs, Sheets, and Calendar with one integration”. That is no longer how it works. The current documentation splits those into separate connectors with separate sign-ins, so if you followed the old post you connected one thing and are now wondering why Grok cannot find a spreadsheet. That post’s interface path is stale too: it says click the + button, select Connectors, then + Add connector. On grok.com today it is New Connector. A tour of the whole set is in our Grok connectors overview.
On Grok Business and Enterprise, xAI states that a team admin must provision a connector in the cloud console before it is available to members of the organization, which needs Team Read-Write permission at console.x.ai under Grok Business then Connectors. Worth noting precisely: + Add Connector does exist, but only there, in the admin console, not in the consumer interface.
Drive gets an easier ride than its Microsoft cousins on those plans. xAI’s documentation carries a table of connectors that require additional admin setup, and that table lists SharePoint, OneDrive and Salesforce. Google Drive is not on it, so Drive needs plain provisioning and no separate consent flow. The privacy line is specific too: nothing is stored, Grok accesses your data in real time when you ask a question, and does not retain it afterward.
The Grok add-on for Google Workspace is a different thing
If you searched for Grok and Google Drive you may have landed on the add-on instead. xAI shipped a Grok add-on for Google Workspace in July 2026, a free add-on where one install from the Marketplace covers Sheets, Slides and Docs. That puts Grok inside those editors, which is the opposite direction to the connector. They are related, since xAI says the add-on can pull from recent emails or files in Google Drive with connectors enabled, but installing one does not set up the other.
Which verbs are documented
xAI lists the Drive capabilities one by one, and the list is unusually concrete.
| Action | Documented? |
|---|---|
| Search files by content keyword or title | Yes, across Docs, Sheets, Slides and other file types |
| Read file contents to summarize or analyze | Yes |
| Create and write files, including new Google Docs | Yes |
| Create folders and list folder contents | Yes |
| Filter by starred, shared, modified-after or a folder | Yes |
| Upload artifacts Grok generates into any folder | Yes |
| Delete a file | Trashing only, no permanent-delete language |
| Move or rename an existing file | Not documented |
| Share a file or change permissions | Not documented |
Two rows matter more than they look. On delete, xAI’s wording is “trashing files”, so plan on recoverable removal rather than destruction. On sharing, there is no share or permissions verb anywhere on the page, so do not build a handover workflow that assumes Grok can grant someone access.
Write access arrives as an optional OAuth scope, described as creating and modifying files in your Drive. This is where Drive genuinely differs from its siblings. On Gmail and Google Calendar, xAI describes writes as enabled progressively by an organization’s administrators. No such progressive admin gating is documented for Drive. It is presented as an optional scope you accept at sign-in. Whether you can decline it and keep a read-only Drive connection is Google’s standard behaviour for optional scopes rather than something xAI states, so check the consent screen you actually get.
A second Google account has no documented slot
Nobody at xAI has written down what happens when you add Google Drive as a connector twice. It may attach a second identity, it may replace the first, it may refuse. The documentation is silent on all three outcomes, and two nearby signals lean singular without proving anything: the scope table requests userinfo.email always, to identify your Google account, and the page says Grok can only access files that the signed-in Google account has access to.
Read that second signal carefully, because it is easy to over-read. It constrains which files one connection reaches, and says nothing about how many connections you can hold. So this is genuinely undocumented, not a documented refusal. Try it if you like, then plan around folder sharing, because that path is the one xAI’s own capability list supports.
Nothing fires when a file lands
Since July 2026 Grok can start work on its own two ways: a schedule, or an incoming email that matches your filters. Email is the only event it watches. The connectors it has to Salesforce, Teams, SharePoint, and the rest never fire anything — they wait to be asked inside a conversation.
Be precise about what that leaves for Drive. There is no Drive trigger and no file trigger in any xAI document, so nothing happens when a file is uploaded, edited, renamed or shared with you. A share notification usually arrives as an email, so an email trigger reaches the notice indirectly on SuperGrok, not the file event itself. A colleague editing a shared budget in place generates nothing Grok can react to. Our Grok Automations page has the full trigger picture.
1. Sort your case
| What you have | Native path in Grok |
|---|---|
| One Google account, many files and folders | Yes, search and read both documented |
| A folder someone shared with your account | Yes, and “shared files” is a documented filter |
| Two separate Google accounts | Not documented either way |
| Creating docs, folders and uploads | Yes, with the optional write scope |
| Moving, renaming or re-sharing a file | Not documented |
| Permanently deleting a file | Trash only |
| Shared drives and Team Drives | Not named in the documentation, unverified |
| Reacting when a file changes | No file trigger, email triggers only, SuperGrok only |
2. Connect Google Drive in Grok
- Go to grok.com/connectors on the web, or Settings then Connectors on iOS and Android.
- Click New Connector.
- Select Google Drive, not Gmail and not Google Calendar, unless you want those too.
- Sign in with your Google account.
- Review the requested permissions and click Allow.
- Accept the optional write permission here if you want Grok to create files, make folders or upload its own output.
- On Grok Business, ask an admin to provision the connector at console.x.ai first.
To undo any of it: disconnect at grok.com/connectors, or revoke from myaccount.google.com/permissions.
3. Pull the second account in by sharing
There is a documented reason to believe in this rather than pure guesswork. xAI wrote two different sentences on neighbouring pages. The Drive page says Grok can only access files that the signed-in Google account “has access to”. The OneDrive page says Grok can only see files in “your own” OneDrive, “not files belonging to other users”. Restrictive phrasing for one, permissive for the other, side by side, which looks deliberate. The consequence is still an inference, so verify it.
- Open Google Drive signed in as the second account.
- Right-click the folder you need and choose Share.
- Add the Google address you connected to Grok.
- Pick the access level you actually want, Viewer or Editor.
- Accept the share from the connected account so it lands in Shared with me.
- Ask Grok for one file in that folder by name and confirm it can read the contents.
Step 6 is not optional. It is the entire verification for an inference rather than a documented feature. Shared drives are a separate question: xAI does not name shared drives or Team Drives anywhere on the Drive page, so nothing here promises they work.
4. Ask before you instruct
Retrieval questions map onto verbs xAI actually documents:
Search my Drive for the Q3 pricing deck and summarize the pricing section.
List the files in my Client Contracts folder that were modified after July 1.
Then the documented filter, which is what makes the sharing workaround checkable:
Show me the shared files in my Drive and say which account shared each one.
5. Connect each Google account to Carly
- Sign in at carlyassistant.com.
- Open carlyassistant.com/integrations.
- Find Google Drive and click Connect.
- Authorize the first Google account.
- Repeat for every additional account, personal, freelance or Workspace.
- Confirm each one appears in the connected list before you rely on it.
No sharing step, and no Drive permissions to maintain and later remember to revoke.
6. Add Carly to Grok
- Go to grok.com/connectors.
- Click New Connector, then select Custom.
- Enter
https://carlyassistant.com/mcp/. - Complete the authentication step.
- Sign in to the Carly account holding the connections above.
Grok discovers the tools Carly exposes and offers them in conversation alongside its built-in connectors. On Grok Business and Enterprise a team admin provisions connectors in the cloud console first.
7. Test each account, then both at once
One account per prompt until the routing is reliable:
In my personal Google Drive, find the tax folder and list everything filed for 2025.
Then the question that needs two real connections rather than a share:
Compare the invoice templates in my personal and work Google Drives, name the account each one came from, and save the differences to a new doc in the work account.
8. Reuse this routing prompt
Treat my Gmail account as Personal and my Workspace account as Work. Always say which Drive you are writing to before creating, uploading or trashing anything, and never write to a Drive I have not named.
Then name the target per action:
Save the Wells Fargo reconciliation to Work in the Finance folder, and put the house survey in Personal.
Grok versus Carly on Google Drive
| Need | Grok | Carly |
|---|---|---|
| Search and read one account’s Drive | Yes | Yes |
| Free connector on the entry tier | Yes | Yes |
| Extra admin consent on business plans | Not required for Drive | Not required |
| Hold two Google accounts as separate connections | Not documented | Yes |
| See a second account’s files | Via Google folder sharing | Directly |
| Create docs, folders and uploads | Yes, with the write scope | Yes |
| Move or rename an existing file | Not documented | Yes |
| Act when a file lands or changes | No file trigger | Yes |
Grok’s Drive connector is free on every consumer tier and covers search, read, create, folders and upload on the account you sign in with, with a trash-not-delete boundary stated plainly. It holds that one account.
Carly is built for the parts Grok leaves undocumented. It authorizes per identity, so a personal Drive and a Workspace Drive sit side by side as separate connections rather than as a sharing arrangement someone has to maintain, and one question can span both. It also acts on the event rather than on a clock: the file lands in the shared folder, the numbers get pulled, the summary is in your inbox before you have opened Drive. If you need something beyond the native connector list, the API path is available and worth a conversation.
Free Zapier-style workflows; AI agents from $35/month. Connect it on the integrations page, or start with Google Drive.
Quick fixes
| Problem | Fix |
|---|---|
| Connected Gmail, Grok cannot find a file | They are separate connectors; add Google Drive as its own New Connector |
| The guide you followed promised “one integration” for all of Workspace | That is xAI’s May 2026 news post; the current docs describe three separate connectors and match the live interface |
| No + Add connector button on grok.com | The consumer path is grok.com/connectors then New Connector; + Add Connector only exists in the console.x.ai admin console |
| Grok will not create a doc or upload anything | The write permission is an optional scope at sign-in; disconnect and re-authorize accepting it |
| Grok is inside Sheets but cannot see Drive | You installed the Workspace add-on, which is separate from the Drive connector |
| A second Google account has nowhere to go | Undocumented; share that account’s folders into the connected one and verify with one known file |
| A file you asked Grok to delete is still findable | Grok’s documented action is trashing, not permanent deletion |
| Nothing happens when a file is shared with you | There is no file trigger; an email trigger on the share notification is the nearest thing, and it needs SuperGrok |
Frequently asked questions
Does Grok work with Google Drive?
Yes. Google Drive is a built-in connector at grok.com/connectors with its own Google sign-in, and xAI states that connectors are available to all Grok users. On Grok Business and Enterprise a team admin has to provision it in the cloud console first, though Drive is not one of the connectors xAI lists as needing additional admin setup.
Can I connect two Google accounts to Grok?
xAI does not document it either way. Nothing states whether a second Google Drive connection adds an identity, replaces the first or fails, so the reliable route today is sharing the second account’s folders into the account you connected.
Will Grok see files that other people shared with me?
xAI’s wording is that Grok can access files the signed-in Google account has access to, which covers files sitting in Shared with me, and “shared files” is one of the documented filter attributes. Confirm it against one file you can name before building anything on it.
Can Grok create and edit files, or only read them?
Both are documented: searching, reading, creating and writing files including new Google Docs, creating folders, listing folder contents, trashing files, and uploading its own generated output. Write access comes as an optional permission at sign-in, and unlike Gmail and Calendar there is no documented progressive admin gating on it.
Can Grok move, rename or reshare a file?
None of those verbs appear in xAI’s Drive capability list. Deletion is documented as trashing rather than permanent removal. Assume Grok finds, reads, creates and uploads, and that reorganizing is still your job.
Does Grok react automatically when something changes in my Drive?
No. Schedules run on a clock for everyone, and email triggers watch the inbox on SuperGrok, so a share notification arriving as mail can be caught indirectly. Nothing fires on a file being uploaded, edited or shared.
Related: Multiple Google Calendars in Grok · Multiple Gmail accounts in Grok · Multiple Outlook accounts in Grok · Grok connectors · Best AI assistants for Google Drive · Google Drive integration
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
