ProspectingConnector
Lusha
Resolve mobile phone and email for a batch of people, matched by LinkedIn profile, through Tulina's own MCP server, not Lusha's own hosted one.
Official site: www.lusha.com
What it can do
1 send
- 01Send
Resolve mobile phone and email for a batch of people in one call
Built for a batch, not a single lookup — resolve mobile phone and email for many people in one call, matched on LinkedIn profile rather than name, which is what keeps a batch from returning the wrong person when two people share a name.
How do you connect Lusha to Claude and ChatGPT?
Through Tulina's own MCP server, not Lusha's own hosted one or its native listing in Claude's connector directory. Resolve mobile phone and email for a batch of people in one call, matched on LinkedIn profile rather than name — 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 Lusha 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 Lusha 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 Lusha returns something usable instead of something generic.
