> ## Documentation Index
> Fetch the complete documentation index at: https://docs.platform.nora.my/llms.txt
> Use this file to discover all available pages before exploring further.

# Google Workspace

> Use Drive, Gmail, and Calendar as data sources and action targets.

The Google Workspace connector is the most-used integration. Once connected, agents can read from Drive, send email through Gmail, and read or write Calendar events — all within scopes you approved.

## What you can build

<CardGroup cols={2}>
  <Card title="Drive as DataSource" icon="folder">
    Point an agent at a Drive folder. Docs, Sheets, and Slides become searchable.
  </Card>

  <Card title="Gmail send / read" icon="envelope">
    Draft and send email through a connected mailbox; read threads for context.
  </Card>

  <Card title="Calendar" icon="calendar">
    List events on a calendar, create new ones, or check free time.
  </Card>

  <Card title="Sheets read / write" icon="table">
    Read spreadsheet rows or append new ones as an Action.
  </Card>
</CardGroup>

## Connect Google

1. Open **Settings → Connections → New → Google Workspace**.
2. Sign in with the Google account you want to use.
3. Grant the scopes for the services you plan to use (Drive read, Gmail send, Calendar events, Sheets read/write).
4. The connection appears in your workspace, ready to attach to Flows.

<Note>
  Nora asks only for the scopes you actually need. If you skip Gmail during setup, Gmail-related blocks won't appear until you reconnect with that scope.
</Note>

## Use Drive as a DataSource

1. On a Flow canvas, add **DataSource → Google Drive**.
2. Pick a folder from the picker (with the connected account).
3. Wait for the initial index (a progress pill sits on the block).
4. Connect the DataSource to your Agent.

New and updated files sync automatically. Deleted files disappear from the index within a few minutes.

For automated bulk ingest into a document collection, use a Foundry pipeline with a Google Drive Source block — see [Source blocks](/build/foundry/ingest).

## Send email with Gmail

1. Add **Action → Gmail: Send** to your Flow.
2. In the block settings, describe what the email should contain — the Agent fills in the details based on the conversation.
3. If you want a human to review before sending, toggle **Requires approval** (see [Approve & deploy](/reliable/optimization/approve)).

Gmail actions default to sending as the connected mailbox. Reply-to and CC are configurable per-Action.

## Read Calendar

1. Add **Tool → Google Calendar** to your Agent.
2. Pick a calendar and the operation (`list events`, `create event`, `find free time`).
3. Connect the Tool to your Agent.

The Agent calls it when a conversation needs calendar context — "when's your next available slot?", "cancel my 3PM meeting", etc.

## Read / write Sheets

* **Tool → Google Sheets: Read** — Agent picks a range and gets rows. Useful for lookup tables.
* **Action → Google Sheets: Append** — write a row after the Agent decides. Useful for logging.

## Multiple Google accounts

You can connect several Google accounts per workspace. When you add a Drive DataSource or Gmail Action, you pick which connected account to use.

Common pattern: one account for shared workspace data (docs, calendar), one account for outbound sends (a no-reply address).

## Scoping to specific folders

For Drive, narrow the connector to a specific folder tree at setup:

* Reduces the surface an Agent can accidentally read from.
* Speeds up initial indexing.

You can add more folders later without re-authing.

## Disconnecting

**Settings → Connections → Google Workspace → Disconnect**. All blocks that used the connection show a "reconnect needed" state until you either reconnect or remove them.

Reconnecting under the same Google account restores the connection without re-indexing.

## Scope changes

If you need additional scopes after initial setup (e.g. added Gmail scopes to an existing Drive-only connection):

1. Settings → Connections → Google Workspace → **Update scopes**.
2. Re-authenticate; Google shows the new consent screen.
3. New blocks for the added scopes become available.

## Related

* [Connectors](/settings/connections/connectors) — the general connector concept.
* [Source blocks](/build/foundry/ingest) — using Drive in a Foundry pipeline.
* [Tool block](/build/workflow/tool-block) — how Agents call Google APIs.