Automations · Webhook
HeyLinked + Make
An HTTP module receives the event and routes it onward.

Setup
- 1
Create a custom webhook in Make.
- 2
Paste the address into HeyLinked and choose the events.
- 3
Make does not need a HeyLinked app.
In practice
On reply.interested, create a deal and assign a task to the person who owns the account.
What HeyLinked sends
POST https://hook.example.com/…
X-HeyLinked-Event: reply.interested
X-HeyLinked-Timestamp: 1763560000
X-HeyLinked-Signature: sha256=…
{
"id": "4f1c…",
"event": "reply.interested",
"created_at": "2026-11-19T09:12:00.000Z",
"campaign": { "id": "…", "name": "Architects Zurich" },
"company_uid": "CHE-101.500.085",
"email": "lena.keller@example.ch",
"step_position": 2
}How it works
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.
Questions
Make
Is there a native Make app?
No app is needed. A webhook address from Make is enough.
Which events arrive?
reply.received, reply.interested, reply.not_interested, email.bounced, email.unsubscribed. Each request is signed with HMAC-SHA256 over timestamp, dot, and raw body in X-HeyLinked-Signature.
Start looking for your next customers
Create an account, start the free trial, and add data or signal capacity when needed.
Our Swiss team replies in person.






