Prospecting
Search people and companies, send connection requests and messages, all as yourself.
Official site: www.linkedin.com
What it does
- Search people and companies across LinkedIn's graph, on Tulina's own access — nothing to configure
- Send connection invitations and messages, and reply in the thread
- Read your LinkedIn feed and comment on a post
Where the data comes from
Two different things sit behind one name here. Search runs on Tulina's own platform access to AI Ark — shared capacity, nothing for a workspace to key in. Messaging runs through Unipile's hosted per-person session: each person connects their own account, and it acts as them, not as a shared bot.
That split is not an implementation detail to hide. Sending an invitation or replying in a thread happens under someone's real identity — worth knowing which of the two you are pointing a model at.
Why through Tulina
Most systems now publish their own way for a model to reach them, and that is a good thing — it is what Tulina connects to. The connection was never the hard part. Deciding who may use it, what it is allowed to return, and what the model knows before it asks: that is.
The keys stay in one place
Connect LinkedIn 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 is handed more access than they need. Revoke it once and everything running on it stops.
What leaves is filtered before it leaves
Roles decide who can reach LinkedIn at all. Beyond that, a policy on the connector itself decides what comes back: fields dropped, identifiers masked or hashed, people pseudonymised. The data is minimised at the source rather than after it has already reached a model.
Every call is on the record
Runs are logged for the organisation — what was called, by whom, when. That is what makes an automated action reviewable after the fact, and what a security review asks for first.
The run starts knowing your company
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 LinkedIn returns something usable instead of something generic.
Processes that run on LinkedIn
CRM hygiene and prospect job changes
Duplicates merged and broken fields repaired on a weekly schedule, with prospects who changed employer followed to their new company and a recap posted to the team.
Prepare for a demo from the last call
The last calls, the deal's state, and fresh research become one prep brief, plus a deck built around that company's own use cases, posted before the meeting.
Revive deals that went cold
Deals lost more than 90 days ago come back with fresh signals, contacts checked for job moves, and the features they asked for that have since shipped.
Source and qualify leads
A target company gets searched across LinkedIn, ranked against your ICP, and the qualified shortlist lands in your CRM with email and mobile filled in.
Turn website visitors into outreach
Every company that reads your site gets one decision, and the few worth answering arrive as a named person with a note already written from the page they read.