The HeyReach alternative that books the call

Export each campaign's leads to CSV from HeyReach, or pull them with POST /api/public/campaign/GetLeadsFromCampaign (it returns each lead's campaign, connection and message status). Keep the LinkedIn profile URL, name, company, title, any custom user fields and tags.

Note who has already been contacted and who replied. You will usually leave those people out of Gelee, or put them in a separate follow-up campaign.

Do this first. Before a single lead goes in. Pull your HeyReach blacklist with POST /api/public/blacklist/GetLeads and GetCompanies (or export it from the app), and add every lead you have already contacted that you do not want contacted again.

Then send it over in one call, or add it in the app's Settings. People and whole companies both work, and sending the same list twice won't break anything. Gelee checks it when someone joins a campaign and again right before every message.

curl -X POST "https://www.gelee.ai/api/v1/blacklist" \
  -H "Authorization: Bearer gk_your_key" \
  -H "Content-Type: application/json" \
  -d '{"entries":[
        {"value":"https://www.linkedin.com/in/janedoe","type":"account"},
        {"value":"Acme Corp","type":"company"}
      ]}'

Whoever sends the outreach connects their LinkedIn in the Gelee app, under Accounts. It takes a minute.

One rule matters more than the rest: don't let HeyReach and Gelee both run campaigns from the same seat at the same time. Neither tool knows what the other sent, and LinkedIn sees both. Pause that seat's HeyReach campaigns first, then switch it on in Gelee.

Brand new or rested account? Turn on warm-up and it starts slow.

Paste your HeyReach messages into Gelee steps and swap the variables. If a variable comes back empty, Gelee drops that sentence instead of sending a blank, so you don't need a fallback on every one.

Anything of your own, like a report link or a finding, becomes a custom field: {{custom.field_name}}. If a step needs a field that isn't there yet, it waits for it (up to a day). Handy if you write the link onto the lead when they accept.

• {FIRST_NAME} → {{firstName}}
• company and position fields → {{company}}, {{role}}
• a custom user field → {{custom.field_name}}
• a fallback message → {{custom.field_name|fallback text}}, or let Gelee drop the sentence

A HeyReach sequence is a tree of nodes (connection request, message, InMail, like, follow, view) with a branch for accepted and not accepted. A Gelee campaign is an ordered list of steps that starts with a connection request (outbound) or a message to existing connections (inbound), with a wait before each step. Rebuild the main path: the invite note, then each follow-up message.

Gelee writes the AI lines and replies, so you can keep your copy as written or let Gelee personalise it per lead. A/B variants are per step, and GET /campaigns/{id}/performance shows replies and bookings for each.

Steps HeyReach sends to Instantly, Smartlead or EmailBison have no Gelee equivalent; send those leads to your email tool from a Gelee webhook instead.

Make the campaign, then add people however's easiest: upload the CSV, push them with the API, or point Zapier or Clay at the campaign's intake URL. All Gelee needs is the LinkedIn URL.

Leave out anyone HeyReach already reached, unless you actually want a second touch. Gelee won't put the same person in two of your campaigns anyway.

Mapping from AddLeadsToCampaignV2: profileUrl → linkedin_url, firstName/lastName → first_name/last_name, companyName → company, position → title, emailAddress → email, customUserFields [{name, value}] → custom_fields {name: value}.

curl -X POST "https://www.gelee.ai/api/v1/campaigns/CAMPAIGN_ID/leads" \
  -H "Authorization: Bearer gk_your_key" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: import-batch-1" \
  -d '{"leads":[{"linkedin_url":"https://www.linkedin.com/in/janedoe",
                "first_name":"Jane","company":"Acme","title":"VP Sales",
                "custom_fields":{"report_link":"https://acme.example/r/5d70"},
                "tags":["imported"]}]}'

Map each HeyReach webhook to the Gelee event in the table above. The main differences: Gelee's reply event fires on every reply (check timeline.first_reply_at for the first), invite_sent and message_sent must be picked by name, and Gelee adds bookings, needs_human and lead_updated.

In Gelee, add a webhook under Settings, Event Destinations (or POST /webhooks). Every event comes with the person, the seat that sent and the campaign. Hit Test to get a full sample before anything real flows.

Leave the HeyReach one running until you cut over, so your CRM doesn't have a gap.

Swap the base URL and header, then follow the mapping table. Every Gelee answer about a person carries the same block: name, LinkedIn URL, lead id, the seat that sent, the campaign, stage, booking likelihood and grade, timeline, booking and a link to the conversation. You can usually drop the extra lookups HeyReach code makes to stitch those together.

Sends take an Idempotency-Key header, so a retry never messages someone twice. Keys that send need the "Read + write + send messages" permission.

# HeyReach
curl -X POST "https://api.heyreach.io/api/public/inbox/SendMessage" \
  -H "X-API-KEY: $HEYREACH_KEY" -H "Content-Type: application/json" \
  -d '{"conversationId":"2-ODM0…","linkedInAccountId":123,"message":"Hi Jane"}'

# Gelee
curl -X POST "https://www.gelee.ai/api/v1/inbox/chat_88/messages" \
  -H "Authorization: Bearer $GELEE_KEY" -H "Content-Type: application/json" \
  -H "Idempotency-Key: msg-5d70-1" \
  -d '{"text":"Hi Jane"}'

Don't move everything on day one. Start with a seat or two, run them next to HeyReach for a few weeks, and look at accepts, replies and booked calls. Split by seat, never by person.

Happy? Pause the rest of HeyReach, export one last time, move the remaining seats. Keep that last export. It's your record of who was contacted before.