New You can now run your Gelee campaigns from Claude, ChatGPT or Cursor. Read the docs →
Home Free tools and guides Blog Switch to Gelee Docs Pricing Get started Sign in

Dux-Soup alternative

Switching from Dux-Soup to Gelee

Bring your leads, do-not-contact list and campaigns over from Dux-Soup. We do the move with you.

Side by side

Gelee vs Dux-Soup

FeatureGeleeDux-Soup
Finding buyers
Live buying signals (hiring, funding, job changes)✓–
Evergreen lists that add new matches every day✓–
Sales Navigator searches that refill themselves✓–
Contact and company details added to every lead✓–
Each prospect rechecked against your criteria before sending✓–
Filters for followers, headcount, industry and mutuals✓–
Every lead scored before you reach out✓–
Reaching them
Each prospect contacted from your best-fit account✓–
Free DMs and Open Profile InMails before paid ones✓–
Skips anyone already messaged or in another campaign✓✓
Per-account limits for invites, messages, reads, likes and comments✓–
Gradual warm-up for new accounts✓–
Old pending invites withdrawn for you✓✓
Post engager campaigns✓–
Keyword search and follower campaigns✓–
Comment-a-keyword campaigns that send a resource✓–
Referral campaigns that ask your network for intros✓–
AI variables in every message✓Full AI messages
A/B tests with results per message✓Clone campaigns
Ready-made campaign templates✓–
Do-not-contact list✓–
AI writes and schedules your LinkedIn posts✓–
Replies and booking
AI drafts replies with your booking link (you approve, or autopilot)✓–
Can book the meeting inside the DM (calendar connected)✓–
One inbox for every account✓–
Tag replies as interested or lost✓AI qualify
Flags threads that need a follow-up✓Ask the AI
Tracked links that show which messages booked✓–
Slack alerts, and answer replies from Slack✓✓
Setup and plumbing
Set up for you by our team✓–
CRM integrations✓✓
Public API and webhooks✓–
MCP for Claude and ChatGPT✓–
Connect LinkedIn accounts from the API or your AI assistant✓–
Discord alerts✓–
For agencies
A separate workspace for every client✓✓
One MCP connection for all your clients✓Team-wide MCP

Should you switch?

Is Gelee the right Dux-Soup alternative?

Switch to Gelee if

  • Bring your own AI key. Dux-Soup's AI previews and response assistant run on your own OpenAI key. Gelee's AI SDR is built in and drafts every reply.
  • Lists that refill themselves. Gelee keeps adding new people who match your ICP every day, so a campaign does not run dry.
  • Nothing to install. Gelee runs in the cloud on every plan. No desktop app, no legacy extension.

Stay on Dux-Soup if

  • Your campaigns depend on profile visits, endorsements, follows or liked posts as steps.
  • You want your LinkedIn automation to run on your own machine, and you are happy bringing your own OpenAI key for replies.

What you'd give up: Visit, follow, endorse and like-a-post actions, and the visit and scan webhooks that go with them. There is no desktop app: Gelee runs in the cloud.

How to switch

Moving from Dux-Soup in 10 steps

Export your campaign prospects from Dux-Soup, connect Gelee to Claude or ChatGPT, bring your blacklisted profiles over, connect your LinkedIn accounts, rebuild the drip campaign and add the leads. Swap Dux-Soup's webhooks and queue commands for Gelee's using the tables below.

Move one seat first, run both for a week or more, then cancel Dux-Soup. Agencies get one Gelee workspace per client, pooled seats, and one MCP connection for all of them.

  1. Export your Dux-Soup prospects

    Open the Prospects panel (in the desktop app, at the bottom of the Funnel Flow, or in the Team or Agency Dashboard for admins), filter by campaign, and click Export to CSV. Do it once per campaign so you keep each person's campaign and connection status. Export your tags from the Tag Tool as well, since the blacklisted tag lives there.

    If you still use the legacy extension, Download Data gives you the visited profiles with Profile URL, names, Company Name, Industry, Location, Notes and Tags. Keep the LinkedIn profile URL, name, company, title and tags; those are what Gelee reads.

    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.

  2. Connect Gelee to Claude or ChatGPT

    You can do every step below by hand in the app. The quicker way is to let an assistant do it with you. In Claude, go to Settings, Connectors, Add custom connector, name it Gelee and paste the server address. In ChatGPT, go to Settings, Connectors, Create, paste the address and choose OAuth. Sign in with your Gelee login, pick the workspace, and say whether it may make changes.

    Then tell it you are moving from Dux-Soup. It starts with get_started, which lists what is already set up and what is left, and it can read your Dux-Soup export, add your do-not-contact list, connect LinkedIn accounts, build the campaign, bring the leads over and set up webhooks. Anything that sends, launches or cannot be undone waits for your yes.

    Running Gelee for several clients? Give it their websites and it creates one workspace per client under yours, with your team already inside and each client's logo, knowledge base and ideal customer read from the site. Seats are pooled across your client workspaces and counted on your plan.

    claude mcp add --transport http gelee https://web.gelee.ai/api/v1/mcp \
      --header "Authorization: Bearer gk_your_key"
  3. Bring your do-not-contact list over first

    Do this before any lead goes in. Export the prospects carrying the blacklisted tag from the Tag Tool, add the profiles and companies your Profile Skipper and company patterns skip, and add everyone already contacted that you do not want contacted again.

    Then send it over in one call, add it in the app's Settings, or hand the file to the assistant and ask it to add everyone to the blacklist. 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"}
          ]}'
  4. Connect your LinkedIn accounts

    Whoever sends the outreach connects their LinkedIn in the Gelee app, under Accounts. It takes a minute. From Claude or ChatGPT, ask for a login link (seat_connect) and log in there, or paste the account's li_at cookie if you already have it (seat_connect_cookie). The link is the safer way: the cookie is your LinkedIn login and stays in your chat history.

    The most important rule: don't let Dux-Soup 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 Dux-Soup campaigns first, then switch it on in Gelee.

    Brand new or rested account? Warm-up starts on its own and ramps up slowly.

  5. Swap your message variables

    Paste your Dux-Soup 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.

    • _FN_ → {{firstName}}
    • _CN_ → {{company}}
    • _TI_ → {{role}}
    • _IN_ → {{industry}}
    • a custom marker from a CSV column → {{custom.column_name}}
    • a fallback → {{custom.column_name|fallback text}}, or let Gelee drop the sentence
  6. Rebuild the drip campaign

    A Dux-Soup drip campaign chains Connect, Message, Endorse, InMail, Follow, Like a post and Visit actions with delays. A Gelee campaign is an ordered list of invite and message steps, each with a wait. Rebuild the main path: the invite note, then each follow-up message. Endorse, follow, like and visit actions have no Gelee step; leave them out.

    Dux-Soup stops the sequence when a prospect replies unless its AI response assistant is on, and that assistant runs on your own OpenAI key. In Gelee the AI SDR is built in: it drafts every reply with your booking link, you approve each one or turn on autopilot, and needs_human tells you when a reply needs a person.

    If you used AI Preview to personalise each message, Gelee's AI variables do the same inside a step, from the person's profile and your own fields.

    Or paste your Dux-Soup messages into Claude or ChatGPT and ask Gelee to build the campaign. It sets it up the way the app does, one question at a time, reads the whole thing back, and launches only after you say yes.

  7. Add your leads

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

    Leave out anyone Dux-Soup already reached, unless you want a second touch. Gelee won't put the same person in two of your campaigns anyway, and it checks the blacklist again before every send.

    Mapping from the Dux-Soup CSV: Profile URL → linkedin_url, First Name and Last Name → first_name and last_name, Company Name → company, Title → title, Tags → tags. Anything else goes into custom_fields.

    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"]}]}'
  8. Repoint your integrations

    Map each Dux-Soup webhook event to the Gelee event in the table above. Make scenarios that start from the Dux-Soup Watch Events trigger start from a Gelee webhook instead; Zapier zaps that pushed queue commands push leads into a Gelee campaign through the intake URL. HubSpot, Pipedrive and Salesforce workflows that read Dux-Soup visit events read Gelee's connection_accepted and reply events instead.

    In Gelee, add a webhook under Settings, Event Destinations (or POST /webhooks, or ask the assistant). Every event comes with the person, the seat that sent and the campaign. Hit Test to get a full sample before anything real flows. HubSpot connects from the app's integrations card.

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

  9. Port your API code

    Dux-Soup's API queues one action at a time for one LinkedIn session. Gelee's works at the level of campaigns and conversations: you add a person to a campaign and the seat sends the invite and follow-ups on schedule, inside its limits. Code that queued connect and message commands becomes a POST /campaigns/{id}/leads call; code that read the queue reads lead_accepted and lead_rejected webhooks or GET /prospects.

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

    # Dux-Soup: queue a message for one profile
    curl -X POST "https://app.dux-soup.com/xapi/remote/control/$USERID/queue" \
      -H "X-Dux-Signature: $HMAC" -H "Content-Type: application/json" \
      -d '{"targeturl":"https://www.dux-soup.com/xapi/remote/control/'$USERID'/queue",
           "timestamp":1730000000000,"userid":"'$USERID'",
           "command":"message","params":{"profile":"https://www.linkedin.com/in/janedoe","messagetext":"Hi _FN_"}}'
    
    # Gelee: reply in the thread
    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"}'
  10. Run both for a week, then cancel Dux-Soup

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

    Happy? Pause the rest of Dux-Soup, export one last time, move the remaining seats, then cancel the Dux-Soup subscription. Keep that last export. It's your record of who was contacted before, and the assistant can read it later if you ever need to check.

What you gain

Included on every plan

Live buying signalsLists that refill themselvesLead details filled inTargeting rechecked before outreachBest people firstMore ways to find peopleBest accounts on best prospectsEvery account, tunedSmart warm-upFree InMailsReplies drafted for youUpdates in SlackSet up for youAPI, webhooks and MCP

Let AI do it

Let Claude or ChatGPT do the move

The Gelee MCP already knows Dux-Soup. Connect it to Claude or ChatGPT and tell it what you use today. It checks with you before anything sends.

Set up the MCP

Questions

Common questions

What happens to my Dux-Soup queue commands?

Most of them become a campaign. Enroll and connect become POST /campaigns/{id}/leads into a campaign whose first step is the invite; message and inmail become POST /inbox/{chat_id}/messages or POST /conversations; tag and untag become PATCH /prospects/{id}. Visit, follow, endorse and likepost have no Gelee equivalent.

How do Dux-Soup's _FN_ markers map to Gelee?

_FN_ is {{firstName}}, _CN_ is {{company}}, _TI_ is {{role}} and _IN_ is {{industry}}. Anything from your own CSV columns becomes {{custom.column_name}}. If a variable is empty, Gelee drops the sentence rather than sending a blank.

Does Gelee have an MCP like Dux-Soup's?

Yes. Connect https://web.gelee.ai/api/v1/mcp to Claude, ChatGPT, Claude Code or Cursor and it can do anything you can click in the app, including the move itself. Anything that sends or launches waits for your yes.

Can I run Dux-Soup and Gelee at the same time?

Yes. Just don't run both on the same LinkedIn seat at once, and don't let them message the same people. Split by seat and you're fine.

Will I lose my Dux-Soup conversation history?

No. The conversations live on LinkedIn, so they show up in Gelee once the seat connects. What doesn't come over is the other tool's own notes, tags and stats. Export those before you cancel.

Do I need the API to switch?

No. You can do all of this in the app, or by talking to Claude or ChatGPT with Gelee connected. The API is there if you'd rather your own systems do it.

Can Claude or ChatGPT do the switch for me?

Mostly, yes. Connect Gelee to Claude or ChatGPT (the server address is https://web.gelee.ai/api/v1/mcp) and it can do anything you can click in the app: connect seats, add your blacklist, build campaigns, bring leads over, set up webhooks and integrations, and for agencies create one workspace per client. It shows you a preview and waits for your yes before anything sends or launches. If you ask for something Gelee can't do yet, it sends the request to our team.

I run Dux-Soup for several clients. How does that move?

Each client gets its own Gelee workspace under your agency's, made from the app, from POST /workspaces, or by giving the assistant the clients' websites. Your team is inside every one, seats are pooled across them and counted on your plan, and there is no limit on how many client workspaces you can have. Move one client at a time, seat by seat.

How long does a switch take?

Setup is about a day, less with the assistant doing it with you. The part that takes time is watching both side by side for a week or two before you move everything.

For developers: the Dux-Soup API mapping11 API calls, 11 webhook events, terms and message variables, in the docs →

Switch

Moving from Dux-Soup? Start in ten minutes.

Add your website and launch your first campaign. Bring your lists and do-not-contact list as you go.