Reference & Lookup Data · Integration
DiscoverOrg
Add DiscoverOrg to your product for your customers, and give your AI agents governed access to it.
Embed a DiscoverOrg integration, now part of ZoomInfo, so your customers can enrich their records with company and contact data from inside your product using their own subscription and entitlements. Lookups run per tenant so usage is attributable to the customer that caused it, pagination and throttling are handled for you, and a bulk enrichment run is rate-limited so it does not exhaust a customer's allowance. fastn handles each customer's credentials and API upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers enrich their own company and contact records inside your product with their own entitlements.
Fill missing firmographic fields on signup so your product's records are usable straight away.
Map returned fields to each customer's own schema so enrichment lands where they expect it.
Re-check records on a schedule so stale company and contact data is refreshed automatically.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent enriches an account before drafting research or outreach.
An agent looks up contacts at a company within governed permissions and per-tenant entitlements.
An agent reacts to a new record in your product and enriches it before the next workflow step.
Example prompt
Enrich the accounts created this week that are missing industry or employee count, and list what could not be matched.
Set up DiscoverOrg in 4 steps
- 01Open the DiscoverOrg connector from your fastn dashboard.
- 02Have each customer authenticate their own subscription with least-privilege credentials.
- 03Map the company and contact fields your product writes into, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the DiscoverOrg integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a DiscoverOrg integration without building it. Your customers connect their own DiscoverOrg 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 DiscoverOrg update is not your on-call problem.
- One integration serves your product and your agents. The same governed DiscoverOrg 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
ClearbitWorks well with
Salesforce
HubSpotOften used alongside
Tools the same teams tend to run next to DiscoverOrg, across other categories.
Notion
Snowflake
Box
ShopifyDiscoverOrg integration FAQ
How do I add a DiscoverOrg integration to my product?
Enable the DiscoverOrg connector in your fastn dashboard, then let each customer authenticate their own DiscoverOrg account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no DiscoverOrg client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own DiscoverOrg account?
Yes. Every connection is scoped to the individual customer, so each authorises their own DiscoverOrg 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 DiscoverOrg 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 enriches an account before drafting research or outreach.
Who maintains the DiscoverOrg integration?
fastn does. When DiscoverOrg 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 DiscoverOrg 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 DiscoverOrg results be cached?
Per tenant, with a window that matches how fast the underlying data actually moves. DiscoverOrg 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 DiscoverOrg integration?
A common starting point: enrich their own company and contact records inside your product with their own entitlements. 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 DiscoverOrg integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding DiscoverOrg does not change your per-connector cost. You can start free with 3 connected accounts.
Add DiscoverOrg to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.