Reference & Lookup Data · Integration
FullContact
Add FullContact to your product for your customers, and give your AI agents governed access to it.
Embed a FullContact integration so your customers can enrich the person and company records in your product using their own FullContact entitlement, rather than you reselling a single shared key. Lookups run per tenant with each customer's credentials, so usage and cost sit with the customer who caused them, and every call is logged. fastn handles credential storage, 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 person record from an email address so your forms stay short.
Enrich a company record from a domain so accounts arrive with firmographic detail already filled in.
Enrich records in bulk on import, throttled so a backfill does not exhaust the customer's allowance.
Trigger enrichment when a new record is created in your product and write the result back.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent enriches a contact before drafting outreach so it is not working from an email address alone.
An agent resolves a company domain to firmographic context while qualifying an inbound signup.
An agent enriches a record within governed permissions and writes the result back to your product.
Example prompt
Enrich these five email addresses and tell me which ones resolve to companies over 500 employees.
Set up FullContact in 4 steps
- 01Open the FullContact connector from your fastn dashboard.
- 02Have each customer supply their own FullContact API credentials.
- 03Map the person and company fields your product writes enrichment 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 FullContact integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a FullContact integration without building it. Your customers connect their own FullContact 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 FullContact update is not your on-call problem.
- One integration serves your product and your agents. The same governed FullContact 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 FullContact, across other categories.
Notion
Snowflake
Box
ShopifyFullContact integration FAQ
How do I add a FullContact integration to my product?
Enable the FullContact connector in your fastn dashboard, then let each customer authenticate their own FullContact account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no FullContact client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own FullContact account?
Yes. Every connection is scoped to the individual customer, so each authorises their own FullContact 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 FullContact 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 contact before drafting outreach so it is not working from an email address alone.
Who maintains the FullContact integration?
fastn does. When FullContact 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 FullContact 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 FullContact results be cached?
Per tenant, with a window that matches how fast the underlying data actually moves. FullContact 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 FullContact integration?
A common starting point: enrich a person record from an email address so your forms stay short. 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 FullContact integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding FullContact does not change your per-connector cost. You can start free with 3 connected accounts.
Add FullContact to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.