Integration

Findymail integration

Findymail is a B2B email and phone finder for sales prospecting. Find a person's work email from their name and company or from their business profile URL, find a US phone number, verify an email, look up the profile behind an email, enrich a company, find employees by job title, read a company's technology stack, find lookalike companies, run Intellimatch plain-language lead searches, manage contact lists and exclusion lists, watch buying signals with monitors, and read credit balance and usage. Results are personal data about real people, and most lookups spend finder or verifier credits as each tool says. Left out: the deprecated find-by-domain search. Authentication is a Findymail API key, created on the API page of the Findymail app, sent as a Bearer token.

Connect Findymail How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Findymail.Built from the 35 Findymail tools below, on the connection you add once.

What you can do with Findymail

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Exclusion list, 5 operations

create_exclusion_listCreate exclusion listPOSTCreates an exclusion list (its name must be unique for you), optionally shared with your current team. Add domains to it with add_excluded_domains.
delete_exclusion_listDelete exclusion listDELETEDeletes an exclusion list together with all of its domains. Only the list owner can delete it.
get_exclusion_listGet exclusion listGETReturns one exclusion list (name, sharing, owner) without its domains; list_excluded_domains with list_id returns those. Only lists you own or that your team shares are readable.
list_exclusion_listsList exclusion listsGETLists the exclusion lists you can use (your own and those shared with your team): companies on them are left out of Intellimatch and lookalike searches.
update_exclusion_listUpdate exclusion listPUTRenames an exclusion list and optionally changes whether it is shared with your team. Only the list owner can update it.

List, 4 operations

create_contact_listCreate contact listPOSTCreates an empty contact list with the given name and returns it with its id.
delete_contact_listDelete contact listDELETEDeletes a contact list.
list_contact_listsList contact listsGETLists your Findymail contact lists with their id, name, timestamps and whether each is shared with your team; the id feeds list_saved_contacts.
update_contact_listUpdate contact listPUTRenames a contact list and sets whether it is shared with your team; both values are required.

Monitor, 4 operations

create_monitorCreate monitorPOSTCreates a signal monitor that watches for keyword mentions, new hires, job changes, post engagement or company hiring. Creating is free; each signal it delivers later spends finder credits, more with filters or enrichment.
delete_monitorDelete monitorDELETEDeletes a signal monitor (Findymail soft-deletes it).
list_monitorsList monitorsGETLists your signal monitors and those shared with your team, newest first, with their type, status, keywords, filters, caps and the number of signals each has matched (the webhook URL is not returned).
update_monitorUpdate monitorPATCHUpdates a signal monitor: name (required), keywords, filters, enrichment level, lead list, relevance prompt, cap and sharing. The signal type cannot be changed after creation.

Domain, 3 operations

add_excluded_domainsAdd excluded domainsPOSTAdds up to 10000 domains to an exclusion list (list_id) or to your global exclusion list. Beyond 50 domains, the first 50 are added at once and the rest are queued in the background.
list_excluded_domainsList excluded domainsGETLists excluded domains page by page, from one exclusion list (list_id) or, without it, from your global exclusion list; query filters by domain text.
remove_excluded_domainsRemove excluded domainsDELETERemoves excluded domains by their ids (from list_excluded_domains). Only domains you may delete are removed: your own global ones, and those of shared lists where you hold the remove permission.

Search, 3 operations

search_lookalike_companiesSearch lookalike companiesPOSTFinds companies similar to a seed company domain, optionally only in the same country or size range and without those in given exclusion lists. Costs 1 finder credit per 10 companies returned, rounded up.
search_technologiesSearch technologiesGETSearches Findymail's technology catalog by name and returns up to 25 matching technologies with their category and subcategory. Free; limited to 10 requests per minute.
start_intellimatch_searchStart intellimatch searchPOSTStarts an Intellimatch search: describe target companies in plain language and get a hash. Poll get_intellimatch_status with it, then read get_intellimatch_results. Credits are charged when the export is generated, as config decides.

Signal, 2 operations

get_signalGet signalGETReturns one signal with its type, snippet, dates, the contact and company it concerns, and the monitors that matched it. Personal data.
list_signalsList signalsGETLists buying signals found by your monitors and your team's, page by page: type, snippet, dates, the contact and company concerned, and each monitor's AI relevance score. Filter by type, monitor, dates or scores. Personal data.

Business profile, 1 operation

find_email_by_profileFind email by profilePOSTFinds a person's work email from their business profile URL (or the profile username). Returns the contact found (name, domain, email). Costs 1 finder credit when an email is found, free otherwise. Personal data.

Company, 1 operation

get_company_informationGet company informationPOSTReturns company data (name, domain, size range, industry, profile URL, description) from a company profile URL, a website domain or a company name; pass at least one. Costs 1 finder credit when the company is found.

Credit, 1 operation

get_remaining_creditsGet remaining creditsGETReturns your team's remaining finder or verifier credits (type), the email of the key's user and, on usage-based plans, whether the team can still run requests (has_capacity).

Data, 1 operation

get_intellimatch_resultsGet intellimatch resultsGETReturns one page of a completed Intellimatch search: each company with domain, size, industries, country and match score, plus the contact found (name, email, job title, phone, profile URL) when requested. Personal data.

Employee, 1 operation

find_employeesFind employeesPOSTFinds up to 3 employees of a company holding the given job titles, with name, profile URL and job title (no email: use find_email_by_profile next). Costs 1 finder credit per employee returned. Personal data.

Get, 1 operation

list_saved_contactsList saved contactsGETReturns the contacts saved in Findymail (name, email, business profile URL, company, job title), from one contact list or from all of them. The results are personal data about real people.

Name, 1 operation

find_email_by_nameFind email by namePOSTFinds a person's work email from their full name and company domain or company name. Returns the contact found (name, domain, email). Costs 1 finder credit when an email is found, free otherwise. Personal data.

Phone, 1 operation

find_phoneFind phonePOSTFinds a person's phone number (US numbers only) and its line type from their business profile URL. EU citizens never return a result. Costs 10 finder credits when a phone is found, free otherwise. Personal data.

Reverse email, 1 operation

reverse_email_lookupReverse email lookupPOSTFinds the business profile URL behind an email address (work or personal); with with_profile, also the profile: name, headline, job, location, company, jobs, education. 1 finder credit, plus 1 for the profile; free if none found. Personal data.

Status, 1 operation

get_intellimatch_statusGet intellimatch statusGETReturns the state of an Intellimatch search: success (results ready), processing (with progress and job counts), pending, failed or not_found (unknown or expired hash). Free.

Summary, 1 operation

get_credit_usageGet credit usageGETReturns your own finder and verifier credit usage between two dates, in total and per day (per month for periods of 2 months or more). Defaults to the last 30 days.

Team summary, 1 operation

get_team_credit_usageGet team credit usageGETReturns finder and verifier credit usage per team member between two dates, plus the team total. Defaults to the last 30 days; only team owners can call it.

Technology, 1 operation

lookup_technologies_by_domainLookup technologies by domainPOSTReturns the technology stack detected on a company's domain (name, category, subcategory, last detected date), optionally filtered to given technology names. Costs 1 finder credit when at least one technology is returned.

Verify, 1 operation

verify_emailVerify emailPOSTChecks whether an email address is valid and deliverable. Returns the email, a verified flag and the mail provider. Costs 1 verifier credit per verification, whatever the result.

Use Findymail from Claude Code, Cursor or Codex

Connect Findymail in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Findymail operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Findymail

Create your workspace
Sign up free. Nothing to install.
Connect Findymail once
Add your Findymail connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.