Connect Instantly
Who this is for: anyone who sends cold email with Instantly and wants SpiderMail to work with that account.
What this does: walks you through creating an Instantly API v2 key and adding it 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
An Instantly Outbound plan. Instantly says "API access is available on all Outbound plans."
About 3 minutes.
Limits and terms to know first
Use an API v2 key. Instantly says "API v1 was deprecated on January 19, 2026" and that v2 "is not compatible with API v1".
Steps
Step 1 — Create the key
In Instantly, open Settings → Integrations → API Keys and click Create API Key. Choose its scopes: SpiderGate's check reads your sending accounts, so the key needs at least read access to accounts; add the scopes for the SpiderMail features you plan to use. Copy the key now: Instantly says it "will be displayed only once".
Step 2 — Add it in SpiderGate
Open Gate → Vault (/dashboard/gate/vault) and click Add Provider. Pick Instantly from Other tools and paste the key into API Key. Leave Workspace ID empty; SpiderGate detects it. 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 Instantly with the key before it stores anything: it lists one of your sending accounts at https://api.instantly.ai/api/v2/accounts.
If Instantly 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 instantly key did not pass its check: <reason>. Nothing was saved.The reason is SpiderGate's own wording, never Instantly'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
The check fails with Access denied (403 Forbidden). The key's scopes do not include reading accounts. Create a key with the scopes from Step 1.
The check fails with Invalid API key (401 Unauthorized). You may have pasted an old v1 key. Create a v2 key.
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.