Findymail connector for AI agents

Tools your prospecting agent reaches for on Findymail, scoped per user.

CALL ANY TOOL

35 tools for email finding in Findymail: find and verify work emails, find phones and employees, search lookalike companies and tech stacks, track buying signals, and manage lists.

findymail_add_excluded_domains

Add excluded domains

Add domains to an exclusion list, or to your global exclusions when no list is given. Returns success, total, processed_immediately, queued, and list_id. Batches over 50 domains are partly queued for background processing. Use add_excluded_domains to stop Intellimatch and lookalike searches returning these companies. Use remove_excluded_domains to undo.

Parameters

Name

Type

Required

Description

domains

array

Required

Domains to exclude, up to 10000. Example: ["competitor.com", "blocked.io"].

list_id

integer

Optional

Exclusion list to add the domains to. Leave empty to add them as global exclusions. Example: 1.

findymail_create_contact_list

List create contact

findymail_create_exclusion_list

List create exclusion

findymail_create_intellimatch_search

Search create intellimatch

findymail_create_signal_monitor

Create signal monitor

Create a monitor that watches for a type of buying signal, such as keyword mentions, new hires, job changes, post engagement, or company hiring. Returns the new monitor with id, name, signal_type, status, its settings, and match_count. Use create_signal_monitor to start tracking a new signal. Use update_signal_monitor to change an existing one; the signal type can't be changed after creation.

Parameters

Name

Type

Required

Description

name

string

Required

Name of the monitor. Example: Hiring monitor.

signal_type

string

Required

What the monitor watches for: keyword_mention (posts mentioning keywords), new_hire, job_change, post_engagement (likes or comments on a LinkedIn post or profile), or company_hiring (job postings). It can't be changed later. Example: keyword_mention. One of: `keyword_mention`, `new_hire`, `job_change`, `post_engagement`, `company_hiring`.

ai_relevance_prompt

string

Optional

Optional instructions, up to 500 characters, that Findymail's AI uses to score how relevant each matched signal is. Example: Focus on Series B+ SaaS companies hiring VP Sales.

engagement_types

array

Optional

Which engagement to track on a post_engagement monitor: like, comment, or both. Required for post_engagement monitors. Example: ["like", "comment"].

enrichment_level

string

Optional

How much to enrich matched contacts: email, or email_phone for email plus phone. Example: email. One of: `email`, `email_phone`.

icp_filters

object

Optional

Optional ideal-customer-profile filters that narrow which signals match. The object can hold industries (LinkedIn industry names), employee_count_ranges (any of 1-10, 11-50, 51-200, 201-500, 501-1000, 1001-5000, 5001-10000, 10001+), countries (2-letter ISO codes), job_title_keywords (up to 10), and seniority_levels (numbers: 1 Entry, 4 IC, 6 Senior IC, 8 Management, 9 Director, 11 VP, 13 Executive, 14 C-Suite, 15 Founder). job_title_keywords and seniority_levels are rejected for company_hiring monitors. Example: {"industries": ["Biotechnology"], "employee_count_ranges": ["51-200"], "countries": ["US", "FR"], "seniority_levels": [11, 13]}.

is_shared

boolean

Optional

true to share the monitor with your current team. Defaults to false. Example: false. Default: `false`.

job_offer_title_keywords

array

Optional

Job posting title keywords to watch for, up to 10, matched as case-insensitive substrings with OR logic. Required for company_hiring monitors and rejected for every other type. Example: ["Account Executive", "SDR"].

keywords

array

Optional

Keywords to track, up to 5. Required for keyword_mention monitors, and for post_engagement monitors that don't set post_url. Example: ["hiring", "fundraise"].

lead_list_id

integer

Optional

ID of a Findymail contact list to add matched contacts to automatically. Get IDs from list_contact_lists. Example: 42.

post_url

string

Optional

For post_engagement monitors: the LinkedIn post URL to watch. Use this or profile_url, or keywords. Example: https://www.linkedin.com/posts/johndoe_activity-123.

profile_url

string

Optional

For post_engagement monitors: a LinkedIn profile whose posts to watch, as an alternative to post_url. Example: https://www.linkedin.com/in/johndoe.

target_companies

array

Optional

Company names or domains to limit signals to, up to 100. Only allowed on new_hire and job_change monitors; any other type returns a 422. Example: ["stripe.com", "Notion"].

webhook_url

string

Optional

Optional HTTPS URL that Findymail calls when new signals match this monitor. Example: https://example.com/webhooks/signals.

findymail_delete_contact_list

List delete contact

findymail_delete_exclusion_list

List delete exclusion

findymail_delete_signal_monitor

Delete signal monitor

findymail_find_email_by_business_profile

Find email by business profile

findymail_find_email_by_name

Find email by name

findymail_find_employees

Find employees

findymail_find_phone

Find phone

findymail_get_company

Get company

findymail_get_credits

Get credits

findymail_get_intellimatch_results

Get intellimatch results

findymail_get_intellimatch_status

Get intellimatch status

findymail_get_signal

Get signal

findymail_get_team_usage_summary

Get team usage summary

findymail_list_contact_lists

List contact lists

findymail_list_contacts

List contacts

findymail_list_excluded_domains

List excluded domains

findymail_list_signal_monitors

List signal monitors

findymail_list_signals

List signals

findymail_lookup_company_technologies

Lookup company technologies

findymail_remove_excluded_domains

Remove excluded domains

findymail_reverse_email_lookup

Reverse email lookup

findymail_search_lookalike_companies

Search lookalike companies

findymail_search_technologies

Search technologies

findymail_update_contact_list

List update contact

findymail_update_signal_monitor

Update signal monitor

Update a signal monitor's name, keywords, filters, enrichment, sharing, or webhook. The signal type can't be changed. Returns the updated monitor with id, name, signal_type, status, its settings, and match_count. Use update_signal_monitor to adjust a monitor. Use create_signal_monitor to track a different signal type.

Parameters

Name

Type

Required

Description

monitor_id

integer

Required

The numeric ID of the monitor to update. Example: 1.

name

string

Required

The monitor's name. Pass the current name to keep it. Example: Updated monitor name.

ai_relevance_prompt

string

Optional

Optional instructions, up to 500 characters, that Findymail's AI uses to score how relevant each matched signal is. Example: Focus on Series B+ SaaS companies hiring VP Sales.

engagement_types

array

Optional

Which engagement to track on a post_engagement monitor: like, comment, or both. Required for post_engagement monitors. Example: ["like", "comment"].

enrichment_level

string

Optional

How much to enrich matched contacts: email, or email_phone for email plus phone. Example: email. One of: `email`, `email_phone`.

icp_filters

object

Optional

is_shared

boolean

Optional

true to share the monitor with your team, false to unshare it. Only the owner or a team admin can change this. Leave empty to keep the current setting. Example: true.

job_offer_title_keywords

array

Optional

keywords

array

Optional

Keywords to track, up to 5. Required for keyword_mention monitors, and for post_engagement monitors that don't set post_url. Example: ["hiring", "fundraise"].

lead_list_id

integer

Optional

ID of a Findymail contact list to add matched contacts to automatically. Get IDs from list_contact_lists. Example: 42.

target_companies

array

Optional

Company names or domains to limit signals to, up to 100. Only allowed on new_hire and job_change monitors; any other type returns a 422. Example: ["stripe.com", "Notion"].

webhook_url

string

Optional

Optional HTTPS URL that Findymail calls when new signals match this monitor. Example: https://example.com/webhooks/signals.

For more tools, view docs.

Build your Agent

Same auth pattern across LangChain, OpenAI, Anthropic, and Google ADK.

import { ScalekitClient } from "@scalekit-sdk/node";
import { createReactAgent } from "@langchain/langgraph/prebuilt";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

// Findymail tools scoped to this user
const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["findymail"], toolNames: [
    "findymail_find_employees",
    "findymail_find_email_by_name",
    "findymail_verify_email"] },
  pageSize: 100,
});

const agent = createReactAgent({ llm, tools });
await agent.invoke({ messages: [{ role: "user", content: "Find heads of sales at northwind.com and their verified work emails" }] });

import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["findymail"] }, pageSize: 100,
});

const res = await openai.chat.completions.create({
  model: "gpt-5",
  messages: [{ role: "user", content: "Find heads of sales at northwind.com and their verified work emails" }],
  tools,
});

// Execute the tool call with the user's vaulted Findymail access token
await sk.tools.executeTool(res.choices[0].message.tool_calls[0], "user_123");

import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["findymail"] }, pageSize: 100,
});

const msg = await anthropic.messages.create({
  model: "claude-sonnet-5",
  max_tokens: 1024,
  messages: [{ role: "user", content: "Find heads of sales at northwind.com and their verified work emails" }],
  tools,
});

// Tool call runs with the user's vaulted Findymail access token
await sk.tools.executeTool(msg.content, "user_123");

import { Agent } from "@google/adk/agents";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["findymail"] }, pageSize: 100,
});

const agent = new Agent({
  name: "prospecting_agent",
  model: "gemini-2.5-pro",
  instruction: "Findymail tools scoped to this user",
  tools,
});

await agent.run("Find heads of sales at northwind.com and their verified work emails");

Try these prompts

Copy any prompt into your agent. Each maps directly to a Findymail tool. Click to copy, paste into your agent, done.

Find and verify

Copy the prompt

Copied

Find the work email for Priya Shah at northwind.com.

Copy the prompt

Copied

Is jane@northwind.com deliverable?

Copy the prompt

Copied

Find the phone number for this LinkedIn profile.

Accounts

Copy the prompt

Copied

Find heads of sales at northwind.com.

Copy the prompt

Copied

Find companies similar to northwind.com.

Copy the prompt

Copied

What technologies does northwind.com use?

Signals and lists

Copy the prompt

Copied

List new buying signals from my monitors.

Copy the prompt

Copied

Create a monitor for companies hiring sales engineers.

Copy the prompt

Copied

Add acme.com to our customer exclusion list.

SEE HOW AUTH WORKS

Each user connects their own Findymail access token once, and Scalekit sends it with every call. Tokens stay vaulted, every call is scope checked, and every action is logged.

Authorize

Your user connects

Findymail

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

Limited to user

Store

Their

Findymail

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

Resolve

When your agent calls a

Findymail

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

Audit

Every

Findymail

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Test other agents

See the same per-user auth pattern across other sales and prospecting connectors.

GTM and RevOps Teams

Outbound prospecting agent

Searches Apollo for prospects matching your ICP, scores and ranks them, drafts personalized outreach in Gmail, and logs every send to Google Sheets. Mail goes out as the rep, not from a shared inbox.

GTM and RevOps Teams

CRM AI agent

Reads the Granola transcript after every call, extracts next steps and updates the HubSpot record, drafts the follow-up in Gmail, and confirms in Slack, all on the rep's own delegated OAuth.

Why Scalekit

Secure your agent's access. Connectors ship in minutes

01.

Shared tokens break per-user analytics

A shared Findymail access token looks fine in a demo. In production every email lookup looks like one service account, and you cannot tell which user triggered it. Scalekit resolves the credential of the actual user who triggered the agent, never a shared bot.

// shared token
audit → bot_service_account

// scalekit
audit → user_abc ✓

02.

Authentication is not authorization

03.

Multi-tenancy is architectural

04.

Findymail today. Ten connectors tomorrow.

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

FAQs

Frequently Asked Questions

Does the agent access Findymail as the user or through a shared token?

As the user. Each user connects their own Findymail access token once, and Scalekit sends it with every call. Credits come from that user's Findymail account, and audit logs attribute every request to that user, not a shared service account.

Where is the Findymail access token stored?

In Scalekit's managed AES-256 token vault, namespaced per tenant. To rotate it, the user reconnects with a new access token. Revocation is a single dashboard action. Credentials never appear in prompts, logs, or LLM context.

Can I limit what the agent does in Findymail?

Yes. Filter by tool name in listScopedTools to expose only what you want, for example find and verify tools without findymail_delete_contact_list or findymail_delete_exclusion_list. Scalekit also enforces scope checks before every API call.

What happens when a user revokes Findymail access?

The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

What are Findymail signals?

Buying signals that Findymail monitors detect, such as new hires, job changes, or company hiring. findymail_create_signal_monitor sets up a monitor for a type of signal, findymail_list_signals lists what your monitors and team-shared monitors found, and findymail_get_signal returns one signal with its contact and company.