Reference & Lookup Data · Integration
InsideView
Add InsideView to your product for your customers, and give your AI agents governed access to it.
Embed an InsideView integration so your customers can enrich company and contact records inside your product using their own account and their own entitlement. Every lookup runs per tenant, so one customer's usage never draws down another's, and returned fields map into your own schema as configuration rather than code. fastn handles per-customer credentials, rate limiting, and API upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers enrich a company record in your product with firmographic data from their own account.
Look up contacts at a company so users find who they need without leaving your product.
Fill missing fields on record creation, mapped to each customer's own schema.
Throttle enrichment during a first import so a bulk run does not exhaust a customer's entitlement.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent enriches an account before answering a research question about it.
An agent looks up contacts at a company to ground a recommendation in current data.
An agent writes enriched fields back within governed permissions, with each lookup logged.
Example prompt
Enrich the accounts added this week and list the ones still missing an industry or employee count.
Set up InsideView in 4 steps
- 01Open the InsideView connector from your fastn dashboard.
- 02Have each customer authenticate their own InsideView account.
- 03Map the returned company and contact fields to your schema, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the InsideView integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an InsideView integration without building it. Your customers connect their own InsideView 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 an InsideView update is not your on-call problem.
- One integration serves your product and your agents. The same governed InsideView 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
Dun & BradstreetWorks well with
DemandbaseOften used alongside
Tools the same teams tend to run next to InsideView, across other categories.
Salesforce
HubSpot
Notion
SnowflakeInsideView integration FAQ
How do I add an InsideView integration to my product?
Enable the InsideView connector in your fastn dashboard, then let each customer authenticate their own InsideView account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no InsideView client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own InsideView account?
Yes. Every connection is scoped to the individual customer, so each authorises their own InsideView 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 InsideView 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 answering a research question about it.
Who maintains the InsideView integration?
fastn does. When InsideView 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 an InsideView 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 InsideView results be cached?
Per tenant, with a window that matches how fast the underlying data actually moves. InsideView 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 InsideView integration?
A common starting point: enrich a company record in your product with firmographic data from their own account. 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 InsideView integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding InsideView does not change your per-connector cost. You can start free with 3 connected accounts.
Add InsideView to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.