ProspectingConnector
Lemlist
Add people to a lemlist campaign and read its sequences and results back from Claude or ChatGPT, through Tulina's own MCP server, not lemlist's own hosted one.
Official site: app.lemlist.com
What it can do
1 send
- 01Send
Read and manage cold email campaigns and their results
Manages a campaign end to end — people added, sequences read back, results reported — but never launches on its own initiative if a workflow doesn't call for it explicitly. Adding the same contact to the same campaign twice is a caller mistake to guard against; the connector doesn't prevent it by itself.
How do you connect Lemlist to Claude and ChatGPT?
Through Tulina's own MCP server, not Lemlist's own hosted one. Add people to a campaign, read its sequences and results back, and manage it end to end — from the same chat as Claude or ChatGPT.
Why through Tulina
The connection was never the hard part.
Most systems now publish their own way for a model to reach them, and that is good: it is what Tulina connects to. The hard part is deciding who may use it, what it is allowed to return, and what the model knows before it asks.
The keys stay in one place
YouTeamOrganisation
Connect Lemlist once. The credential is encrypted in a vault, never held in clear, and never pasted into a chat or a workflow file. A person uses their own key where they have one, their team's where they do not, the organisation's after that, so nobody is blocked and nobody holds more access than they need. Revoke it once and everything running on it stops.
What leaves is filtered before it leaves
fields droppedmasked or hashedpseudonymised
Roles decide who can reach Lemlist at all. Beyond that, a policy on the connector itself decides what comes back. The data is minimised at the source rather than after it has already reached a model.
Every call is on the record
whatwhowhen
Runs are logged for the organisation. That is what makes an automated action reviewable after the fact, and it is what a security review asks for first.
The run starts knowing your company
namingkey accountsdecisions
A direct connection gives a model access. It does not tell it how your company names things, which accounts matter, or what was decided last quarter. Tulina carries that across every tool, so the same request against Lemlist returns something usable instead of something generic.
Processes that run on Lemlist
Build a target list from a sentence
AI lead generation from one sentence: companies sourced and scored on dated signals, contacts verified, checked against your CRM and staged as a campaign.
6 steps →Find buyers engaging with competitors
Everyone who engages with a competitor's posts gets found, scored against your ICP, enriched, and staged for outreach with a human approving the list.
5 steps →Find contacts for signal accounts
Companies that already showed interest but have nobody linked get the right people found by role, deduped, and added to outreach automatically.
6 steps →Outbound from buying signals
Each morning, companies with a new stack or hiring signal are scored on your rubric, checked against the CRM and live sequences, and given one opener per buyer.
7 steps →Run LinkedIn outreach at a safe pace
Small sending slots through the day, a daily budget that climbs one step only while the account stays healthy, and every send stopped at the first warning.
7 steps →Turn website visitors into outreach
Website visitor tracking that ends in outreach: each company is checked against your CRM, and the few with real intent get a named contact and a drafted note.
7 steps →
