Reference & Lookup Data · Integration
Lusha
Add Lusha to your product for your customers, and give your AI agents governed access to it.
Embed a Lusha integration so enrichment inside your product runs on each customer's own Lusha account, their own credits and their own data entitlement rather than a shared key you have to meter. Lusha exposes verified contact and company data, so a form fill or an imported list becomes a record your product can route, score and act on. Calls are scoped per tenant and logged, which matters when the underlying data is licensed per customer, and pagination and throttling are handled so a bulk enrichment job does not exhaust an allowance. fastn owns the credentials and API upkeep, and the same governed connection serves your AI agents.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers connect their own Lusha account so enrichment in your product runs on their credits and their entitlement, not a shared key.
Enrich a contact or company the moment the record is created so a form fill becomes something your product can route.
Fill in missing work emails, phone numbers and company details before a record is scored or assigned.
Keep every enrichment call attributable to the tenant that made it, which is what licensed data usually requires.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent enriches a prospect before it drafts outreach, using the customer's own Lusha entitlement.
An agent checks whether a record already has verified details before spending a credit, with each call audited.
An agent completes a list of accounts with company details and reports what it could not find.
Example prompt
Enrich these new signups with Lusha and tell me which ones look like a fit.
Set up Lusha in 4 steps
- 01Enable the Lusha connector in your fastn dashboard.
- 02Have each customer authorise their own Lusha account so calls run on their credits.
- 03Map which fields you enrich and when enrichment should run, per customer.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Lusha integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Lusha integration without building it. Your customers connect their own Lusha 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 Lusha update is not your on-call problem.
- One integration serves your product and your agents. The same governed Lusha 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
LeadIQ
FullContactOften used alongside
Tools the same teams tend to run next to Lusha, across other categories.
Salesforce
HubSpot
Notion
SnowflakeLusha integration FAQ
How do I add a Lusha integration to my product?
Enable the Lusha connector in your fastn dashboard, then let each customer authenticate their own Lusha account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Lusha client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Lusha account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Lusha 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 Lusha 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 a prospect before it drafts outreach, using the customer's own Lusha entitlement.
Who maintains the Lusha integration?
fastn does. When Lusha 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 Lusha 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 Lusha results be cached?
Per tenant, with a window that matches how fast the underlying data actually moves. Lusha 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 Lusha integration?
A common starting point: connect their own Lusha account so enrichment in your product runs on their credits and their entitlement, not a shared key. 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 Lusha integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Lusha does not change your per-connector cost. You can start free with 3 connected accounts.
Add Lusha to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.