Google Workspace (DWD) connector for AI agents

Google Workspace (DWD) tools for AI agents

CALL ANY TOOL

12 tools covering complete, append, clear.

googledwd_add_group_member

Add group member

Add a member to a Google Workspace group using the Admin Directory API. Uses DWD service account credentials.

Parameters

Name

Type

Required

Description

group_key

string

Required

Email address or unique ID of the group.

member_email

string

Required

Email address of the user or group to add as a member.

role

string

Optional

Role to assign the member: OWNER, MANAGER, or MEMBER.

googledwd_append_values

Append values

googledwd_copy_file

Copy file

googledwd_create_admin_group

Create admin group

googledwd_create_contact

Create contact

googledwd_create_filter

Create filter

Create a new email filter for the authenticated Gmail account. Specify criteria (sender, recipient, subject, query, or attachment) and actions (apply labels, forward, archive, star, trash, mark as read, etc.). At least one criteria field should be provided. Uses DWD service account credentials.

Parameters

Name

Type

Required

Description

add_label_ids

array

Optional

List of Gmail label IDs to apply to matching messages (e.g., ['Label_123', 'STARRED']). Use the List Labels tool to find valid label IDs.

forward

string

Optional

Email address to forward matching messages to. The address must already be configured as a forwarding address in the Gmail account.

from

string

Optional

Sender email address or domain to match in the filter criteria (e.g., 'alerts@github.com' or '@newsletter.com').

has_attachment

boolean

Optional

If true, only match messages that have at least one attachment.

query

string

Optional

Gmail search query string to match messages using Gmail's search syntax (e.g., 'larger:10M', 'is:important').

remove_label_ids

array

Optional

List of Gmail label IDs to remove from matching messages (e.g., ['INBOX'] to archive, ['UNREAD'] to mark as read).

schema_version

string

Optional

Optional schema version to use for tool execution

should_always_mark_important

boolean

Optional

If true, always mark matching messages as important regardless of Gmail's automatic importance detection.

should_archive

boolean

Optional

If true, skip the inbox for matching messages (equivalent to adding the 'Archive' action).

should_mark_read

boolean

Optional

If true, automatically mark matching messages as read.

should_never_mark_important

boolean

Optional

If true, never mark matching messages as important, overriding Gmail's automatic importance detection.

should_never_spam

boolean

Optional

If true, never send matching messages to the Spam folder.

should_star

boolean

Optional

If true, automatically star matching messages.

should_trash

boolean

Optional

If true, automatically move matching messages to the Trash.

subject

string

Optional

Subject line text to match in the filter criteria (e.g., '[GitHub]' or 'Invoice').

string

Optional

Recipient email address to match in the filter criteria (e.g., 'team@example.com').

tool_version

string

Optional

Optional tool version to use for execution

googledwd_create_presentation

Create presentation

googledwd_create_task_list

List create task

googledwd_delete_admin_group

Delete admin group

googledwd_delete_event

Delete event

googledwd_fetch_mails

Fetch mails

googledwd_get_admin_group

Get admin group

googledwd_get_attachment_by_id

Get attachment by id

googledwd_get_file_metadata

Get file metadata

googledwd_get_meet_space

Get meet space

googledwd_get_thread_by_id

Get thread by id

googledwd_list_alert_feedback

List alert feedback

googledwd_list_chat_spaces

List chat spaces

googledwd_list_filters

List filters

googledwd_list_responses

List responses

googledwd_modify_message_labels

Modify message labels

googledwd_query_drive_activity

Query drive activity

googledwd_read_document

Read document

googledwd_remove_group_member

Remove group member

googledwd_search_content

Search content

googledwd_send_message

Send message

googledwd_signout_admin_user

Signout admin user

googledwd_update_admin_group

Update admin group

googledwd_update_document

Update document

googledwd_update_task

Update task

For more tools, view docs.

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