New You can now run your Gelee campaigns from Claude, ChatGPT or Cursor. Read the docs →

Switching from another tool

From Octopus CRM

Octopus CRM's API calls, webhooks, terms and message variables, each mapped to its Gelee equivalent.

Last updated 3 November 2026

Deciding whether to switch?

The plain-English guide covers what you gain, what you give up and when to stay on Octopus CRM: Switching from Octopus CRM to Gelee.

What Octopus CRM offers

Octopus CRM is a Chrome extension with four action tabs (Connect, Message, Visit, Endorse), a Personal CRM with stats, and funnels built by linking campaigns, so that people who accept a connecting campaign move into a message campaign. Its site lists Starter, Pro, Advanced and Unlimited plans and an Agency option for 20 or more accounts, with one shared feature list that includes Export / import data, Build funnels and Integration with Zapier / Hubspot.

Export to CSV downloads a campaign's processed users with first name, last name, email, website, LinkedIn URL, company and position. The only integration documented is a per-campaign Zapier field that takes a Webhooks by Zapier Catch Hook URL, with a Batch profiles option; HubSpot is reached through Zapier. We found no public REST API, no outbound event names, no blacklist (Octopus skips anyone in its processed history) and no AI or MCP features on its site. One Octopus account runs one LinkedIn account.

Their words, our words

Octopus CRMGeleeNotes
Campaign (Connect, Message, Visit or Endorse)A step in a campaignGelee campaigns hold the invite and the follow-up messages together.
Funnel (linked campaigns)CampaignThe invite, then each message with its wait. No linking needed.
Processed users / HistoryBlacklist and "already contacted"A real list, checked before every send, plus a skip for anyone a seat already messaged.
Personal CRM with statsLeads, inbox and analyticsEvery lead with its stage, score, timeline and booking.
LinkedIn account (one per subscription)SeatAdd as many as you need to one workspace.
Zapier integration (Catch Hook per campaign)Webhook destinationOne destination can cover every campaign.
PREMIUM and CUT list buttonsCampaign filtersTitles, places, company size and more, rechecked before every send.

API calls

Every Octopus CRM 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.

Octopus CRMGeleeNotes
Export to CSVGET /prospects, GET /prospects?campaign_id=…Every lead with its seat, campaign, stage, score, timeline and booking.
Import a CSV of LinkedIn profilesA CSV or Google Sheet upload, POST /campaigns/{id}/leads, or the intake URLOnly the LinkedIn URL is required.
Zapier Catch Hook (per campaign, batched)WebhooksSigned, with the person, seat and campaign on every event.
Link campaigns (funnel), FORWARDA campaign with several stepsAccepted people get the next message after the wait you set.
Visit, Endorse campaignsNot availableGelee has no visit or endorse actions.
Connect by Email (Unlimited plan)Not availableGelee sends invites, free InMails to Open Profiles, and messages.
(not in Octopus's materials)POST /inbox/{chat_id}/messages, POST /conversations, PATCH /prospects/{id}, POST /blacklistSend, update leads and manage the blacklist from your own code.

Webhooks

Gelee signs every delivery and retries failures. Setup and signature checks are in Webhooks.

Octopus CRMGelee webhookNotes
Zapier hook: profile processed by a campaigninvite_sent, message_sent, connection_acceptedPick invite_sent and message_sent by name.
(none)reply_received, reply_positive, reply_negative, needs_humanReplies, sorted by sentiment, and the ones the AI handed to a person.
(none)call_booked, lead_updated, campaign_completed

Message variables

Octopus CRMGelee
First Name{{firstName}}
Last Name{{fullName}} (first and last together)
Company{{company}}
Position{{role}}
(no custom variables documented){{custom.field_name}}

Every Gelee variable:

ValueGelee 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 Code
claude mcp add --transport http gelee https://web.gelee.ai/api/v1/mcp \
  --header "Authorization: Bearer gk_your_key"
Push the blocklist
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"}
      ]}'
Push leads with your own 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"]}]}'

Octopus CRM's docs