Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
HeyReach (BYOK) icon

HeyReach (BYOK)

Read your HeyReach LinkedIn outreach campaigns, lead lists, sender accounts, webhooks and overall performance stats with your own API key

Unify Dynamics LLC

Tools9read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProviderHeyReachunofficial, not affiliated
Works withMCP · RESTany agent

Try asking

Real questions, and the tools your agent calls to answer them.

Is my HeyReach API key valid?
Tools called
check_api_key
Which LinkedIn accounts are connected in HeyReach and are they active?
Tools called
list_linkedin_accounts
Show HeyReach LinkedIn account 1234
Tools called
get_linkedin_account
Which HeyReach campaigns are running and how far along are they?
Tools called
list_campaigns
How is HeyReach campaign 321 doing?
Tools called
get_campaign
What lead lists do we have in HeyReach and how big are they?
Tools called
list_lead_lists

About

HeyReach (BYOK) lets an AI assistant read your own HeyReach data through the HeyReach API with a key you supply (HeyReach API key). Read-only: 9 tools (check_api_key, list_linkedin_accounts, get_linkedin_account, list_campaigns, get_campaign, list_lead_lists, get_lead_list, get_overall_stats, list_webhooks). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.heyreach.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by HeyReach. HeyReach and its logos are trademarks of their owners and are used only to say which service the connector works with.

Sources: Live from the HeyReach API (api.heyreach.io) with a BYOK key; documentation: https://docs.heyreach.io/hey-reach-api. Endpoints checked against that documentation on 2026-10-16.

Privacy

The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.

Data not collectedNo account, no profile, no stored prompts or results.

What it can do

9 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI
Read your data9 tools
  • Check api keyCheck that the HeyReach API key works.
  • List linkedin accountsList the connected LinkedIn sender accounts with name, profile URL, active and valid-session flags, active campaign count and today's action limits.
  • Get linkedin accountGet one connected LinkedIn sender account by ID with its status flags, cooldowns and action limits.
  • List campaignsList outreach campaigns with name, status, creation time, linked lead list, sender account IDs and progress counts (total, in progress, pending,…
  • Get campaignGet one campaign by ID with status, linked lead list, sender accounts, exclusion settings and progress counts.
  • List lead listsList lead and company lists with name, item count, creation time and the campaigns using them.
  • Get lead listGet one lead or company list by ID with its item count, creation time and campaigns.
  • Get overall statsGet outreach totals for a date range: profile views, post likes, follows, messages sent and replied, connection requests sent and accepted, and…
  • List webhooksList the webhooks configured in HeyReach with name, target URL, event type, campaign IDs and active flag.

Information

PublisherUnify Dynamics LLC
CategoryWork & productivity
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://byok-heyreach.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide
FunctionOther
LayerDeep connectors

Connect it to your agent

Three ways in, the same 9 tools.

MCP (Claude, Cursor, Windsurf, VS Code, any MCP client)https://byok-heyreach.connectorbay.com/mcp
RESTPOST https://byok-heyreach.connectorbay.com/v1/tools/<tool>
OpenAI function callinghttps://connectorbay.com/openai/byok-heyreach.json
OpenAI-compatible chathttps://connectorbay.com/v1/chat/completions · how it works
  • Add the MCP URL in your client's connector, MCP or integration settings (streamable HTTP, no OAuth).
  • Key: send your HeyReach API key in the X-Upstream-Key header (get one at docs.heyreach.io).
  • Ask a question; the agent picks the right tool and answers from the live data.

HeyReach connector: questions and answers

What is the HeyReach connector?

HeyReach (BYOK) lets an AI assistant read your own HeyReach data through the HeyReach API with a key you supply (HeyReach API key). It is a hosted MCP server with 9 tools such as Check api key, List linkedin accounts, Get linkedin account, List campaigns, Get campaign, List lead lists, published by Unify Dynamics LLC. It is independent and not affiliated with HeyReach.

How do I connect HeyReach to Claude, ChatGPT or Cursor?

Add the MCP endpoint https://byok-heyreach.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-heyreach.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-heyreach.json.

Do I need a HeyReach account or API key?

Yes: this is a bring-your-own-key connector. Create a HeyReach API key at https://docs.heyreach.io/hey-reach-api and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.

Is HeyReach read-only?

Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.

Is the HeyReach connector free?

Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.

More like this

More in Other

Jotform (BYOK)

Read your Jotform forms, questions, submissions, folders and account usage with your own API key

Live · MCP + REST11 tools

JSONBin (BYOK)

Read your JSONBin.io bins and collections with your own master key

Live · MCP + REST7 tools

Juro (BYOK)

Read your Juro contract templates and contracts, with status, owner and dates, using your own API key

Live · MCP + REST5 tools

JustCall (BYOK)

Read your JustCall phone numbers, contacts, SMS texts and threads, tags, user groups, AI voice agents, sales dialer campaigns and call analytics with your own API key and secret

Live · MCP + REST9 tools

Kanka (BYOK)

Read your Kanka worldbuilding campaigns: characters, locations, organisations, notes, quests, journals and items with your own personal access token

Live · MCP + REST12 tools

Kapso (BYOK)

Read your Kapso WhatsApp numbers, conversations, messages, contacts, broadcasts and flows with your own project API key

Live · MCP + REST12 tools

Documentation

Back to top

HeyReach (BYOK) — connector documentation

  • MCP endpoint: https://byok-heyreach.connectorbay.com/mcp
  • REST API: POST https://byok-heyreach.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-heyreach.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own HeyReach HeyReach API key, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-heyreach.connectorbay.com/health · Tool schemas: https://byok-heyreach.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-heyreach · agent@connectorbay.com

What HeyReach (BYOK) is for

HeyReach (BYOK) lets an AI assistant read your own HeyReach data through the HeyReach API with a key you supply (HeyReach API key). Read-only: 9 tools (check_api_key, list_linkedin_accounts, get_linkedin_account, list_campaigns, get_campaign, list_lead_lists, get_lead_list, get_overall_stats, list_webhooks). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.heyreach.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by HeyReach. HeyReach and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Is my HeyReach API key valid?"
  • "Which LinkedIn accounts are connected in HeyReach and are they active?"
  • "Show HeyReach LinkedIn account 1234"
  • "Which HeyReach campaigns are running and how far along are they?"
  • "How is HeyReach campaign 321 doing?"
  • "What lead lists do we have in HeyReach and how big are they?"

What it does

  • check_api_key: Check that the HeyReach API key works. Returns an empty success answer when the key is valid.
  • list_linkedin_accounts: List the connected LinkedIn sender accounts with name, profile URL, active and valid-session flags, active campaign count and today's action limits. Page size is at most 100.
  • get_linkedin_account: Get one connected LinkedIn sender account by ID with its status flags, cooldowns and action limits.
  • list_campaigns: List outreach campaigns with name, status, creation time, linked lead list, sender account IDs and progress counts (total, in progress, pending, finished, failed). Page size is at most 100.
  • get_campaign: Get one campaign by ID with status, linked lead list, sender accounts, exclusion settings and progress counts.
  • list_lead_lists: List lead and company lists with name, item count, creation time and the campaigns using them. Page size is at most 100.
  • get_lead_list: Get one lead or company list by ID with its item count, creation time and campaigns.
  • get_overall_stats: Get outreach totals for a date range: profile views, post likes, follows, messages sent and replied, connection requests sent and accepted, and the reply and acceptance rates. All senders and campaigns are included.
  • list_webhooks: List the webhooks configured in HeyReach with name, target URL, event type, campaign IDs and active flag. Custom header values are not returned.

BYOK key

You bring your own HeyReach HeyReach API key (https://docs.heyreach.io/hey-reach-api). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.heyreach.io over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the HeyReach API (api.heyreach.io) with a BYOK key; documentation: https://docs.heyreach.io/hey-reach-api. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by HeyReach. HeyReach and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your HeyReach account.

Built for: Worldwide. Languages: English.

Privacy policy

Back to top

HeyReach (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What HeyReach (BYOK) is. HeyReach (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own HeyReach data: Read your HeyReach LinkedIn outreach campaigns, lead lists, sender accounts, webhooks and overall performance stats with your own API key. You bring your own HeyReach HeyReach API key; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one HeyReach call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to api.heyreach.io, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If HeyReach rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What HeyReach receives. The request we make on your behalf, including the key and the arguments, under HeyReach's own terms and privacy policy. HeyReach acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer HeyReach gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your HeyReach data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. HeyReach (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at HeyReach at any time to end all access.

Children. HeyReach (BYOK) is a general-audience service operated by the adult using the assistant, under HeyReach's own age rules.

Changes. We will post changes here with a new effective date.

Terms of service

Back to top

HeyReach (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the HeyReach (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

  1. The Service. HeyReach (BYOK) provides: Read your HeyReach LinkedIn outreach campaigns, lead lists, sender accounts, webhooks and overall performance stats with your own API key. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
  2. Your own key, your own account. You must use your own HeyReach credentials and only access data you are allowed to access. HeyReach's terms apply to your use of HeyReach; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
  3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by HeyReach. HeyReach and its logos are trademarks of their owners and are used only to say which service the connector works with.
  4. No advice, no guarantees. Output is the data HeyReach returns, lightly trimmed; it may be incomplete, delayed or changed by HeyReach. Check important facts at the source.
  5. Read-only. The Service does not create, change, send or delete anything in your HeyReach account.
  6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent HeyReach's controls, or to attack any system.
  7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; HeyReach may change or end its API at any time.
  8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
  9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your HeyReach key.
  10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action HeyReach takes on your account. Our total liability is limited to US $100.
  11. Governing law. California law; venue in San Mateo County, California.
  12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-heyreach

HeyReach (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. HeyReach (BYOK) never asks for them.

Get HeyReach (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own HeyReach HeyReach API key. Create one at https://docs.heyreach.io/hey-reach-api, with the fewest permissions it needs (read-only if the provider offers it). Your assistant sends it in the X-Upstream-Key header with every request. It is used for that one call only: never stored, logged or cached, and only ever sent to HeyReach. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with HeyReach.