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

Octopus CRM alternative

Switching from Octopus CRM to Gelee

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

Side by side

Gelee vs Octopus CRM

FeatureGeleeOctopus CRM
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✓Processed history
Per-account limits for invites, messages, reads, likes and comments✓Unlimited plan
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✓–
A/B tests with results per message✓–
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✓–
Flags threads that need a follow-up✓–
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✓Via Zapier
Public API and webhooks✓Zapier hook only
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✓–

Should you switch?

Is Gelee the right Octopus CRM alternative?

Switch to Gelee if

  • It runs in the cloud. Octopus is a Chrome extension: your browser has to be open. Gelee runs all day without your computer on.
  • Replies drafted for you. We found no AI reply feature on Octopus's site. Gelee drafts every reply and sends your booking link.
  • A real do-not-contact list. Octopus skips people in its processed history. Gelee keeps a blacklist of people and companies and checks it before every send.

Stay on Octopus CRM if

  • You run one LinkedIn account from your browser, send a handful of invites a week, and are happy writing every reply yourself.
  • Your outreach depends on visit and endorse campaigns or on invites sent by email.

What you'd give up: A Chrome extension on your own browser. Gelee runs in the cloud instead. Visit and endorse campaigns, and Connect by Email.

How to switch

Moving from Octopus CRM in 9 steps

Export each Octopus campaign to CSV, connect Gelee to Claude or ChatGPT, build your do-not-contact list from the people you have already processed, connect your LinkedIn account, rebuild each funnel as one Gelee campaign, and upload the leads. If a Zapier Catch Hook received Octopus data, point the Zap at a Gelee webhook instead.

Run both for a week on different people, then cancel Octopus. One Octopus subscription is one LinkedIn account; in Gelee, add as many seats as you need, or a workspace per client.

  1. Export your Octopus campaigns

    In each Octopus campaign, click EXPORT TO CSV. You get the processed users with first name, last name, email, website, LinkedIn URL, company and position. Do it for every campaign in a funnel, so you know who was only invited, who got the first message, and who got the follow-ups.

    Octopus's processed history is the only record of who you contacted. Export it now, before you clear anything.

  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 Octopus CRM. It starts with get_started, which lists what is already set up and what is left, and it can read your Octopus CRM 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. Octopus has no blacklist to export. Build the list from your CSVs: everyone already messaged whom you do not want contacted again, plus customers and anyone you avoided by hand.

    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 Octopus CRM 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 Octopus CRM 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 Octopus CRM 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}}
    • Position → {{role}}
    • anything of your own → {{custom.field_name}}
  6. Turn each funnel into one campaign

    An Octopus funnel is a Connect campaign linked to a Message campaign, sometimes with a Visit or Endorse campaign first. A Gelee campaign holds all of it: the invite note, then each message with its wait, sent only to people who accepted. Visit and endorse have no Gelee step; leave them out.

    Octopus has no reply handling beyond stopping. In Gelee the AI SDR 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.

    Or paste your Octopus CRM 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 Octopus CRM 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 Octopus CSV: LinkedIn URL → linkedin_url, first name and last name → first_name and last_name, company → company, position → title, email → email.

    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

    If a Zap catches Octopus profile data per campaign, start it from a Gelee webhook instead, and pick the events you want. A HubSpot connection made through Zapier can become Gelee's native HubSpot integration in the app.

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

  9. Run both for a week, then cancel Octopus CRM

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

    Happy? Pause the rest of Octopus CRM, export one last time, move the remaining seats, then cancel the Octopus CRM 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 Octopus CRM. 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 replaces Octopus funnels?

One Gelee campaign. The invite is the first step and each follow-up message is a later step with a wait. Follow-ups only go to people who accepted, so you do not link campaigns or forward people by hand.

Does Gelee have an export like Octopus's CSV?

Yes, and more. GET /prospects returns every lead with its seat, campaign, stage, score, timeline and booking, or ask the assistant for the list. The conversations themselves show up in Gelee as soon as the seat connects.

I have several Octopus subscriptions, one per account. How does that work in Gelee?

One workspace, as many seats as you need, each with its own limits and warm-up. If the accounts belong to different clients, give each client a workspace of its own under yours.

Can I run Octopus CRM 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 Octopus CRM 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 Octopus CRM 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 Octopus CRM API mapping7 API calls, 3 webhook events, terms and message variables, in the docs →

Switch

Moving from Octopus CRM? Start in ten minutes.

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