ZoomInfo

Live

OAUTH 2.0

SALES

CRM & Sales

The ZoomInfo connector lets AI agents search and enrich B2B contact and company data, access buyer intent signals, discover technographic insights, and manage GTM Studio records including ICPs, personas, competitors, and offerings. Agents can execute ZoomInfo's full data platform on behalf of the authorized user without any manual API wiring.

  • Acts as the user: Company lookalike searches, ICP segment updates, and engagement records are tied to the ZoomInfo account owner who authorized the agent.
  • Credentials stay vaulted: AES-256, resolved at request time, never in LLM context.
  • Scoped before every call: Permissions enforced per-user. 90-day audit trail.
ZoomInfo
agent · Acme Q3
Run
Find the VP of Sales at companies with 500+ employees in fintech.
S
zoominfo_search_contacts
98ms
ZoomInfo agent
Found 3 contacts: Sarah Chen, VP of Sales at Stripe (2,400 employees); Marcus Webb, VP of Sales at Plaid (900 employees); Priya Nair, VP of Sales at Brex (1,100 employees).
Sources: 3 contacts, fintech segment
zoominfo
3 contacts
18:29
Message Claude...

Tools your sales agent reaches for on ZoomInfo, scoped per user.

CALL ANY TOOL
15 tools covering company lookalike discovery, GTM Studio management for ICPs, offerings, competitor records, buyer personas, customer settings, and engagement interaction tracking.
zoominfo_archive_buyer_persona
Archive Buyer Persona
Archive a buyer persona to hide it from active use without permanently deleting it. The persona can be unarchived later. Use this instead of delete when you may need to restore the persona.
Parameters
Name
Type
Required
Description
buyerPersonaId
string
Required
UUID of the buyer persona.
schema_version
string
Optional
Schema version override
tool_version
string
Optional
Tool version override
zoominfo_archive_competitor
Archive Competitor
zoominfo_archive_offering
Archive Offering
zoominfo_archive_segment
Archive Segment
zoominfo_ask_account_summary
Ask Account Summary
zoominfo_create_audience
Create Audience
zoominfo_create_audience_columns
Create Audience Columns
zoominfo_create_folder
Create Folder
zoominfo_create_marketing_audience
Create Marketing Audience
zoominfo_delete_audience
Delete Audience
zoominfo_delete_audience_column
Delete Audience Column
zoominfo_delete_audience_rows
Delete Audience Rows
zoominfo_delete_buyer_persona
Delete Buyer Persona
zoominfo_delete_competitor
Delete Competitor
zoominfo_delete_content_interaction
Delete Content Interaction
zoominfo_delete_folder
Delete Folder
zoominfo_delete_marketing_audience
Delete Marketing Audience
zoominfo_delete_offering
Delete Offering
zoominfo_delete_segment
Delete Segment
zoominfo_delete_settings
Delete Settings
zoominfo_enrich_audience
Enrich Audience
zoominfo_enrich_companies
Enrich Companies
zoominfo_enrich_contacts
Enrich Contacts
zoominfo_enrich_corporate_hierarchy
Enrich Corporate Hierarchy
zoominfo_enrich_hashtags
Enrich Hashtags
zoominfo_enrich_intent
Enrich Intent
zoominfo_enrich_news
Enrich News
zoominfo_enrich_org_charts
Enrich Org Charts
zoominfo_enrich_scoops
Enrich Scoops
zoominfo_enrich_technologies
Enrich Technologies

For more tools, view docs.

Build your Agent
Same auth pattern across every framework.
Try these prompts
Paste any prompt into your agent to get started.
SEE HOW AUTH WORKS
User authorises once. Every agent call after uses their token with scope enforcement.
1
Authorize
Your user connects
ZoomInfo
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
ZoomInfo
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
ZoomInfo
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
ZoomInfo
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.
No items found.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
Other connector libraries treat auth as a demo afterthought.
“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 connect to ZoomInfo using an API key or OAuth?
ZoomInfo uses API key authentication. Scalekit stores the API key in its encrypted vault and injects it at request time. The key is never written into LLM context, agent memory, or logs — the agent calls ZoomInfo tools without ever seeing the credential directly.
What data can the agent access through the ZoomInfo MCP server?
The agent can search for companies and contacts, retrieve firmographic data (industry, revenue, headcount, location), technographic data (tools and technologies in use), and enrich CRM records with verified business information. Access is scoped to the data products included in your ZoomInfo subscription.
Are any ZoomInfo actions irreversible? Can the agent write or modify data?
ZoomInfo MCP tools are primarily read-only — searching, looking up, and enriching are non-destructive operations. If your integration includes CRM enrichment writes, those updates are applied to your CRM records and cannot be automatically undone. Use listScopedTools to restrict the agent to read-only tools if you want to prevent any write operations.
How does Scalekit secure the ZoomInfo API key?
Scalekit vaults the ZoomInfo API key with AES-256 encryption at rest. The key is resolved at request time per tool call and is never surfaced to the LLM, stored in agent memory, or written to logs. You can rotate or revoke the key from the Scalekit dashboard at any time, and the change takes effect immediately on the next call.
ZoomInfo charges per credit for certain data lookups. Can the agent exhaust my credit balance?
Yes — bulk enrichment or high-frequency contact lookups can consume credits quickly. You can limit exposure by using listScopedTools to restrict the agent to lower-cost search tools and blocking direct export or bulk-enrich tools. It is also good practice to set usage alerts in your ZoomInfo account so you are notified before credits run low.
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"": {
""zoominfo"": {
""url"": ""https://mcp.scalekit.com/zoominfo"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.zoominfo]
url = ""https://mcp.scalekit.com/zoominfo""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""zoominfo"": {
""url"": ""https://mcp.scalekit.com/zoominfo"",
""type"": ""http""
}
}
}