ContactOut connector for AI agents

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

CALL ANY TOOL

26 tools for contact data in ContactOut: find emails and phones for profiles, search people and companies, verify emails in bulk, find decision makers, and manage email campaigns.

contactout_add_campaign_recipients

Add campaign recipients

Add up to 100 recipients to an email campaign. Returns success_count, failure_count and results with each recipient's email, status (success, warning or failed) and message. Use contactout_list_campaigns to find the campaign_id. Use contactout_start_campaign to send to them. Requires the Campaigns API to be enabled for your API token; otherwise ContactOut returns 403.

Parameters

Name

Type

Required

Description

campaign_id

string

Required

ID of the campaign to add recipients to. Get it from contactout_list_campaigns (the id field) or from the last segment of the campaign URL in the ContactOut web app. Example: pEVRKd

recipients

array

Required

Recipients to add, 1 to 100. Each recipient needs an email or a valid phone number, and can also have a first name, last name and company. Recipients are processed one by one, so some can fail while others succeed. Example: [{"email": "jane.doe@example.com", "first_name": "Jane", "last_name": "Doe", "company": "Acme"}]

contactout_bulk_get_contact_info

Bulk get contact info

contactout_check_personal_email

Check personal email

contactout_check_phone

Check phone

contactout_check_work_email

Check work email

contactout_count_people

Count people

Count the people that match a set of search filters, without using credits. Returns total_results plus estimated_personal_emails, estimated_work_emails and estimated_phones. Use this to size a search before contactout_search_people, which takes the same filters.

Parameters

Name

Type

Required

Description

company

array

Optional

Company names to match, up to 50. Scope (current or past employer) is set by company_filter. Example: ["Stripe", "Plaid"]

company_filter

string

Optional

Which roles the company filter applies to: current (API default), past, past_only (company in past experience but not the current employer), or both. One of: `current`, `past`, `past_only`, `both`.

company_size

array

Optional

Company headcount ranges, up to 8. Values: 1_10, 11_50, 51_200, 201_500, 501_1000, 1001_5000, 5001_10000, 10001. Example: ["51_200", "201_500"]

current_company_only

boolean

Optional

If true (the API default), company matches only the current employer.

current_titles_only

boolean

Optional

If true (the API default), job_title matches only current roles. Set false to also match past job titles.

current_work_location

array

Optional

Locations where the person currently works, up to 50. Example: ["New York"]

domain

array

Optional

Company website domains to match, up to 50. Example: ["stripe.com"]

education

array

Optional

Schools or degrees to match, up to 50. Supports capitalized AND, OR, NOT. Example: ["Stanford University"]

educations

array

Optional

Structured education filters, up to 50. Each item can set a school name, a field of study and a location. Example: [{"school_name": "Stanford University", "field_of_study": "Computer Science"}]

exclude_companies

array

Optional

Company names to exclude, up to 50. Scope is set by exclude_companies_filter (default both current and past). Example: ["Acme Corp"]

exclude_companies_filter

string

Optional

Which roles exclude_companies applies to: current, past, or both (API default). Independent of company_filter. One of: `current`, `past`, `both`.

exclude_job_titles

array

Optional

Job titles to exclude from results. Example: ["Intern", "Assistant"]

include_related_job_titles

boolean

Optional

If true, also matches job titles related to the ones in job_title. API default is false.

industry

array

Optional

Industries to match, up to 50. Prefix a value with NOT to exclude it, for example "NOT Computer Software". AND and OR are not supported here. Example: ["Financial Services"]

is_currently_working

boolean

Optional

If true, returns only people with an active current role; if false, only people without one. Omit to return both.

job_function

array

Optional

Job functions to filter by, up to 50. Example: ["Engineering", "Sales"]

job_title

array

Optional

Current job titles to match (up to 50). Supports capitalized boolean operators AND, OR, NOT inside a value. Example: ["Head of Sales", "VP Sales"]

keyword

string

Optional

Keyword that appears anywhere in the profile. Supports capitalized AND, OR, NOT. Example: fintech AND payments

languages

array

Optional

Languages the person speaks, up to 50. Each item needs a language name and can list accepted proficiency levels. Example: [{"language": "Spanish", "proficiency": ["Native or bilingual proficiency"]}]

location

array

Optional

Locations where the person lives, up to 50. Example: ["San Francisco, California", "United States"]

location_radius

integer

Optional

Search radius in miles around location, from 1 to 500. Works only when location is a city or area. Example: 25

match_experience

string

Optional

Requires job_title and company to match within the same experience entry: current (API default), past, or both. One of: `current`, `past`, `both`.

name

string

Optional

Full or partial name of the person to find. Example: Jane Doe

past_company

array

Optional

Companies the person worked at in past (non-current) roles, up to 50. Cannot be combined with company_filter past, past_only or both, or with match_experience when both job_title and company are set. Example: ["Google"]

past_job_title

array

Optional

Job titles the person held in past (non-current) roles, up to 50. Supports capitalized AND, OR, NOT. Cannot be combined with current_titles_only false, or with match_experience when both job_title and company are set. Example: ["Software Engineer"]

past_work_location

array

Optional

Locations where the person worked before, up to 50. Example: ["London"]

recently_changed_jobs

boolean

Optional

If true, returns only people whose current job started within the last 3 calendar months. Cannot be used with years_in_current_role.

seniority

array

Optional

Seniority levels to filter by, up to 50. Example: ["Manager", "Vice President"]

skills

array

Optional

Skills to match, up to 50. Supports capitalized AND, OR, NOT. Example: ["Python", "Machine Learning"]

years_in_current_role

array

Optional

Years-in-current-role ranges, up to 20. Example values: 1_2, 3_5. Cannot be used with recently_changed_jobs. Example: ["1_2"]

years_of_experience

array

Optional

Total years of experience ranges, up to 20. Example values: 1_2, 3_5, 6_10, 10. Example: ["3_5", "6_10"]

contactout_create_bulk_contact_info_job

Create bulk contact info job

contactout_create_bulk_email_verification_job

Create bulk email verification job

contactout_enrich_domains

Enrich domains

contactout_enrich_email

Enrich email

contactout_enrich_linkedin_profile

Enrich linkedin profile

contactout_enrich_person

Enrich person

contactout_find_linkedin_by_email

Find linkedin by email

contactout_get_bulk_contact_info_job

Get bulk contact info job

contactout_get_bulk_email_verification_job

Get bulk email verification job

contactout_get_campaign

Get campaign

contactout_get_contact_info

Get contact info

contactout_get_decision_makers

Get decision makers

contactout_get_usage_stats

Get usage stats

contactout_list_campaigns

List campaigns

contactout_remove_campaign_recipients

Remove campaign recipients

contactout_search_companies

Search companies

contactout_search_people

Search people

Search ContactOut's people database with filters such as job title, company, location, skills, seniority, industry and keyword. Returns metadata (page, page_size, total_results) and profiles keyed by LinkedIn URL, each with full_name, title, headline, company, location and contact_availability; contact_info is filled only when reveal_info is true. Use contactout_count_people first to size a search without using credits. Use contactout_get_decision_makers for the leaders of one company. Rate limit: 60 requests per minute.

Parameters

Name

Type

Required

Description

company

array

Optional

Company names to match, up to 50. Scope (current or past employer) is set by company_filter. Example: ["Stripe", "Plaid"]

company_filter

string

Optional

Which roles the company filter applies to: current (API default), past, past_only (company in past experience but not the current employer), or both. One of: `current`, `past`, `past_only`, `both`.

company_size

array

Optional

Company headcount ranges, up to 8. Values: 1_10, 11_50, 51_200, 201_500, 501_1000, 1001_5000, 5001_10000, 10001. Example: ["51_200", "201_500"]

current_company_only

boolean

Optional

If true (the API default), company matches only the current employer.

current_titles_only

boolean

Optional

If true (the API default), job_title matches only current roles. Set false to also match past job titles.

current_work_location

array

Optional

Locations where the person currently works, up to 50. Example: ["New York"]

data_types

array

Optional

Return only profiles that have at least one of these contact data types: personal_email, work_email, phone. Example: ["work_email"]

detailed_education

boolean

Optional

If true, education entries are structured objects (school, degree, years) instead of strings. API default is false.

detailed_experience

boolean

Optional

If true, experience entries are structured objects (title, company, dates) instead of strings. API default is false.

domain

array

Optional

Company website domains to match, up to 50. Example: ["stripe.com"]

education

array

Optional

Schools or degrees to match, up to 50. Supports capitalized AND, OR, NOT. Example: ["Stanford University"]

educations

array

Optional

Structured education filters, up to 50. Each item can set a school name, a field of study and a location. Example: [{"school_name": "Stanford University", "field_of_study": "Computer Science"}]

exclude_companies

array

Optional

Company names to exclude, up to 50. Scope is set by exclude_companies_filter (default both current and past). Example: ["Acme Corp"]

exclude_companies_filter

string

Optional

Which roles exclude_companies applies to: current, past, or both (API default). Independent of company_filter. One of: `current`, `past`, `both`.

exclude_job_titles

array

Optional

Job titles to exclude from results. Example: ["Intern", "Assistant"]

include_related_job_titles

boolean

Optional

If true, also matches job titles related to the ones in job_title. API default is false.

industry

array

Optional

Industries to match, up to 50. Prefix a value with NOT to exclude it, for example "NOT Computer Software". AND and OR are not supported here. Example: ["Financial Services"]

is_currently_working

boolean

Optional

If true, returns only people with an active current role; if false, only people without one. Omit to return both.

job_function

array

Optional

Job functions to filter by, up to 50. Example: ["Engineering", "Sales"]

job_title

array

Optional

Current job titles to match (up to 50). Supports capitalized boolean operators AND, OR, NOT inside a value. Example: ["Head of Sales", "VP Sales"]

keyword

string

Optional

Keyword that appears anywhere in the profile. Supports capitalized AND, OR, NOT. Example: fintech AND payments

languages

array

Optional

Languages the person speaks, up to 50. Each item needs a language name and can list accepted proficiency levels. Example: [{"language": "Spanish", "proficiency": ["Native or bilingual proficiency"]}]

location

array

Optional

Locations where the person lives, up to 50. Example: ["San Francisco, California", "United States"]

location_radius

integer

Optional

Search radius in miles around location, from 1 to 500. Works only when location is a city or area. Example: 25

match_experience

string

Optional

Requires job_title and company to match within the same experience entry: current (API default), past, or both. One of: `current`, `past`, `both`.

name

string

Optional

Full or partial name of the person to find. Example: Jane Doe

output_fields

array

Optional

Limit each profile to these fields, up to 16. Allowed: li_vanity, full_name, title, headline, company, company.name, company.website, company.headquarter, company.domain, company.size, location, industry, experience, education, skills, profile_picture_url. Example: ["full_name", "title", "company.name"]

page

integer

Optional

Page number of results, starting at 1. API default is 1. Example: 2

page_size

integer

Optional

Number of profiles per page, from 1 to 25 (API default 25). Search credits are charged per profile returned. Example: 10

past_company

array

Optional

past_job_title

array

Optional

past_work_location

array

Optional

Locations where the person worked before, up to 50. Example: ["London"]

recently_changed_jobs

boolean

Optional

If true, returns only people whose current job started within the last 3 calendar months. Cannot be used with years_in_current_role.

reveal_info

boolean

Optional

If true, contact_info in each profile is filled with emails and phones, and email/phone credits are charged. API default is false.

seniority

array

Optional

Seniority levels to filter by, up to 50. Example: ["Manager", "Vice President"]

skills

array

Optional

Skills to match, up to 50. Supports capitalized AND, OR, NOT. Example: ["Python", "Machine Learning"]

years_in_current_role

array

Optional

Years-in-current-role ranges, up to 20. Example values: 1_2, 3_5. Cannot be used with recently_changed_jobs. Example: ["1_2"]

years_of_experience

array

Optional

Total years of experience ranges, up to 20. Example values: 1_2, 3_5, 6_10, 10. Example: ["3_5", "6_10"]

contactout_start_campaign

Start campaign

contactout_stop_campaign

Stop campaign

contactout_verify_email

Verify email

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);

// ContactOut tools scoped to this user
const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["contactout"], toolNames: [
    "contactout_search_people",
    "contactout_get_contact_info",
    "contactout_verify_email"] },
  pageSize: 100,
});

const agent = createReactAgent({ llm, tools });
await agent.invoke({ messages: [{ role: "user", content: "Find heads of growth at fintech companies in New York and get their 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: ["contactout"] }, pageSize: 100,
});

const res = await openai.chat.completions.create({
  model: "gpt-5",
  messages: [{ role: "user", content: "Find heads of growth at fintech companies in New York and get their work emails" }],
  tools,
});

// Execute the tool call with the user's vaulted ContactOut API key
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: ["contactout"] }, pageSize: 100,
});

const msg = await anthropic.messages.create({
  model: "claude-sonnet-5",
  max_tokens: 1024,
  messages: [{ role: "user", content: "Find heads of growth at fintech companies in New York and get their work emails" }],
  tools,
});

// Tool call runs with the user's vaulted ContactOut API key
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: ["contactout"] }, pageSize: 100,
});

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

await agent.run("Find heads of growth at fintech companies in New York and get their work emails");

Try these prompts

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

Contact info

Copy the prompt

Copied

Get the work email and phone for this LinkedIn profile.

Copy the prompt

Copied

Find the LinkedIn profile behind jane@northwind.com.

Copy the prompt

Copied

Get emails for these 80 LinkedIn profiles in one job.

Copy the prompt

Copied

How many VPs of Engineering in London work at companies with 200 to 1,000 employees?

Copy the prompt

Copied

Search for heads of growth at fintech companies in New York.

Copy the prompt

Copied

Who are the decision makers at northwind.com?

Verify and campaigns

Copy the prompt

Copied

Is jane@northwind.com deliverable?

Copy the prompt

Copied

Add these 40 contacts to the Q4 Outbound campaign.

Copy the prompt

Copied

Stop the Q4 Outbound campaign.

SEE HOW AUTH WORKS

Each user connects their own ContactOut API key once, and Scalekit sends it with every call. Keys stay vaulted, every call is scope checked, and every action is logged.

Authorize

Your user connects

ContactOut

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

ContactOut

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

ContactOut

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

ContactOut

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 ContactOut API key looks fine in a demo. In production every lookup and campaign change 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 key
audit → bot_service_account

// scalekit
audit → user_abc ✓

02.

Authentication is not authorization

03.

Multi-tenancy is architectural

04.

ContactOut 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 ContactOut as the user or through a shared key?

As the user. Each user connects their own ContactOut API key once, and Scalekit sends it with every call. Credits come from that user's ContactOut account, and audit logs attribute every lookup and campaign change to that user, not a shared service account.

Where is the ContactOut API key stored?

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

Can I limit what the agent does in ContactOut?

Yes. Filter by tool name in listScopedTools to expose only what you want, for example lookups and search without contactout_start_campaign or contactout_remove_campaign_recipients, which start sending a campaign or drop its recipients. Scalekit also enforces scope checks before every API call.

What happens when a user revokes ContactOut 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.

Can the agent check what ContactOut has before spending credits?

Yes. contactout_check_work_email, contactout_check_personal_email, and contactout_check_phone report whether ContactOut has that data for a LinkedIn profile without using credits, on paid plans. contactout_get_usage_stats returns credit usage and quotas for a billing month.