What you can build
Drive as DataSource
Point an agent at a Drive folder. Docs, Sheets, and Slides become searchable.
Gmail send / read
Draft and send email through a connected mailbox; read threads for context.
Calendar
List events on a calendar, create new ones, or check free time.
Sheets read / write
Read spreadsheet rows or append new ones as an Action.
Connect Google
- Open Settings → Connections → New → Google Workspace.
- Sign in with the Google account you want to use.
- Grant the scopes for the services you plan to use (Drive read, Gmail send, Calendar events, Sheets read/write).
- The connection appears in your workspace, ready to attach to Flows.
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.
Use Drive as a DataSource
- On a Flow canvas, add DataSource → Google Drive.
- Pick a folder from the picker (with the connected account).
- Wait for the initial index (a progress pill sits on the block).
- Connect the DataSource to your Agent.
Send email with Gmail
- Add Action → Gmail: Send to your Flow.
- In the block settings, describe what the email should contain — the Agent fills in the details based on the conversation.
- If you want a human to review before sending, toggle Requires approval (see Approve & deploy).
Read Calendar
- Add Tool → Google Calendar to your Agent.
- Pick a calendar and the operation (
list events,create event,find free time). - Connect the Tool to your Agent.
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.
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):- Settings → Connections → Google Workspace → Update scopes.
- Re-authenticate; Google shows the new consent screen.
- New blocks for the added scopes become available.
Related
- Connectors — the general connector concept.
- Source blocks — using Drive in a Foundry pipeline.
- Tool block — how Agents call Google APIs.