Switching from another tool

From Aimfox

Aimfox'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 Aimfox: Switching from Aimfox to Gelee.

What Aimfox offers

Aimfox has an API (docs at docs.aimfox.com) with keys made under Workspace Settings, API keys, in two permission levels (all, or read-only for GET calls). Its help center describes syncing leads, adding profiles to campaigns, sending messages, setting lead labels and notes, and managing account limits; its n8n guide lists conversation actions (list, read, start, send, mark read) and a limit of 60 requests a minute. It also has an MCP server and webhooks set under Settings, Webhooks.

Their words, our words

Aimfox	Gelee	Notes
Campaign	Campaign
Account	Seat
Lead / target	Lead
Labels	Tags and inbox flags
Notes	Notes	POST /prospects/{id}/notes

API calls

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

Aimfox	Gelee	Notes
`Add profile to campaign (POST /campaigns/{id}/targets)`	`POST /campaigns/{id}/leads`
`Get lead (GET /leads/{id})`	`GET /prospects/{id}, GET /people/{id}`	With the whole story.
`List conversations, get messages`	`GET /inbox, GET /inbox/{chat_id}/messages`
`Send message, start conversation`	`POST /inbox/{chat_id}/messages, POST /conversations`	Idempotency-Key makes retries safe.
`Mark read`	`POST /inbox/{chat_id}/read`
`Set labels, notes`	`PATCH /prospects/{id} { tags }, POST /prospects/{id}/notes`
`Account limits`	`PATCH /seats/{id}`

Webhooks

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

Aimfox	Gelee webhook	Notes
Reply events	`reply_received`
Connection accepted	`connection_accepted`
Invite / message sent	`invite_sent, message_sent`	Pick by name.

Message variables

Aimfox	Gelee
`First name`	`{{firstName}}`
`Company`	`{{company}}`
`A custom variable`	`{{custom.variable_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

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