Switching from another tool
From Dux-Soup
Dux-Soup's API calls, webhooks, terms and message variables, each mapped to its Gelee equivalent.
The plain-English guide covers what you gain, what you give up and when to stay on Dux-Soup: Switching from Dux-Soup to Gelee.
What Dux-Soup offers
Dux-Soup now sells its product as STACKED, as a desktop app (STACKED local) or hosted (STACKED cloud); the Chrome extension is listed as an alternative setup and the old Dux-Soup Pro is marked legacy. Its support site documents a LinkedIn Activity API (the former Remote Control API) that queues commands such as visit, enroll, connect, message, inmail, tag, follow, endorse and likepost at app.dux-soup.com/xapi/remote/control/{USERID}/queue with an HMAC signature, plus prospect, campaign, messaging, user settings, team monitoring and reporting APIs. The API needs a Turbo, Cloud or STACKED licence.
Up to five webhooks send visit, scan, action, message, rccommand and session events; message events need the Message Bridge. Prospects export to CSV from the Prospects panel, tags export from the Tag Tool, and the legacy Download Data screen lists its columns. An MCP server at app.dux-soup.com/mcp is available to STACKED users. Blacklisting works by applying a tag named blacklisted.
Their words, our words
| Dux-Soup | Gelee | Notes |
|---|---|---|
| Drip campaign (Preconnect, Postconnect, Connect, Visit) | Campaign | Outbound campaigns start with an invite; inbound ones message existing connections. |
| Prospect | Lead | |
| LinkedIn session / seat | Seat | One connected LinkedIn account. |
| Tags | Tags | Plus inbox flags: interested, lost, referral, follow-up. |
| Tag "blacklisted" | Blacklist | A real list, with people and companies, checked before every send. |
| Qualified Funnel | Interested flag and booking | The AI SDR marks the reply, sends your link and records the booking. |
| Message Bridge / Unified Messaging | Inbox | Every seat's conversations in one place, with drafts waiting for you. |
| Dashboard / Admin Portal (team and agency) | Agency workspace and client workspaces | One child workspace per client, seats pooled across them. |
| Dux-Soup MCP (app.dux-soup.com/mcp) | Gelee MCP (web.gelee.ai/api/v1/mcp) | Claude, ChatGPT, Claude Code and Cursor. |
API calls
Every Dux-Soup call we found in its docs, and the Gelee call that does the same job. Gelee's base URL, keys and limits are in Keys and limits.
| Dux-Soup | Gelee | Notes |
|---|---|---|
queue: enroll (profile into a campaign) | POST /campaigns/{id}/leads, or the campaign's intake URL | Only the LinkedIn URL is required. |
queue: connect (with messagetext) | A campaign's invite step | Gelee sends invites from campaigns, not one command at a time, so limits and warm-up hold. |
queue: message, inmail | POST /inbox/{chat_id}/messages, POST /conversations | Takes an Idempotency-Key; POST /conversations starts a new thread or InMail. |
queue: tag, untag | PATCH /prospects/{id} { tags: { add, remove } } | |
queue: visit, follow, endorse, likepost, savetopdf, saveaslead | Not available | Gelee has no visit, follow, endorse or like actions. |
Prospect API, Messaging & Activity API | GET /prospects, GET /people/{id}, GET /inbox, GET /inbox/{chat_id}/messages, GET /prospects/{id}/activity | Every answer carries the seat, campaign, stage, score and booking. |
Campaign Management API | GET, POST, PATCH /campaigns, POST /campaigns/{id}/launch, /pause | |
User Settings API (webhooks, limits) | POST, GET, PATCH, DELETE /webhooks; PATCH /seats/{id} | Seat limits and warm-up per account. |
Team Monitoring API (/accounts, /status, /kpis, /funnel) | GET /seats, GET /health, GET /analytics/daily, GET /workspaces | Health shows planned versus sent with the reasons for any gap. |
Reporting & Discovery API | GET /analytics, GET /campaigns/{id}/performance | |
Zapier actions (Connect, Message, Enroll, Tag, …) | Gelee webhooks, the intake URL and POST /campaigns/{id}/leads | Gelee's Zapier use runs through webhooks and the intake URL rather than a native app. |
Webhooks
Gelee signs every delivery and retries failures. Setup and signature checks are in Webhooks.
| Dux-Soup | Gelee webhook | Notes |
|---|---|---|
| message received (MEMBER_TO_MEMBER, INMAIL) | reply_received, message_received | reply_received is for people in your campaigns, with reply_positive and reply_negative by sentiment; message_received is every message, picked by name. |
| message received (INVITATION_ACCEPT) | connection_accepted | |
| action create: connectProfile | invite_sent | Pick by name. |
| action create: messageProfile, inmailProfile | message_sent | Pick by name. message.message_type says INMAIL for InMails. |
| message sent (MEMBER_TO_MEMBER) | message_sent | |
| action create: disconnectProfile | No webhook | |
| action create: followProfile, endorseProfile, pdfProfile, saveasleadProfile | No webhook | Gelee has no follow, endorse, PDF or save-lead actions. |
| visit create / update, scan create | No webhook | Gelee does not visit or scan profiles as a campaign step. |
| rccommand received, completed, error | lead_accepted, lead_rejected | The verdict on each lead you push, with the reason. |
| session create / update | account_disconnected, account_reconnected | Plus account_rate_limited when LinkedIn slows a seat down. |
| (none) | call_booked, needs_human, lead_updated, campaign_completed | Bookings, replies the AI handed to a person, lead changes and campaign ends. |
Message variables
| Dux-Soup | Gelee |
|---|---|
_FN_ | {{firstName}} |
_LN_ | {{fullName}} (first and last together) |
_CN_ | {{company}} |
_TI_ | {{role}} |
_IN_ | {{industry}} |
_LO_ (location) | Not a built-in variable; send it as {{custom.location}} |
Custom message markers from a Revisit Data upload | {{custom.field_name}} |
Every Gelee variable:
| Value | Gelee variable |
|---|---|
| First name | {{firstName}} |
| Full name | {{fullName}} |
| Company | {{company}} |
| Job title | {{role}} |
| Industry | {{industry}} |
| Your own per-lead field | {{custom.your_field}} |
| A fallback when empty | {{custom.your_field|default text}} |
| Sender's name | {{senderName}} |
Code from the guide
claude mcp add --transport http gelee https://web.gelee.ai/api/v1/mcp \
--header "Authorization: Bearer gk_your_key"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"}
]}'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"]}]}'# 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"}'