From reading your post to being in a campaign
The people worth contacting are usually already reading you. The gap is the address, and the fifteen minutes of going and finding one, which is the reason it does not happen.
With lemlist connected, accepting somebody starts the lookup and puts them into the campaign you choose. The sender is whatever the campaign already uses.
Connecting it
- 1In Inklined, open Settings and connect lemlist with a key from your own lemlist account. Lookups draw on your lemlist balance rather than anything Inklined resells.
- 2Choose the campaign a lead should join. The sender is set on the campaign in lemlist, so there is nothing extra to pick in Inklined.
- 3Where Apollo is also connected, Apollo is tried first for the lookup. Either one on its own is enough.
What Inklined takes
- →A work email address. lemlist runs the lookup as a job rather than answering immediately, so it takes a moment and Inklined waits rather than failing.
- →The lead created directly in the campaign, which is the part lemlist does differently from Apollo.
What happens to it
The first thing that happens to a transcript is that the names come out of it. People become role descriptors, so a participant is stored as “Host [GTM Consultant]” rather than by name. Companies become sector descriptors, so a client called Acme Corp is stored as “a B2B SaaS startup”. Email addresses, phone numbers, office addresses and profile links are removed. This runs once, on the way in, before anything else touches the text.
What is left is split into passages and indexed, so that when Inklined asks you something tomorrow it can show you the 40 seconds of the call the question came from rather than asserting that you said it.
Then a second rule applies, and it is the one that matters most if your calls are client work. Only speech attributed to you can become something you publish. On a typical consulting corpus most of the words belong to the other person, and offering those back to you as “something you said” is how somebody ends up publishing a client’s thinking under their own name. Anything that still names an organisation after all that asks you to confirm before it will draft from it.
One limitation worth stating rather than hiding: a client name that opens a sentence is not always caught, because “Sona ran this play” is shaped exactly like “Pricing pages need an owner”. The title check is the reliable one, and the confirmation step exists because no automatic check is enough on its own.
More on this: how Inklined works.
When it does not work
A connection that authenticates and then returns nothing looks exactly like a healthy one, which is why lemlist going quiet is hard to diagnose from the outside.
- Everything stops working at once
- Almost always the lemlist balance running out. It is worth knowing because the raw failure is unreadable, so Inklined reduces it to the one fact that matters: top up in lemlist and the queue clears.
- The lookup gave up
- lemlist answers asynchronously and Inklined stops waiting after about three minutes. Nothing is charged twice for a retry and the person is left where they were.
- No email address was found
- Reported as exactly that. No address is guessed and no campaign add is made without one.
- The account is reported as no longer connected
- The key has been revoked or rotated in lemlist. Reconnect in Settings.
Questions
Sync runs every 4 hours. Setup steps checked against the product on 24 September 2026. Using something else? See what Inklined connects to.
The calls are already happening.
Start with the strategy session. No card needed for that part.