--- title: "Findymail Integration" description: "Find and verify B2B work emails and look up direct phone numbers with Findymail. Agents complete a contact record and confirm it is deliverable before the sequence spends a send on it." url: https://flowrunner.ai/integrations/findymail date_modified: 2026-08-07T17:20:23-07:00 --- # Findymail [Sales Intelligence](https://flowrunner.ai/integrations/category/crm-sales) Find and verify B2B work emails and look up direct phone numbers with Findymail. Agents complete a contact record and confirm it is deliverable before the sequence spends a send on it. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 8 actions · API key · available [Findymail website](https://findymail.com/) · [Platform Documentation](https://www.findymail.com/api) · Capability data verified 2026-08-02 1. A target account is marked for a multithreaded approach 2. Find People At Company returns the buying committee by job title 3. Find Email resolves each contact, verified in the same response 4. Enrich Company attaches size, industry and firmographics to the account 5. Find Phone Number resolves direct dials for the contacts that justify one 6. Rep receives emails cleared for sending and phone numbers listed separately 7. Rep decides which contacts get called before any number enters the dialer ## What This Integration Enables Findymail takes a position most finders avoid: it verifies every address its finder returns, so Verify Email exists mainly for addresses that came from somewhere else. That collapses the usual two-step find-then-verify pattern into one operation, and it removes the window where an unverified address sits in a CRM field looking exactly like a verified one. A credit is charged only when an address is actually found, so the flow does not pay for the misses either. For an agent, this is simpler in a way that matters, because every branch that existed to handle "found but not yet verified" disappears. The second thing Findymail is good at is working an account rather than a contact. Find People At Company takes a company website and optional job titles and returns the people who match, charging per contact returned. Combined with Enrich Company for firmographics and Reverse Email Lookup for inbound signals, an agent can go from a domain to a mapped buying committee inside one flow. Find Phone Number resolves a direct dial from a profile URL at ten credits per hit, and Findymail is explicit that this lookup excludes the European Union for GDPR reasons, which is a design decision the vendor made and worth building around rather than working around. Everything here is synchronous with no submit-and-poll cycle, and Findymail documents support for up to 300 concurrent requests by default, so a flow can widen out across a list without queueing behind itself. ### Without FlowRunner **Find then verify**: Two tools, two steps, and addresses that reach a sequence before the second one runs **Single-threaded accounts**: Outreach depends on one contact who may never reply **Undifferentiated channels**: Email and phone are treated as interchangeable ways to reach the same person ### With FlowRunner **Verified on arrival**: The finder returns addresses it has already checked, so there is no unverified window **Committees, not contacts**: A target account resolves into the several people who actually decide together **Channels chosen deliberately**: Phone lookups are separated from email and routed through a decision, not a default ## Use Case Scenarios ### Mapping a buying committee An account gets promoted to the target list with a domain and no contacts. The agent calls Find People At Company with the titles that matter for the deal shape, then Find Email for each returned person, taking the verified address directly from the response. Enrich Company fills in size, industry and LinkedIn presence on the account record. The agent writes the whole committee into [Pipedrive](https://flowrunner.ai/integrations/pipedrive) as linked contacts on a single account, tagged with the role that produced each one, and hands the rep a picture of the account rather than a single name to chase. Multithreading stops being a discipline the rep has to remember and becomes the default shape of the record. ### Identifying who just signed up A trial signup arrives with an email address and nothing else. The agent calls Reverse Email Lookup, which returns the person's name and company, and with Include Profile enabled returns their fuller professional profile at the cost of a second credit. It then calls Enrich Company on the resulting domain. Before the first onboarding email goes out, the record shows whether this is a solo evaluator at a five-person company or a director at a target account, and routes accordingly. The routing decision is made on real firmographics instead of on the domain suffix. ### A list search that respects its own cost An SDR describes the people they want in plain language, such as heads of revenue operations at mid-market software companies. The agent passes that to Find Leads, which searches the Intellimatch database, and it sets the configuration toggles deliberately, because whether contact records and email addresses are resolved as part of the search changes how many credits the search consumes. It checks Get Credits first and alerts in [Slack](https://flowrunner.ai/integrations/slack) if the balance will not cover the intended resolution depth. The team gets the list, and nobody discovers the cost after the fact. ## Human-in-Loop Highlight Findymail draws a line most vendors leave to the customer: Find Phone Number excludes the European Union, and the reason it gives is GDPR. That tells you something about the operation. A direct dial resolved from a profile URL reaches a phone the person never handed to you, and depending on where they sit, calling it may require a legal basis that a target list does not supply. The agent has no way to determine that from the record. So it does the work and stops at the channel decision: "Buying committee for \[Account\] is mapped. \[N\] verified emails cleared for sequencing. Direct dials found for \[N\] contacts, \[N\] credits spent. Numbers listed below with the country on the enriched company record. Confirm which of these should go into the dialer queue, and which should stay on email only?" The rep answers per contact. Emails proceed automatically because they are verified and the channel is understood. Phone numbers wait, because a phone call is a more intrusive contact than an email and the connector itself has already signalled that jurisdiction changes the answer. That split is the whole point of [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) on a connector like this one. Agents do the finding. People decide who gets called. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via email Human decides Agent resumes with decision ## Agent Capabilities 8 actions ### Email 3 - **Find Email** Finds a person's verified work email from their full name plus a company domain. Findymail verifies every address it returns, so results are ready to mail without a separate verification step. One credit is charged only when an address is found. - **Verify Email** Checks whether an address is valid and deliverable, returning the verification outcome and the detected mail provider. Used on addresses sourced elsewhere, since the connector's own finder results are already verified. - **Reverse Email Lookup** Identifies the person behind an email address, returning their name and company. Include Profile returns their fuller professional profile at the cost of a second credit. Used to enrich inbound signups and form submissions that arrive with only an address. ### Lead Finding 2 - **Find Leads** Searches the Intellimatch lead database from a natural-language query describing the people you want, such as a role at a type of company, and returns matching leads. Configuration toggles control whether contact records and email addresses are resolved during the search, which changes credit consumption. - **Find People At Company** Finds people working at a given company website, optionally narrowed to specific job titles, up to a requested count. One credit is charged per contact returned. Used to build a buying committee at a target account without knowing anyone's name. ### Phone 1 - **Find Phone Number** Finds a direct phone number for a person from their LinkedIn profile URL. Ten credits are charged when a number is found. For GDPR reasons this lookup excludes the European Union, so expect no result for EU-based contacts. ### Company 1 - **Enrich Company** Returns firmographic details for a company domain, including company name, size, industry and LinkedIn presence, at one credit per lookup. Used to enrich an account record when all you hold is a website address. ### Account 1 - **Get Credits** Returns the remaining credit balance on the account. Used to gate a large enrichment run, or to raise an alert before credits are exhausted partway through a campaign. Finder credits are consumed only when a result comes back. ## Frequently Asked Questions ### What can FlowRunner do with Findymail? FlowRunner agents can run Find Email, Verify Email, and Find Leads in Findymail, plus 5 more actions. ### Does connecting Findymail to FlowRunner require OAuth? No. Findymail connects to FlowRunner with an API key, no OAuth flow required. ### Can Findymail trigger a FlowRunner workflow automatically? Findymail doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Findymail?** This integration exposes Findymail to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/findymail. Site index: https://flowrunner.ai/llms.txt