HeyLinked inside the tools you already use.

Assistants drive the work through MCP. Your own programs use the API. Make, Zapier, n8n, Slack, and the CRMs share one address. An app inside every system is not required for that.

Assistants

The assistant searches, reads lists and campaigns, and creates drafts. Sending and new recipients stay behind a confirmation, so nobody spends credits or sends mail without a limit.

Cursor

MCP

HeyLinked as a tool in the editor, with your API key.

Add an MCP server in Cursor at https://heylinked.io/api/mcp. The header is Authorization: Bearer and the key from Settings → API & MCP. Campaigns and webhooks need the Campaigns scope on that key.

“Find IT companies in Zurich with a website and show the running campaigns.” Setting a campaign to active, or enrolling companies, happens only when the tool sends confirm true.

Claude

MCP

Sign-in through your HeyLinked account, with no key in the chat.

Add https://heylinked.io/api/mcp in Claude. Claude follows the OAuth hint, you sign in, and you choose the rights for this workspace. The access belongs to the signed-in person.

“Who replied this week, and in which campaign?” Claude sees only what the chosen rights allow.

ChatGPT

MCP

The same sign-in as Claude.

ChatGPT uses the same MCP address. The first call without access leads to sign-in at HeyLinked. You confirm the workspace and the rights. After that, the tools match Cursor and Claude.

“Pause the Architects Zurich campaign.” Pausing stops sending. Starting again stays behind the confirmation.

Your own programs

The same work, without an assistant. The key and the rights are the same as for MCP.

REST API

API

Search, people, campaigns, replies, and webhooks under /api/v1.

Every call carries Authorization: Bearer and the key. Read, unlock, campaigns, and signals are separate rights. The reference lives at /entwickler.

An internal tool searches companies, unlocks only the ones that fit, and writes the UID into its own system. Credits are spent only on the unlock.

CSV

File

Lists as a file, for Excel or a CRM that only imports files.

Export from the workspace. The file is the same set you see in the product. Locked contact details stay locked.

A reviewed list goes to Excel, you cut it down, and only what remains goes back into a campaign.

Automations

One HTTPS address under Settings → API & MCP. HeyLinked posts JSON on reply, interested, not interested, bounce, and unsubscribe. The receiver checks X-HeyLinked-Signature with the secret: HMAC-SHA256 over timestamp, a dot, and the raw body.

Make

Webhook

An HTTP module receives the event and routes it onward.

Create a custom webhook in Make. Paste the address into HeyLinked and choose the events. Make does not need a HeyLinked app.

On reply.interested, create a deal and assign a task to the person who owns the account.

Zapier

Webhook

Webhooks by Zapier, trigger Catch Hook.

Create the Catch Hook and paste the address into HeyLinked. That is the connection. There is no listed Zapier app, and this path does not need one.

Each reply becomes a row, with company, email, campaign, and time.

n8n

Webhook

The Webhook node takes the same JSON.

Set the Webhook node to POST and paste the production URL into HeyLinked. Same events, same signature.

Write replies into your own database and post a short note to the sales channel at the same time.

Slack

Webhook

An incoming webhook URL from Slack, saved in HeyLinked.

Create an incoming webhook for the channel and save it in HeyLinked. Choose reply or interested. There is no HeyLinked app in the Slack directory.

#sales sees the company, campaign, and email as soon as someone replies.

CRM and records

HubSpot, Pipedrive, Salesforce, and the spreadsheets hang off Make, Zapier, or n8n. HeyLinked does not install a package or an app there. The JSON carries the event, campaign, UID, and email, so the scenario can find the right record.

HubSpot

Webhook

A contact, company, or deal once someone is interested.

Make or Zapier receives reply.interested and writes to HubSpot. You map the fields in the scenario: email, company name, campaign, UID.

An interested company becomes a deal in the Outbound pipeline, owned by the person running the campaign.

Pipedrive

Webhook

A person and a deal from the same address.

Make or Zapier creates a person on reply or interest and, if you want, a deal. The campaign can land in its own field.

The owner opens the deal and sees which sequence the reply came from.

Salesforce

Webhook

A task or an opportunity when the team already works in Salesforce.

Zapier or Make writes to Salesforce. HeyLinked does not install a package in the org and does not need a Salesforce IT review, as long as the Zap runs as an existing user.

On a reply, a task on the contact. On interest, an opportunity named after the campaign.

Attio

Webhook

A record in Attio, built in Make or Zapier.

The scenario calls Attio with HeyLinked’s JSON. Person, company, email, and campaign are enough for the first record.

A new reply, a new person record, status open.

Google Sheets

Webhook

One row per event.

Zapier or Make appends time, event, company, email, and campaign to the sheet. The sheet is the simplest handoff when no CRM is in play yet.

The weekly list of replies for standup, without anyone copying out of HeyLinked.

Notion

Webhook

A row in a Notion database.

Make or Zapier creates the item. Status, campaign, and email come from the JSON.

Replies land in the Conversations database, status open.

Airtable

Webhook

A row in the base, for RevOps to filter.

Make or Zapier writes into the table. Bounces and unsubscribes can be their own view.

RevOps filters bounces and drops those addresses from the next list.

Events inward

The way out is the webhook. The way in is the API: your system tells HeyLinked that something happened at a company.

Signals from a shop, site, or CRM

API

POST /api/v1/signals attaches an event to the company. It does not cost a credit.

The key needs the Signals right. The body carries title and company_uid or company_name. An unknown UID is rejected. idempotency_key keeps the same company from being filed twice.

The shop reports “demo booked”. The signal sits on the company, and the next piece of research can see the reason.

Start looking for your next customers

Create an account, start the free trial, and add data or signal capacity when needed.

Create account
  • Neschmil
  • Tim
  • Nadine
  • Nina
  • Pascal

Our Swiss team replies in person.