HeyReach

Live

API KEY

OUTREACH

Every LinkedIn campaign, prospect list, and outreach sequence your team runs lives in HeyReach. HeyReach MCP gives your agent authenticated access to LinkedIn outreach data scoped to the user who authorized it.

  • Acts as the user: Access and write actions stay tied to the HeyReach account that authorized the agent.
  • Credentials stay vaulted: AES-256, resolved at request time, never in LLM context.
  • Scoped before every call: User permissions enforced. 90-day audit trail.
HeyReach
agent · Acme Q3
Run
What is the reply rate on our Q4 outbound campaign and how many leads are in each stage?
S
heyreach_stats_get
81ms
Outreach agent
Q4 outbound: 1,240 leads sent. Reply rate 14.2% (176 replies). Connection rate 38.4% (476). 12 meetings booked. 64 leads in follow-up, 38 in negotiation stage.
Sources: Q4 outbound campaign
heyreachmcp
1 campaign
18:29
Message Claude...

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_campaigns_list
List campaigns
List HeyReach campaigns with status and date filters.
Parameters
Name
Type
Required
Description
status
string
Optional
Status: active, paused, completed
limit
integer
Optional
Max campaigns
heyreach_campaign_get
Get campaign
heyreach_leads_list
List leads
heyreach_lead_add
Add lead
heyreach_stats_get
Get campaign 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.
1
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
2
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
3
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
4
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.
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.

Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack
Cursor Code REPL
# ~/.cursor/mcp.json
{
""mcpServers"": {
""heyreach"": {
""url"": ""https://mcp.scalekit.com/heyreach"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.heyreach]
url = ""https://mcp.scalekit.com/heyreach""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""heyreach"": {
""url"": ""https://mcp.scalekit.com/heyreach"",
""type"": ""http""
}
}
}