Overview
The ZoomInfo integration lets users connect their ZoomInfo account so Alysio can search and enrich B2B contact, company, intent, news, and scoops data on their behalf. Users can ask Alysio to find contacts or companies by criteria, enrich records by email or domain, search intent signals and news, get org charts and tech stacks, and use ZoomInfo’s AI Copilot for account summaries and natural-language questions—all in natural language. The integration uses the user’s ZoomInfo credential via OAuth 2.0 and is read-only (search and enrich); it does not write or delete data in ZoomInfo.Read-Only Access: This integration supports read-only data access, ideal for research, prospecting, and account preparation. Alysio never writes or modifies information in your ZoomInfo account.
- Search — Contact search, company search, intent search (buying signals), news search, scoops search; all support filters and pagination.
- Data lookup — Reference lists for filter values (e.g. job titles, industries, intent topics, news categories, scoop types, tech categories). Use before search/enrich to get valid filter options.
- Enrich — Contact enrich (by email/name/company), company enrich (by ID/domain/website), news enrich, intent enrich, company technologies, corporate hierarchy, org charts, company hashtags, scoops enrich.
- Copilot — Account summary for a company, natural-language questions about an account, and insights by signal type (funding, intent, scoops, etc.).
Authentication
Method: OAuth 2.0 or API key (ZoomInfo). The MCP sends requests using a Bearer token and a credential ID that identifies the user’s ZoomInfo connection. Requests use ZoomInfo’s Data API and Copilot API (JSON:API style,Content-Type: application/vnd.api+json).
Redirect URI: Configured when the ZoomInfo integration is set up in Alysio. If ZoomInfo uses API key only, no redirect is used.
Token handling
- The ZoomInfo credential (OAuth tokens or API key) is stored securely and refreshed as needed.
- Each user/tenant has their own credential; the MCP sends the appropriate credential ID with each request so calls are isolated per connection.
- On disconnect, that credential is no longer used and ZoomInfo tools will not be available until the user reconnects ZoomInfo.
| Scope / capability | Purpose |
|---|---|
| Search | Run contact, company, intent, news, and scoops searches. |
| Enrich | Call contact, company, news, intent, technologies, hierarchy, org charts, hashtags, and scoops enrich APIs. |
| Lookup | Fetch reference data for filters (job titles, industries, intent-topics, news-categories, scoop-types, etc.). |
| Copilot | Get account summary, ask questions, and retrieve insights by type. |
API Usage
All requests are sent to the ZoomInfo Data API and Copilot API using the user’s stored credential. Alysio performs read-only, on-demand operations with no background syncs or data persistence. Request characteristics- JSON:API format (
application/vnd.api+json) - Pagination supported (default 20 items per page, max 100)
- Extensive filter parameters (100+)
- 10-minute timeout and up to 10 automatic retries on transient failures
- Structured JSON error responses
- Graceful handling of 400+ status codes
MCP Tools
The ZoomInfo MCP exposes the following tools. Users can invoke these capabilities through natural language in Alysio.| Tool | Description | Example user prompts |
|---|---|---|
zoominfo_data_lookup | Returns reference lists for a given lookup type (e.g. job-titles, industries, intent-topics, news-categories, scoop-types) for use as filter values in search/enrich. | ”What intent topics are available?”, “Get list of job titles for filtering.” |
zoominfo_contact_search | Searches for contacts/people by name, email, job title, company, location, and other criteria; use company search first to get companyId if needed. | ”Find CEOs at tech companies in California”, “Search for contacts at Acme Corp.” |
zoominfo_company_search | Searches for companies by name, domain, employee count, revenue, funding, and other criteria. | ”Find companies in healthcare with 100+ employees”, “Search for companies in Boston.” |
zoominfo_intent_search | Searches for companies showing buying signals/intent by topic; use data lookup with intent-topics first for valid topics. | ”Companies showing intent to buy CRM”, “Find companies with buying signals.” |
zoominfo_news_search | Searches news articles and media coverage; use data lookup with news-categories first if filtering by category. | ”News about Acme Corp”, “Search for recent funding news.” |
zoominfo_scoops_search | Searches scoops and insider intelligence; use data lookup with scoop-types first if filtering by type. | ”Scoops about Acme Corp”, “Search for executive change scoops.” |
zoominfo_contact_enrich | Enriches contact data by email/name/company (matchPersonInput); returns detailed contact fields. | ”Enrich contact for john@company.com”, “Get full profile for this contact.” |
zoominfo_company_enrich | Enriches company data by ID, domain, or website (matchCompanyInput); returns detailed company fields. | ”Enrich company by domain company.com”, “Get full company profile for Acme.” |
zoominfo_news_enrich | Returns detailed news for companies (e.g. by companyId); supports category filters (use data lookup for categories). | ”Get news for this company”, “Enrich news for company ID 123.” |
zoominfo_intent_enrich | Returns detailed intent data for companies; supports topic and other filters (use data lookup for topics). | ”Get intent signals for this company”, “Enrich intent for company 123.” |
zoominfo_company_technologies_enrich | Returns technology stack and software information for companies. | ”What tech does this company use?”, “Get tech stack for company 123.” |
zoominfo_corporate_hierarchy_enrich | Returns corporate hierarchy and reporting structure for companies. | ”Who reports to the CEO at Acme?”, “Get corporate hierarchy for this company.” |
zoominfo_org_charts_enrich | Returns organizational charts and team structure for companies. | ”Show org chart for Acme”, “Get org chart for company 123.” |
zoominfo_company_hashtag_enrich | Returns hashtag and social media information for companies. | ”What hashtags does this company use?”, “Get social data for company 123.” |
zoominfo_scoops_enrich | Returns scoops and insider information for companies; use data lookup for types/topics if filtering. | ”Get scoops for this company”, “Enrich scoops for company 123.” |
zoominfo_get_copilot_account_summary | Returns ZoomInfo Copilot account summary for a company (companyId required). | ”Give me an account summary for Acme”, “Copilot summary for company 123.” |
zoominfo_copilot_account_summary_question | Asks a natural-language question to Copilot about a company account (companyId and question required). | ”Who are the decision makers at Acme?”, “Ask Copilot: what’s our risk with this account?” |
zoominfo_copilot_insights_by_type | Returns Copilot insights by signal type (e.g. funding, intent, scoops) for given company IDs. | ”Get funding insights for these companies”, “Copilot insights by type for company 123.” |
App Behavior
- API calls are made on-demand only when the user asks something that requires ZoomInfo data (e.g. search contacts/companies, enrich by email/domain, get intent/news/scoops, or use Copilot). There is no background sync; each request triggers the relevant ZoomInfo API call using the user’s stored credential.
- User asks: “Find companies in tech with more than 500 employees.”
- Alysio routes the request to the ZoomInfo MCP.
- The MCP calls
zoominfo_company_searchwith appropriate filters (e.g. industry, employee count). - The request is sent to the ZoomInfo Data API using the user’s stored credential.
- The MCP returns the company list; Alysio presents the results in chat. The user can then ask to enrich a company or get a Copilot summary by company ID.
Troubleshooting
Common issues- Missing or expired connection — User sees errors or no ZoomInfo data. Fix: Reconnect ZoomInfo in Settings → Integrations (re-authorize or update API key).
- 401 Unauthorized — Invalid or expired credential. Fix: Re-authorize the integration in Settings → Integrations; confirm ZoomInfo API access and key/scope.
- 403 Forbidden — ZoomInfo contract may not include the requested API (e.g. Copilot, certain enrich endpoints). Fix: Verify ZoomInfo subscription includes the feature; reduce request scope or use an allowed endpoint.
- Invalid filter values — Search or enrich fails due to unknown topic, category, or type. Fix: Use
zoominfo_data_lookupwith the correctlookupType(e.g.intent-topics,news-categories,scoop-types) and use returned values in the filter. - Missing companyId — Enrich or Copilot tools require a ZoomInfo company ID. Fix: Run
zoominfo_company_searchfirst (by name or domain) and use the returnedcompanyIdin enrich/Copilot calls. - Empty or limited results — ZoomInfo coverage and filters may limit matches. Fix: Widen filters or try alternate criteria (e.g. domain instead of company name); check ZoomInfo docs for field and filter behavior.
- Email: support@alysio.ai
- Docs: https://tech.alysio.ai/integrations/zoominfo
- For ZoomInfo API behavior and limits, see ZoomInfo Developer Documentation.
Version History
| Date | Update | Notes |
|---|---|---|
| October 2025 | OAuth 2.0 integration | Updated authentication flow, added Copilot scopes, finalized technical documentation for marketplace submission |
Data Flow Diagram
Flow summary- The user authorizes Alysio via ZoomInfo OAuth (or provides API key).
- Credentials are stored and refreshed securely per connection.
- Alysio sends authenticated requests with the user’s credential.
- API calls are validated against OAuth scopes or API permissions.
- Results are returned securely and displayed in real time, with no storage or export.
- Alysio cannot exceed the scopes or permissions granted by the user.
- Each API call is validated against the authorized credential before execution.
- All data travels over HTTPS; tokens/keys are never exposed in client-side code.
- On disconnect, the integration is fully deauthorized and all API access stops.