HeyReach MCP | API Key HeyReach connector for AI agents

Tools your outreach agent reaches for on HeyReach, scoped per user.

CALL ANY TOOL

List campaigns and leads, pull stats, add prospects, and track reply and connection rates.

heyreach_add_leads_to_campaign

Add Leads To Campaign

Add up to 100 leads to an existing HeyReach campaign. The campaign must be in an ACTIVE state (IN_PROGRESS), or use resumeFinishedCampaign / resumePausedCampaign to auto-resume. Each lead is bound to a specific LinkedIn sender account (linkedInAccountId) that will send the outreach. Use heyreach_get_campaign_by_id to find the campaign's sender accounts (campaignAccountIds). Rate limit: 300 requests/minute.

Parameters

Name

Type

Required

Description

accountLeadPairs

array

Required

Array of lead + sender account pairs to add to the campaign (max 100). Each pair binds a lead to the LinkedIn sender account that will reach out. Minimum required per lead: profileUrl.

campaignId

integer

Required

The ID of the HeyReach campaign to add leads to. Get campaign IDs from heyreach_get_all_campaigns.

resumeFinishedCampaign

boolean

Optional

If true and the target campaign is in FINISHED state, HeyReach will resume it so the new leads can be processed. Defaults to false.

resumePausedCampaign

boolean

Optional

If true and the target campaign is in PAUSED state, HeyReach will resume it so the new leads can be processed. Defaults to false.

heyreach_check_api_key

Check Api Key

heyreach_get_all_campaigns

Get All Campaigns

heyreach_get_all_linkedin_accounts

Get All Linkedin Accounts

heyreach_get_all_lists

Get All Lists

heyreach_get_campaign_by_id

Get Campaign By Id

heyreach_get_conversations

Get Conversations

heyreach_get_lead

Get Lead

heyreach_get_leads_from_list

List get leads from

heyreach_get_overall_stats

Get Overall Stats

Build your Agent

Drop the toolkit in, point it at the user, and your outreach agent can use HeyReach from the first run.

import { ScalekitClient } from "@scalekit-sdk/node";
import { DynamicStructuredTool } from "@langchain/core/tools";
import { createReactAgent } from "@langchain/langgraph/prebuilt";
import { z } from "zod";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["heyreach"], toolNames: ["heyreach_campaigns_list", "heyreach_campaign_get", "heyreach_leads_list"] },
  pageSize: 100,
});

const lcTools = tools.map((t) => new DynamicStructuredTool({
  name: t.tool.definition.name,
  description: t.tool.definition.description,
  schema: z.object({}).passthrough(),
  func: async (args) => {
    const { data } = await sk.tools.executeTool({
      toolName: t.tool.definition.name,
      identifier: "user_123",
      params: args,
    });
    return JSON.stringify(data);
  },
}));

const agent = createReactAgent({ llm, tools: lcTools });

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

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["heyreach"], toolNames: ["heyreach_campaigns_list", "heyreach_campaign_get", "heyreach_leads_list"] },
  pageSize: 100,
});

const llmTools = tools.map((t) => ({
  type: "function",
  function: {
    name: t.tool.definition.name,
    description: t.tool.definition.description,
    parameters: t.tool.definition.input_schema,
  },
}));

const resp = await openai.responses.create({
  model: "gpt-4o", input: prompt, tools: llmTools,
});

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

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["heyreach"], toolNames: ["heyreach_campaigns_list", "heyreach_campaign_get", "heyreach_leads_list"] },
  pageSize: 100,
});

const llmTools = tools.map((t) => ({
  name: t.tool.definition.name,
  description: t.tool.definition.description,
  input_schema: t.tool.definition.input_schema,
}));

const msg = await anthropic.messages.create({
  model: "claude-sonnet-4-6", max_tokens: 1024,
  tools: llmTools,
  messages: [{ role: "user", content: prompt }],
});

import { Agent } from "@google/adk/agents";
import {
  MCPToolset, StreamableHTTPConnectionParams,
} from "@google/adk/tools/mcp";

const toolset = new MCPToolset({
  connectionParams: new StreamableHTTPConnectionParams({
    url: "https://mcp.scalekit.com/heyreach",
    headers: { Authorization: `Bearer ${userScopedToken}` },
  }),
});

const agent = new Agent({
  name: "agent", model: "gemini-2.0-flash",
  tools: await toolset.getTools(),
});

Try these prompts

Paste any prompt into your agent to start using HeyReach.

Search & status

Copy the prompt

Copied

List all active campaigns.

Copy the prompt

Copied

Get stats for [campaign name].

Copy the prompt

Copied

List leads in [campaign] with status replied.

Copy the prompt

Copied

How many meetings has [campaign] booked?

Action & prospecting

Copy the prompt

Copied

Add [LinkedIn URL] to campaign [name].

Copy the prompt

Copied

Add [list of URLs] to [campaign].

Copy the prompt

Copied

Pause campaign [name].

Copy the prompt

Copied

Get the sequence steps for [campaign].

Reporting & optimization

Copy the prompt

Copied

Compare reply rates across all campaigns.

Copy the prompt

Copied

Which campaigns have connection rate above 40%?

Copy the prompt

Copied

List all leads who replied but didn't book.

Copy the prompt

Copied

Reply rate trend for [campaign] last 30 days.

SEE HOW AUTH WORKS

Users authorize HeyReach once. Their credentials stay vaulted, every call is checked, and every action is logged.

Authorize

Your user connects

HeyReach

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

HeyReach

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

HeyReach

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

HeyReach

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

Same per-user auth pattern across other outreach agents and MCP connectors. Working code, live demos, fork what fits.

SALES

Outbound prospecting agent

Build targeted prospect lists with Apollo, enrich with firmographic data, and draft personalised outreach. Runs on a schedule.

Apollo

View agent

Why Scalekit

Secure your agent's access. Connectors ship in minutes

Other connector libraries treat auth as a demo afterthought. Scalekit starts with user identity, scope enforcement, and audit.

01.

Shared tokens break per-user analytics

A shared token looks fine in a demo. In production every call looks like a service account. Scalekit resolves the real user credential so attribution, audit, and scope stay accurate.

// shared token
 audit → bot_service_account
 user_filter → broken

 // scalekit
 audit → user_abc
 scope → enforced ✓

02.

Authentication is not authorization

03.

Multi-tenancy is architectural

04.

HeyReach today. Others 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 HeyReach as the user or as a shared key?

As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.

Where is the HeyReach api key stored?

In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.

Can I limit what the agent is allowed to do in HeyReach?

Yes. Pass a tool name filter to listScopedTools so the outreach agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches HeyReach.

What happens when a user revokes HeyReach 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 send outreach from another team member's LinkedIn account?

No. Outreach sends only from LinkedIn accounts connected under the authorizing user's HeyReach credentials. The agent cannot impersonate another team member's sender account.

On this page

Tool and actions Framework Compatibility Starter Prompt Auth Lifecycle Try Other Agents Why Scalekit