Connect lemlist

Who this is for: anyone who sends cold email with lemlist and wants SpiderMail to work with that account.

What this does: walks you through creating a lemlist API key, looking up your tea_ Team ID, and adding both to your SpiderGate vault. SpiderMail uses an outreach key to read your sending accounts and their health, and to handle the provider's campaign events. It is not an LLM key; the gateway never sends chat requests with it.

Before you begin

A lemlist plan with API access. lemlist's pricing lists the API key on its Email, Multichannel and Enterprise plans.
To be a lemlist admin, or to have API access permission.
A terminal with curl, to look up your Team ID.
About 5 minutes.

Limits and terms to know first

lemlist warns: "Your account may not support API integrations due to its type."

Steps

Step 1 — Create the key

In lemlist, click your profile icon (bottom left), then Settings. Go to Integrations and click Generate. Enter a name and click Create Key. Copy it now: lemlist says "You can only view the API key once after generation."

Step 2 — Look up your Team ID

lemlist shows the Team ID only through its API. lemlist uses Basic authentication with an empty username and the key as the password:

curl -s -u ":YOUR_LEMLIST_KEY" https://api.lemlist.com/api/team

Copy the _id value from the answer. It starts with tea_.

Step 3 — Add it in SpiderGate

Open Gate → Vault (/dashboard/gate/vault) and click Add Provider. Pick Lemlist from Other tools, paste the key into API Key and the tea_ value into Team ID, and add a Label. Under Routing, turn Share with SpiderIQ key pool off, so the key stays with your brand. Click Add key.

Verify it worked

When you click Add key, SpiderGate sends one request to lemlist with the key before it stores anything: it reads your team at https://api.lemlist.com/api/team.

If lemlist accepts the key, the dialog closes and the key appears in your vault list.

If it does not, the dialog stays open and shows:

The lemlist key did not pass its check: <reason>. Nothing was saved.

The reason is SpiderGate's own wording, never lemlist's error text. The usual ones are Invalid API key (401 Unauthorized), Access denied (403 Forbidden) and The account behind this key has no credit left (402).

To see the key serve a request, give it a slot in one of your own routing aliases and send a request to that alias. The trace shows which provider answered.

Troubleshoot

You need to revoke the key. Delete it in lemlist's Integrations settings; lemlist says that "immediately revokes access for any integration using it". Then remove it from your vault.

Too many keys checked for this workspace; try again in …s. SpiderGate runs at most 20 key checks per brand in any 10 minutes. Wait the number of seconds it gives, then click Add key again.

Request timed out (15s) or Could not reach … to check the key. Try again later. The provider did not answer in time. Nothing was saved. Try again in a minute.

The provider is rate-limiting us (429). Try again in a minute. The provider throttled the check itself. Wait a minute and retry.