Google Contacts

Live

OAUTH 2.0

CONTACTS

Productivity

Google Contacts gives agents authenticated access to your contacts: create, read, update, and delete contacts and groups, and search directory information under the user's own account.

  • Per-user credentials: each contact change runs as the actual user, scoped to their own address book.
  • Encrypted per-tenant vault: AES-256, resolved at request time, never in LLM context.
  • Scoped before every call: pre-call scope check, 90-day SIEM-exportable audit chain.
Google Contacts
agent · Acme Q3
Run
Add everyone from today's meeting to a group called Q3 Prospects.
S
googlecontacts_contact_get
88ms
Google Contacts agent
Created the Q3 Prospects group and added 4 contacts. 1 already existed and was merged, not duplicated.
Contacts: 4 added, 1 group
googlecontacts
4 contacts
18:29
Message Claude...

Tools your productivity agent reaches for in Google Contacts, scoped per user.

CALL ANY TOOL
Manage contacts end to end: create, read, update, and delete contacts, organize them into groups, and look up directory information.
googlecontacts_group_get
Group get
Returns a single contact group by resource name, including its members if requested.
Parameters
Name
Type
Required
Description
group_id
string
Required
The group ID of the contact group (the part after 'contactGroups/').
group_fields
string
Optional
Comma-separated fields to return: clientData, groupType, memberCount, metadata, name.
max_members
integer
Optional
Maximum number of group members to return (default 0 = none).
googlecontacts_groups_list
Groups list
googlecontacts_contact_get
Contact get
googlecontacts_group_create
Group create
googlecontacts_group_delete
Group delete
googlecontacts_group_update
Group update
googlecontacts_contacts_list
Contacts list
googlecontacts_contact_create
Contact create
googlecontacts_contact_delete
Contact delete
googlecontacts_contact_update
Contact update
googlecontacts_directory_list
Directory list
googlecontacts_contacts_search
Contacts search
googlecontacts_groups_batch_get
Groups batch get
googlecontacts_directory_search
Directory search
googlecontacts_people_batch_get
People batch get
googlecontacts_other_contact_copy
Other contact copy
googlecontacts_other_contacts_list
Other contacts list
googlecontacts_contact_delete_photo
Contact delete photo
googlecontacts_group_members_modify
Group members modify
googlecontacts_contact_update_photo
Contact update photo
googlecontacts_contacts_batch_create
Contacts batch create
googlecontacts_contacts_batch_delete
Contacts batch delete
googlecontacts_contacts_batch_update
Contacts batch update
googlecontacts_other_contacts_search
Other contacts search
Build your Agent
Same auth pattern across LangChain, OpenAI, Anthropic, and Google ADK.
Python · LlamaIndex
import { ScalekitClient } from "@scalekit-sdk/node";
import { createReactAgent } from "@langchain/langgraph/prebuilt";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

// Google Contacts tools scoped to this user
const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["googlecontacts"], toolNames: [
    "googlecontacts_group_get",
    "googlecontacts_groups_list",
    "googlecontacts_contact_get"] },
  pageSize: 100,
});

const agent = createReactAgent({ llm, tools });
await agent.invoke({ messages: [{ role: "user", content: "Add everyone from today's meeting to a group called Q3 Prospects." }] });
import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["googlecontacts"] }, pageSize: 100,
});

const res = await openai.chat.completions.create({
  model: "gpt-5",
  messages: [{ role: "user", content: "Add everyone from today's meeting to a group called Q3 Prospects." }],
  tools,
});

// Execute the tool call with the user's vaulted Google Contacts credential
await sk.tools.executeTool(res.choices[0].message.tool_calls[0], "user_123");
import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["googlecontacts"] }, pageSize: 100,
});

const msg = await anthropic.messages.create({
  model: "claude-sonnet-5",
  max_tokens: 1024,
  messages: [{ role: "user", content: "Add everyone from today's meeting to a group called Q3 Prospects." }],
  tools,
});

// Tool call runs with the user's vaulted Google Contacts credential
await sk.tools.executeTool(msg.content, "user_123");
import { Agent } from "@google/adk/agents";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["googlecontacts"] }, pageSize: 100,
});

const agent = new Agent({
  name: "googlecontacts_agent",
  model: "gemini-2.5-pro",
  instruction: "Manage Google Contacts for the signed-in user.",
  tools,
});

await agent.run("Add everyone from today's meeting to a group called Q3 Prospects.");
Try these prompts
Copy any prompt into your agent. Each maps directly to a Google Contacts tool. Click to copy, paste into your agent, done.
Manage contacts
Copy the prompt
Copied
Add this person to my contacts.
Copy the prompt
Copied
Update the phone number for this contact.
Copy the prompt
Copied
Find the contact for jane@acme.com.
Groups
Copy the prompt
Copied
Create a group called Q3 Prospects.
Copy the prompt
Copied
Add these people to the Investors group.
Copy the prompt
Copied
Which groups is this contact in?
Clean up
Copy the prompt
Copied
Find duplicate contacts and merge them.
Copy the prompt
Copied
List contacts with no email address.
Copy the prompt
Copied
Remove this contact from all groups.
SEE HOW AUTH WORKS
Your users connect once. Their Google Contacts credentials stay vaulted, every call is scope-checked, and every action is logged.
1
Authorize
Your user connects
Google Contacts
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
2
Store
Their
Google Contacts
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
3
Resolve
When your agent calls a
Google Contacts
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
4
Audit
Every
Google Contacts
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 productivity connectors.
People Ops and HR teams
New Hire Provisioning Agent
Open-source Python template. Creates or detects the hire in Deel, provisions their Workspace account, builds the Notion onboarding page, posts the welcome.
People Ops and HR teams
PTO & Leave Request Agent
Open-source Python template. Resolves the employee in Deel, validates against their real entitlement, submits the request for approval, blocks the calendar.
Engineering Teams
Incident Response Agent
Open-source Python template. Triggers the PagerDuty page, opens the Jira incident, notifies the on-call Slack channel, and drafts the Confluence postmortem.
GTM and RevOps Teams
Competitive intelligence briefing agent
Scans Gong calls for competitor mentions, matches each one to its Notion battlecard, and DMs every affected rep a single Slack digest per cycle. Every call runs as the PMM who owns the briefing, never a shared bot.
Test other agents
See the same per-user auth pattern across other productivity connectors.
OPS
Email-to-calendar scheduling agent
Read scheduling intent out of Gmail threads, resolve mutual free time, and create the Google Calendar event.
ENGINEERING
Engineering standup agent
Pull commits from GitHub and GitLab, track Jira issue movement, and post a per-engineer standup brief to Slack.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
01.
A shared key touches everyone's address book
A shared Google Contacts token looks fine in a demo. In production it means one agent can read and edit every user's contacts. Scalekit resolves the credential of the actual user who triggered the agent, so each agent only ever touches that user's own contacts.
// shared token
audit → bot_service_account

// scalekit
audit → user_abc ✓
02.
Authentication is not authorization
03.
Multi-tenancy is architectural
04.
Google Contacts today. Ten connectors tomorrow.
“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 Contacts 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 Contacts OAuth token 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 Contacts?
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 Contacts.

What happens when a user revokes Google Contacts 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.

Does the agent respect Google Contacts permissions?
Yes. Every call runs as the authorizing user. Native roles, sharing settings, and scope restrictions in Google Contacts apply to each request, and actions log to the audit chain.

Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack
Cursor Code REPL
# ~/.cursor/mcp.json
{
""mcpServers"": {
""googlecontacts"": {
""url"": ""https://mcp.scalekit.com/googlecontacts"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.googlecontacts]
url = ""https://mcp.scalekit.com/googlecontacts""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""googlecontacts"": {
""url"": ""https://mcp.scalekit.com/googlecontacts"",
""type"": ""http""
}
}
}