Integrations

Connect Lemlist to send chosen leads into a campaign, and how the API key is kept safe.

Integrations move your leads out of Harken and into the tools your team already runs outreach from. This release ships one: Lemlist. The CRM cards on the same tab (Pipedrive, HubSpot, Attio, Folk, Twenty and Airtable) stay marked for a later phase.

Connecting Lemlist

1. In Lemlist, copy an API key. It sits in your Lemlist settings, in the integrations area.
2. In Harken, open Settings, then Integrations, and open Lemlist with its Details button.
3. Paste the key and press Connect.

Harken checks the key straight away by asking Lemlist for your campaigns. A key Lemlist refuses is turned down with a message and nothing is saved. Once a key is accepted, the card carries a green check mark and the number of campaigns it can reach.

To stop sending, press Disconnect in the same dialog. The stored key is removed at once.

How the key is stored

The key is encrypted by the application before it reaches the database, with a symmetric Fernet key that only the server holds (the INTEGRATIONS_SECRET setting). The database row never contains the key in readable form, and it is never written to logs, sent back to the browser or shown again after you connect. If Lemlist later stops accepting it, the push dialog tells you to connect again.

A server without that setting cannot store keys, so the card says Lemlist cannot be connected there yet.

Sending leads

On the Leads page, tick one or more rows and press Push to Lemlist in the bar that appears. The button shows up only while Lemlist is connected. Pick a campaign and press Send. Each lead goes over with its given name, family name, company and, for people found on LinkedIn, their profile link.

Lemlist needs an email address for every lead, so use Find email in the lead's panel first. Leads without one are left out and counted in the message. If Lemlist asks us to slow down, the push pauses and tells you how many were sent, so you can send the rest a few minutes later.

Pushing costs no credits. Credits are only drawn when a lead is created or an email is found.

FAQ

Can two workspaces share one Lemlist account?

Yes. Each workspace stores its own copy of the key, and each can connect or disconnect without affecting the other.

Will a lead be added twice if I push it again?

No. Lemlist turns down a lead that is already in that campaign, and Harken reports it as not sent.