Reference & Lookup Data · Integration
ZoomInfo
Add ZoomInfo to your product for your customers, and give your AI agents governed access to it.
ZoomInfo is somebody else's database that you query, not a place your customers keep records of their own, and its pricing model is the thing to build around. Search and enrich are different calls with different economics: a search returns matches and spends nothing, while an enrich returns the full profile and costs a credit. What makes that manageable is that a redeemed record stays under management for twelve months, so enriching the same contact again before the anniversary costs nothing further, which turns caching from a nicety into the obvious design. Alongside contacts and companies sit scoops, news and intent signals, which is what turns a lookup into a reason to act rather than a field to fill. Authentication is a token exchanged from a username and password or from a key pair, and it lapses within the hour, so refresh is continuous rather than occasional. Each customer connects their own account, so credits and rate limits land on the tenant that spent them.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Have each customer connect their own ZoomInfo account so credits come out of their allowance rather than a shared key you then have to re-bill.
Search before you enrich, since matching costs nothing and pulling the full profile costs a credit.
Cache an enriched record for the twelve months it stays under management, rather than spending a second credit on something you already hold.
Read intent and scoops so your product can surface a reason to get in touch, not just a phone number.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent finds the right company match and reports what it is confident about before anything is enriched.
An agent enriches a record inside a spending limit you set, and the credit it used is attributed to that tenant.
An agent says where a data point came from instead of presenting an outside lookup as the customer's own record.
Example prompt
Find this company, tell me which contacts match the role we sell to, and what it would cost to enrich them.
Set up ZoomInfo in 4 steps
- 01Enable the ZoomInfo connector in your fastn dashboard.
- 02Have each customer bring credentials for their own account, whether that is a username and password or a key pair, so credits come from their allowance.
- 03Decide where you search and where you enrich, and cache enriched records for the period they stay under management.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the ZoomInfo integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a ZoomInfo integration without building it. Your customers connect their own ZoomInfo account inside your product and work their lookups, results and reports there, with no per-customer code on your side.
- Handle the part that actually costs time: these are metered read sources, so an uncached lookup on every page view burns the customer's allowance. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a ZoomInfo update is not your on-call problem.
- One integration serves your product and your agents. The same governed ZoomInfo connection powers in-product features and gives AI agents scoped, audited access, so you answer questions from an authoritative outside source without holding that data yourself without wiring it twice.
Used by these teams
Compare with
Clearbit
BomboraWorks well with
ApolloOften used alongside
Tools the same teams tend to run next to ZoomInfo, across other categories.
Salesforce
HubSpot
Notion
SnowflakeZoomInfo integration FAQ
How do I add a ZoomInfo integration to my product?
Enable the ZoomInfo connector in your fastn dashboard, then let each customer authenticate their own ZoomInfo account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no ZoomInfo client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own ZoomInfo account?
Yes. Every connection is scoped to the individual customer, so each authorises their own ZoomInfo account and only ever sees their own lookups, results and reports. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this ZoomInfo integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent finds the right company match and reports what it is confident about before anything is enriched.
Who maintains the ZoomInfo integration?
fastn does. When ZoomInfo changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Whose credentials does a ZoomInfo lookup run under?
Each customer's own. Quota and cost land on the customer that caused them rather than on a shared key you have to meter and re-bill, and one heavy customer cannot exhaust another's allowance.
How should ZoomInfo results be cached?
Per tenant, with a window that matches how fast the underlying data actually moves. ZoomInfo is a read source rather than a system of record, so the same query returns the same answer until the source changes, and caching is the difference between a sustainable integration and one that exhausts a customer's allowance on a busy page.
What can I build with the ZoomInfo integration?
A common starting point: have each customer connect their own ZoomInfo account so credits come out of their allowance rather than a shared key you then have to re-bill. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the ZoomInfo integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding ZoomInfo does not change your per-connector cost. You can start free with 3 connected accounts.
Add ZoomInfo to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.