Connect Lemlist

Lemlist connects with an API key rather than OAuth, and that one key does two separate jobs: it unlocks Push to Campaign on records and tables, and it makes contact enrichment spend your own Lemlist credits instead of Spiich credits.

Get your Lemlist API key

The dialog in Spiich shows these steps too, under Find Key.

1. 1

   Open Lemlist settings

   Log in at Lemlist and open Settings in the left sidebar.

2. 2

   Go to API and Webhooks

   Click Integrations, then API & Webhooks.

3. 3

   Generate the key

   Generate an API key and copy it to your clipboard. It is a 32-character hex string.

Save the key in Spiich

1. 1

   Open Enrichment providers

   In Spiich, go to Settings > Integrations and scroll to Enrichment providers, described as Bring your own data provider key. Enrichments then spend that provider's credits instead of Spiich credits.

2. 2

   Add the key

   On the Lemlist card, click Add API Key, then Next.

3. 3

   Paste and connect

   Paste the key and click Connect. Spiich checks it against Lemlist before saving, so a wrong key is rejected here rather than at your next enrichment.

4. 4

   Point your team at the provider

   A saved key is not quite enough on its own. In Settings > Team Management, set the team's enrichment provider to Lemlist so enrichments actually route through it.

To change the key later, use the card's options menu: Replace API key or Disconnect.

Push to Campaign

Once the key is saved, three entry points appear.

One contact from a record. Open a record in Tables and click Push to Campaign in the header bar. The dialog shows the contact's name, title, company, email and phone, and a searchable campaign picker. Choose a campaign and click Add to Campaign. Spiich splits the name into first and last name and sends company name, job title and phone alongside the email.

One row from a table. Hover a row in a records table and click the small send icon, tooltip Push to Lemlist campaign. Same dialog, without leaving the table.

Many at once. Select rows in a records table and use the bulk bar: Push {n} to Lemlist, or push everything matching the current filter. Spiich resolves each row to a person with an email, adds them, and reports back how many were added, how many were already in the campaign and how many failed.

If someone is already enrolled in the chosen campaign, the button reads Already in Campaign and nothing is duplicated.

Limits

• Only admins hold the key. Members can push to campaigns but cannot add, replace or remove the API key.
• A bulk push is capped at 500 leads per run. When a filter matches more than that, the button reads Push up to 500 to Lemlist. Run it again for the rest; leads already added are recognised and not duplicated.
• A bulk push has a 50-second deadline. If Lemlist is slow or rate-limiting, the run returns a partial result and tells you which leads did not make it, rather than hanging.
• Every contact needs an email address. Rows without one are skipped and counted in the result.
• The assistant cannot push to campaigns. Push to Campaign is a manual action in the Spiich interface. Ask the assistant to find and enrich people, then push them yourself.
• Campaign lists are paged from Lemlist newest first, so a campaign created moments ago may not be in the cached list until you reopen the dialog.

Where the credits go

With your own Lemlist key saved, prospect search, company search and contact enrichment spend that Lemlist account's credits and no Spiich credits. Without a key, the same work runs on Spiich's key and is metered in Spiich credits. You can see your balance and usage in Settings > Billing. More in Credits and usage.

If something goes wrong

Push to Campaign does not appear on a record. No Lemlist API key is saved yet. Ask an admin to add one at Settings > Integrations > Enrichment providers.

*Saving the key gives Invalid Lemlist API key. The key was copied wrong or is not active. Regenerate it in Lemlist under Settings > Integrations > API & Webhooks* and paste it again.

*A bulk push reports Nothing to push though rows were selected.* None of the matching records had a person with an email address, which Lemlist requires. Enrich the contacts first, then push.

Some leads come back as failed. Lemlist rate-limited the run, or the 50-second deadline was reached. Push the remainder in a smaller batch.

*A record shows No email address - cannot add to campaign.* Add or enrich the contact's email, then reopen the dialog.