# Google Drive

> A one-click Google connection that lets EOMA create documents in your Drive — and cannot open anything already in it.

Source: https://eoma.ai/docs/integrations/google-drive
Product: EOMA — AI search visibility for brands (https://eoma.ai)
Last updated: 2026-08-14

---
## In 10 seconds

- One step, one click. There is no folder to choose and no second window, unlike the other two Google connections.
- EOMA asks for the narrowest Drive permission Google offers: it can only touch **files it creates itself**. Your existing documents stay invisible to it.
- Today this connection is groundwork. No screen in EOMA writes to your Drive yet — connecting it changes nothing you can see. Skip it until you need it.

## Before you start

- You must be the **owner** of this brand in EOMA. Everyone else sees "Owner only".
  See [Integrations](/docs/settings/integrations).
- Any Google account works. Unlike Google Analytics and Search Console, there is no
  property or verified site to match, so the "wrong account" problem barely applies
  here — pick the account whose Drive you want documents to land in.
- No plan requirement. Integrations are available on every plan.

## Steps

### 1 — Open Settings → Integrations

```
┌─ Settings ───────────────────┬─────────────────────────────────┐
│    Plan & Usage              │  Analytics & Search             │
│    Brand Profile             │  ▮ Google Analytics 4           │
│  ● Integrations       ← here │  ▮ Google Search Console        │
│                              │  ▮ Google Drive       [Connect] │
└──────────────────────────────┴─────────────────────────────────┘
```

Third card in the **Analytics & Search** group.

### 2 — Click Connect and approve

Your browser leaves EOMA for Google's approval screen, which asks for one thing:

> **See, edit, create and delete only the specific Google Drive files you use
> with this app**

Read that wording carefully, because it is the whole point of this connection.
"Only the specific files you use with this app" means files EOMA creates. A document
already sitting in your Drive is not one of them, and EOMA cannot list it, open it or
change it. There is no broader Drive permission behind this one.

Approve, and Google returns you to Settings → Integrations.

### 3 — Confirm the card

That is the entire flow. There is no folder picker and nothing to select.

```
Google Drive              Connected            Disconnect
```

If it says anything else, see the table at the bottom.

## What you'll see

### The card, before you connect

The provider name and a **Connect** button.

### The card, once connected

The word **Connected** and a **Disconnect**. There is no name, count or folder beside
it, because this connection has nothing to point at — it is permission to write into a
Drive, not a link to one particular place in it.

### "Owner only"

Shown instead of any button when your role on this brand is not owner.

### What changes elsewhere in EOMA

Almost nothing, and this is worth being straight about. Connecting Drive today has one
visible effect: when EOMA's agent works on your brand, "Google Drive" appears in its
list of connected services, so it knows the option exists.

**No screen in EOMA currently writes a document to your Drive.** The ability to create
one is built and tested on our side, and nothing in the product calls it yet. If you
connect Drive expecting reports or drafts to start appearing in it, they will not.
Connect it when a feature asks you to; there is no benefit to connecting it early, and
no harm in disconnecting it.

For taking work out of EOMA today, use the download and copy options on an action's
result instead. See [Actions](/docs/pages/actions).

## Reading the numbers

**There is no number on this card, and that is the honest state.** Every other
connection here counts something — properties, a site, a repository — because something
in EOMA reads it. Drive has nothing to count yet.

**"Connected" means only that the permission is stored.** It does not mean anything has
been written, or ever will be until a feature uses it. Treat the word as "approved",
not as "working".

**One email per disconnection.** If the Google authorisation later breaks, EOMA emails
the brand owner once — not once per attempt. Reconnecting resets it, so a future break
notifies you again.

## When it goes wrong

| You see | Why | What to do |
|---|---|---|
| "Google Drive connect failed: access denied" | You pressed Cancel on Google's approval screen. | Click Connect and approve. |
| "Google Drive connect failed: invalid state" | More than 10 minutes passed on Google's screen before approving. | Click Connect and go through it without pausing. |
| The card still says **Connect** after you approved | The approval came back but was not stored. | Click Connect once more. If it repeats, contact support. |
| Nothing appears in your Google Drive | Expected. No feature writes to Drive yet. | Nothing to fix. Use the export options on an action's result instead. |
| A message that the connection errored | The saved Google authorisation stopped working — usually revoked from the Google account's own security settings. | Disconnect, then Connect again. |
| An email from EOMA saying an integration disconnected | The link broke and stayed broken. Sent once per disconnection, to the brand owner. | Reconnect, or disconnect the card if you do not need it. |
| You want EOMA to stop having access entirely | Disconnecting here removes EOMA's stored permission. | Press **Disconnect**. To be doubly sure, also remove EOMA from your Google account's third-party access list. |

## Related

- [Integrations](/docs/settings/integrations) — every connection in one place
- [Actions](/docs/pages/actions) — where finished work is downloaded or copied today
- [Google Analytics 4](/docs/integrations/google-analytics) — the Google connection that does feed a screen