Google Workspace (DWD) connector for AI agents

Google Workspace (DWD) tools for AI agents

CALL ANY TOOL

12 tools covering complete, append, clear.

googledwd_list_tasks

List tasks

List all tasks in a specified Google Tasks task list. Supports filtering by completion status, deletion status, and due date range. Uses DWD service account credentials.

Parameters

Name

Type

Required

Description

task_list_id

string

Required

The ID of the task list to retrieve tasks from.

due_max

string

Optional

Upper bound for a task's due date (RFC3339 datetime). Tasks due after this datetime are excluded.

due_min

string

Optional

Lower bound for a task's due date (RFC3339 datetime). Tasks due before this datetime are excluded.

max_results

integer

Optional

Maximum number of tasks to return. Accepted value is between 1 and 100.

page_token

string

Optional

Token specifying the page of results to return. Obtained from nextPageToken in a previous response.

schema_version

string

Optional

Optional schema version to use for tool execution

show_completed

boolean

Optional

Flag indicating whether completed tasks are returned. The default is true.

show_deleted

boolean

Optional

Flag indicating whether deleted tasks are returned. The default is false.

show_hidden

boolean

Optional

Flag indicating whether hidden tasks are returned. The default is false.

tool_version

string

Optional

Optional tool version to use for execution

googledwd_search_files

Search files

googledwd_list_alerts

List alerts

googledwd_search_people

Search people

googledwd_list_drafts

List drafts

googledwd_search_content

Search content

googledwd_list_events

List events

googledwd_get_form

Get form

googledwd_list_labels

List labels

googledwd_get_alert

Get alert

googledwd_list_filters

List filters

googledwd_get_values

Get values

googledwd_list_threads

List threads

googledwd_get_contacts

Get contacts

googledwd_list_calendars

List calendars

googledwd_get_response

Get response

googledwd_list_documents

List documents

googledwd_get_userinfo

Get userinfo

googledwd_list_responses

List responses

googledwd_get_send_as

Get send as

googledwd_list_org_units

List org units

googledwd_get_keep_note

Get keep note

googledwd_list_keep_notes

List keep notes

googledwd_get_admin_user

Get admin user

googledwd_list_task_lists

List task lists

googledwd_get_chat_space

Get chat space

googledwd_list_admin_users

List admin users

googledwd_get_meet_space

Get meet space

googledwd_list_chat_spaces

List chat spaces

googledwd_get_admin_group

Get admin group

Build your Agent

Same auth pattern across every framework.

token = client.agent.get_token(user_id="user_id", connector="googledwd")

const token = await client.agent.getToken({ userId: "user_id", connector: "googledwd" });

const token = await client.agent.getToken({ userId: "user_id", connector: "googledwd" });

token = client.agent.get_token(user_id="user_id", connector="googledwd")

Try these prompts

Paste any prompt into your agent to get started.

Get started

SEE HOW AUTH WORKS

User authorises once. Every agent call after uses their token with scope enforcement.

Authorize

Your user connects

Google Workspace (DWD)

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

Limited to user

Store

Their

Google Workspace (DWD)

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

Resolve

When your agent calls a

Google Workspace (DWD)

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

Audit

Every

Google Workspace (DWD)

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Test other agents

See the same per-user auth pattern across other connectors.

GTM and RevOps Teams

Deal room sync

Pulls opportunity context from Salesforce, captures key decisions from Slack, and syncs a running summary to the deal room doc in Google Drive, but only when the deal actually changed.

People Ops and HR teams

Performance review collector

Collects review feedback from Airtable and Google Forms scoped to each manager's direct reports, writes per-employee summaries to Notion, and DMs the manager a Slack digest.

People Ops and HR teams

Offer letter routing agent

Drafts the offer in PandaDoc, blocks on the hiring manager's approval in Slack, then emails the candidate their e-signature link. Every call runs as the recruiter who triggered it, never a shared HR bot.

Support and Ops Teams

Support ticket automation agent

Fetches new Zendesk tickets, drafts a reply from Notion knowledge base articles, digests what it cannot answer to Slack, and archives the rest, acting as the support agent rather than a shared API key.

Why Scalekit

Secure your agent's access. Connectors ship in minutes

01.

Shared tokens break per-user analytics

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

FAQs

Frequently Asked Questions

Does the agent access Google Workspace (DWD) as the user or as a shared key?
As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.

Where is the Google Workspace (DWD) service account key stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.

Can I limit what the agent is allowed to do in Google Workspace (DWD)?
Yes. Pass a tool name filter to listScopedTools so the productivity agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Google Workspace (DWD).

What happens when a user revokes Google Workspace (DWD) access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

How does Domain-Wide Delegation stay safe with agents?
The service account key stays in Scalekit's vault and every call impersonates a specific workspace user under your configured scopes. Pre-call scope checks and the audit chain record which user context each Gmail, Drive, or Sheets call ran in.

On this page

Tool and actions Framework Compatibility Starter Prompt Auth Lifecycle Try Other Agents Why Scalekit