Reference & Lookup Data · Integration
Findymail
Add Findymail to your product for your customers, and give your AI agents governed access to it.
Findymail serves its API from app.findymail.com/api rather than an api subdomain, and it behaves like a web application first: a request without an Authorization header is answered with a 302 redirect to the login page rather than a 401, so a client that follows redirects will parse an HTML sign-in page and report a confusing failure. Sending an Accept header of application/json alongside the bearer token is what makes it answer as an API. Lookups come in two shapes, one by person name plus company domain and one by LinkedIn profile URL, and the LinkedIn path resolves cases the name path cannot because it does not depend on the domain being guessed correctly. Verification is a separate call from finding, and credits are only consumed when an address is actually found or confirmed, so a failed lookup is cheap. Remaining credits are readable from their own endpoint, which is worth checking before a bulk run. fastn holds each customer's own token, keeps it current, and keeps lookups and credit spend attributed per tenant.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Findymail account so email lookups in your product draw on their credits
Resolve a work email from a name and company domain when a lead arrives without one
Verify an address before your product writes it into a customer's outbound sequence
Show a customer their remaining credit balance before they start a bulk enrichment run
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent find and verify a contact's work email before drafting outreach, with each lookup and its credit cost audited per tenant
Have an agent resolve an email from a LinkedIn profile URL when the company domain is unknown
Allow an agent to check a tenant's remaining credits and stop a bulk run before it exhausts them
Example prompt
Find and verify the work email for this LinkedIn profile, and tell me how many credits we have left.
Set up Findymail in 4 steps
- 01Enable the Findymail connector from your fastn dashboard.
- 02Have each customer authorise their own Findymail 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 Findymail integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Findymail integration without building it. Your customers connect their own Findymail 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 Findymail update is not your on-call problem.
- One integration serves your product and your agents. The same governed Findymail 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 Findymail, across other categories.
Salesforce
HubSpot
Notion
SnowflakeFindymail integration FAQ
How do I add a Findymail integration to my product?
Enable the Findymail connector in your fastn dashboard, then let each customer authenticate their own Findymail account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Findymail client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Findymail account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Findymail 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 Findymail integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Let an agent find and verify a contact's work email before drafting outreach, with each lookup and its credit cost audited per tenant
Who maintains the Findymail integration?
fastn does. When Findymail 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 Findymail 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 Findymail results be cached?
Per tenant, with a window that matches how fast the underlying data actually moves. Findymail 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 Findymail integration?
A common starting point: let a customer connect their own Findymail account so email lookups in your product draw on their credits. 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 Findymail integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Findymail does not change your per-connector cost. You can start free with 3 connected accounts.
Add Findymail to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.