Overview
The ZoomInfo integration connects Alysio to ZoomInfo’s API using OAuth 2.0 via Paragon Connect.
It enables AI agents to securely retrieve real-time company, contact, intent, and business intelligence data for lead generation, enrichment, and research — all within Alysio’s conversational interface.
All access is user-authorized, on-demand, and scope-restricted.
No data is stored or cached; each request retrieves only the fields required to fulfill a specific user query.
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.
Purpose & Use Cases
-
Search and enrich leads or company data directly in Alysio
-
Identify intent signals and buying patterns
-
Retrieve AI-powered insights and summaries from ZoomInfo Copilot
-
Combine CRM and third-party data to power natural language analysis
Supported ZoomInfo Objects
-
Contacts
-
Companies
-
Intent Signals
-
News & Media
-
Scoops (Business Intelligence)
-
Technologies & Hierarchies
-
AI Copilot Summaries and Insights
Authentication
Method: OAuth 2.0 via Paragon Connect
Redirect URI: https://passport.useparagon.com/oauth
Token Handling:
-
OAuth tokens are issued by ZoomInfo and securely managed by Paragon; Alysio never stores them.
-
Each tenant’s connection is isolated and identified by a signed
X-Paragon-Credential header.
-
Tokens are automatically refreshed through Paragon’s secure infrastructure.
-
Uninstalling the integration removes credentials and stops all API activity.
-
✅ Alysio dynamically enforces the OAuth scopes granted by the user — all API operations are limited to those authorized permissions.
Enabled Scopes
Copilot Read Account Summary API
Copilot Read Insights Data
Company
Contact
Intent
News
Scoops
Scope Justification
| Scope | Purpose |
|---|
| Copilot Read Account Summary API | Access AI-generated company summaries and business insights. |
| Copilot Read Insights Data | Retrieve data from ZoomInfo’s AI-driven insights and signals APIs. |
| Company | Read company profiles, hierarchies, and technology data. |
| Contact | Search and enrich contact and lead information. |
| Intent | Read intent signals and trending topics to identify in-market companies. |
| News | Retrieve company-related news and media mentions. |
| Scoops | Access insider intelligence and business scoops for target accounts. |
All data access is restricted to these scopes; Alysio never requests or uses broader permissions.
API Usage
All requests are routed through Paragon’s secure proxy (/sdk/proxy/zoominfo/https://api.zoominfo.com) to the official ZoomInfo REST API.
Alysio performs read-only, on-demand operations with no background syncs or data persistence.
Endpoint Categories
| Category | Examples | Purpose |
|---|
| Search | /data/v1/contacts/search, /data/v1/companies/search, /data/v1/intent/search | Query for matching contacts, companies, or signals |
| Enrichment | /data/v1/contacts/enrich, /data/v1/companies/enrich | Enrich existing records with verified data |
| AI/Copilot | /copilot/v1/companies/{id}/account-summary, /copilot/v1/companies/insights | Retrieve AI-generated summaries and insights |
| Utility | /data/v1/lookup/{lookupType} | Get lookup values for structured data fields |
Request Characteristics
-
JSON:API format (
application/vnd.api+json)
-
Pagination supported (default 20 items per page, max 100)
-
Extensive filter parameters (100+)
-
Validation with Pydantic models
-
10-minute timeout and up to 10 automatic retries on transient failures
Error Handling
-
Structured JSON error responses
-
Graceful handling of 400+ status codes
-
Full logging through Paragon infrastructure
App Behavior
-
API calls are initiated on-demand through user actions in Alysio (e.g., natural language queries).
-
Each call is validated against the granted OAuth scopes before execution.
-
Data is retrieved securely from ZoomInfo in real time and displayed to the user without storage.
-
There are no batch syncs, exports, or automated background processes.
Example Flow
-
A user asks: “Show me contacts at companies researching AI infrastructure.”
-
Alysio routes the request through the ZoomInfo MCP server.
-
The MCP server calls
/data/v1/contacts/search and /data/v1/intent/search through Paragon.
-
ZoomInfo returns paginated results matching the request.
-
Alysio displays those results in the chat — no data stored locally.
Troubleshooting
Common Issues
-
Invalid Token or Expired Session → Reconnect integration in Alysio → Settings → Integrations → ZoomInfo.
-
Missing Scopes → Ensure all required scopes (Copilot, Company, Contact, Intent, News, Scoops) are granted during install.
-
Rate Limit Exceeded → Retry after delay; additional throttling may occur via Paragon proxy.
-
OAuth Redirect Error → Verify redirect URI matches
https://passport.useparagon.com/oauth.
Support
Version History
| Date | Update | Notes |
|---|
| October 2025 | Created OAuth 2.0 via Paragon | Updated authentication flow, added Copilot scopes, finalized technical documentation for marketplace submission |
Data Flow Diagram
Text Version:
┌────────────────────┐
│ ZoomInfo User │
└────────┬───────────┘
│
▼
(1) OAuth Authorization
│
▼
┌───────────────────────────┐
│ Paragon Connect │
│ – Manages OAuth tokens │
│ – Handles token refresh │
│ – Validates redirect URI │
└────────┬──────────────────┘
│
▼
(2) Signed Credential Token
│
▼
┌───────────────────────────┐
│ Alysio App │
│ – Receives signed token │
│ – Calls Paragon proxy │
│ – Validates granted scopes │
│ – Processes transient data │
└────────┬──────────────────┘
│
▼
(3) Proxied API Requests
│
▼
┌───────────────────────────┐
│ ZoomInfo API │
│ – Executes permitted ops │
│ – Enforces OAuth scopes │
└───────────────────────────┘
Flow Summary
-
The user authorizes Alysio via ZoomInfo OAuth.
-
Paragon manages token exchange, refresh, and secure storage.
-
Alysio receives a signed credential for authenticated requests.
-
API calls are executed through Paragon’s proxy and validated against OAuth scopes.
-
Results are returned securely and displayed in real time, with no storage or export.
Summary
-
Alysio cannot exceed the OAuth scopes granted by the user.
-
Each API call is validated against the authorized token before execution, ensuring data access is restricted and ephemeral.
-
All data travels over HTTPS; tokens are never exposed or stored locally.
-
On uninstall, the integration is fully deauthorized and all syncs stop.