Reference & Lookup Data · Integration
ContactOut
Add ContactOut to your product for your customers, and give your AI agents governed access to it.
ContactOut is a lookup service rather than a store: you supply a LinkedIn profile URL, a name plus company, or an email, and get back candidate contact details with a status indicating whether each was verified. The people search endpoint is POST-only, so a GET returns 405 rather than anything explanatory, and requests carry both a token header and an authorization header on most plans. Work emails and personal emails come back in separate arrays, and callers routinely merge them and then mail a personal address by mistake. Quota is drawn down per successful reveal rather than per request, so a miss is usually free but a broad search that resolves many profiles is not. Some lookups run live rather than from cache, so response times vary widely across otherwise identical calls. fastn holds each customer's ContactOut credentials, meters their quota and maintains the connector.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own ContactOut key so reveals draw down their credits, not a shared pool.
Enrich a lead record from a LinkedIn URL and store only the verified work email.
Check an existing email against ContactOut's verification status before a sequence is sent.
Run a company plus role search to build a shortlist without leaving your own interface.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Have an agent find a verified work email for a named prospect, with each reveal counted and audited per tenant.
Ask an agent to check whether a stored contact's email still verifies before a campaign goes out.
Let an agent enrich only records that are missing a work email, so no credit is spent twice.
Example prompt
Find a verified work email for this LinkedIn profile.
Set up ContactOut in 4 steps
- 01Enable the ContactOut connector from your fastn dashboard.
- 02Have each customer authorise their own ContactOut account, so calls run under their credentials rather than a shared key.
- 03Decide which lookups, results and reports your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the ContactOut integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a ContactOut integration without building it. Your customers connect their own ContactOut 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 ContactOut update is not your on-call problem.
- One integration serves your product and your agents. The same governed ContactOut 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
APIVoidOften used alongside
Tools the same teams tend to run next to ContactOut, across other categories.
Salesforce
HubSpot
Notion
SnowflakeContactOut integration FAQ
How do I add a ContactOut integration to my product?
Enable the ContactOut connector in your fastn dashboard, then let each customer authenticate their own ContactOut account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no ContactOut client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own ContactOut account?
Yes. Every connection is scoped to the individual customer, so each authorises their own ContactOut 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 ContactOut integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Have an agent find a verified work email for a named prospect, with each reveal counted and audited per tenant.
Who maintains the ContactOut integration?
fastn does. When ContactOut 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 ContactOut 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 ContactOut results be cached?
Per tenant, with a window that matches how fast the underlying data actually moves. ContactOut 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 ContactOut integration?
A common starting point: let a customer connect their own ContactOut key so reveals draw down their credits, not a shared pool. 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 ContactOut integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding ContactOut does not change your per-connector cost. You can start free with 3 connected accounts.
Add ContactOut to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.