Switching from another tool

From Dripify

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

Last updated 25 October 2026

Deciding whether to switch?

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

What Dripify offers

Dripify exports leads to CSV and sends lead data out through a webhook URL set in each campaign's settings, which is how its Zapier and Make connections work; it also lists native CRM integrations. Its pricing page (checked 23 October 2026) also lists an open API, an MCP server and HubSpot integration.

Their words, our words

Dripify	Gelee	Notes
Drip campaign	Campaign
LinkedIn account	Seat
Lead	Lead
Campaign webhook	Webhook destination	One destination can cover every campaign, or only chosen ones.
Inbox	Inbox	With the AI SDR drafting or sending replies.

API calls

Every Dripify 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.

Dripify	Gelee	Notes
`Campaign webhook (outbound)`	`Webhooks: reply_received, connection_accepted, …`	Every event carries the person, seat and campaign.
`(not in Dripify's materials)`	`POST /campaigns/{id}/leads, intake URL`	Push leads in from your own tools.
`(not in Dripify's materials)`	`GET /prospects, PATCH /prospects/{id}`	Read leads back and write outcomes, fields and tags.
`(not in Dripify's materials)`	`POST /inbox/{chat_id}/messages`	Send from your own code.

Webhooks

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

Dripify	Gelee webhook	Notes
Webhook on a lead event in a campaign	`reply_received, connection_accepted, invite_sent, message_sent`	Pick the events you want per destination.

Message variables

Dripify	Gelee
`First name`	`{{firstName}}`
`Company`	`{{company}}`
`Position`	`{{role}}`

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

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