The Waalaxy alternative that books the call

Export each prospect list or campaign to CSV from Waalaxy. Filter first if you only want some of them. Keep the LinkedIn URL, name, company, title and status.

Do this first. Before a single lead goes in. Collect the prospects you excluded in Waalaxy, plus anyone already contacted.

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 Waalaxy 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 Waalaxy campaigns first, then switch it on in Gelee.

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

Paste your Waalaxy 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 → {{company}}
• job title → {{role}}

Rebuild the invite and message steps with their waits. Visit and follow steps are not Gelee steps.

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 Waalaxy already reached, unless you actually want a second touch. Gelee won't put the same person in two of your campaigns anyway.

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"]}]}'

Where a Waalaxy CRM sync step or webhook feeds Zapier, Make or n8n, replace it with a Gelee webhook. Gelee also has an API for writing back.

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 Waalaxy one running until you cut over, so your CRM doesn't have a gap.

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

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