> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.lido.app/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Connect Google Drive

Connect a Google account to Lido so workflows can watch Drive folders, download files, and trigger on new uploads. The same connection powers the Google Drive Trigger and the Google Drive node.

---

## When to connect

- You want a workflow that runs every time a new file lands in a Drive folder.
- You want workflows to download or list files from Drive.
- You want to use Drive folders as the destination for files Lido creates (exports, generated PDFs).

---

## Before you start

You need:

- A Google account that has access to the folders you want Lido to read from or write to.
- For shared/team folders: confirm the account has at least Viewer access.
- Admin rights to add integrations to your Lido workspace.

---

## Step-by-step

1. Open your Lido workspace settings and find **Integrations** (or Credentials).
2. Click **Add Integration → Google Drive**.
3. Click **Connect** to start the OAuth flow. Sign in to the Google account, review the requested scopes, and approve.
4. Lido stores the connection as a credential.
5. Return to the workflow editor. Add a **Google Drive Trigger** or **Google Drive** node — the connected account now appears as a selectable credential.

That's it. The connection is workspace-wide; everyone in the workspace can use it in workflows.

---

## What Lido can and can't do with the connection

**Can:**

- Watch a folder for new files.
- Download files for processing.
- List files in a folder.
- Upload files Lido creates (exports, generated PDFs) to a folder.

**Can't (without explicit configuration):**

- Read your entire Drive. Lido only accesses what you point it at via folder selection.
- Modify file permissions.
- Delete files (unless you explicitly use a deletion-capable action and confirm).
- Read other users' Drives unless they share the folder with the connected account.

---

## Using the connection in workflows

### Watch a folder

Add a **Google Drive Trigger** node. Pick the connected credential, pick the folder, set file types. The workflow now fires on every new file matching the filter.

### List files in a folder

Add a **Google Drive** node with operation `List`. Returns an item per file in the folder. Useful for batch processing on a schedule.

### Download a file

Add a **Google Drive** node with operation `Download`. Pass it a file URL or ID; it returns the file content for downstream processing (e.g., Data Extractor).

---

## Tips

- **Use a service account or shared mailbox** for production workflows. Personal accounts cause problems when employees leave.
- **Connect the most restricted account that still has access.** Avoid connecting a personal account with full Drive access; create a dedicated account with access only to the folders Lido needs.
- **Folder selection matters.** Lido only watches the folder you pick — not subfolders by default. Pick the right level.
- **Test with a non-production folder first.** Drop a file in to confirm the workflow fires before pointing it at the live folder.

---

## Common mistakes

- **Connecting an account that doesn't have access to the production folder.** OAuth grants what the user can grant; if the account can't see the folder, neither can Lido.
- **Wrong folder selected.** "Invoices" vs. "2026 Invoices" vs. "Invoices Inbox" — pick the right one.
- **Watch mode set to "all changes" instead of "new files only".** Re-fires on every file edit; almost never what you want.
- **No file type restriction.** Random `.docx` files trigger PDF extraction workflows that fail.
- **Personal account used for production workflows.** When the employee leaves and the account is disabled, all your workflows break silently.

---

## Disconnecting

Open workspace settings → Integrations → find the Google Drive credential → **Remove**. Workflows using the credential will fail until you reconnect or point them at a different credential.

---

## Related articles

- Build your first workflow
- Triggers: how workflows start (Google Drive Trigger)
- Connect OneDrive
- Automate extraction with workflows