Prospecting
Unipile
The hosted-messaging subscription the six channel connections sit on.
Official site: www.unipile.com
What it does
- Hold the subscription once for the organization, in the vault
- Let each person link their own LinkedIn, WhatsApp, Telegram, Instagram, Messenger or X account
- Run each session on a real hosted browser rather than a pasted cookie
This is the account, not a channel. The organization puts the Unipile subscription in place once — its own key, or the platform's with hosted messaging granted by an admin — and each of the six networks is then its own connection that a person links separately. LinkedIn does not bring WhatsApp with it, and turning one on leaves the others off.
That granularity is the point. Sessions run on a real browser with a residential proxy, and each acts as the person who opened it rather than as a shared bot, so the scope of what a model can send is decided per network and per person. Reach here scales fast, which makes that the thing worth deciding upfront rather than after the first run.
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 Unipile 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 Unipile 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 Unipile returns something usable instead of something generic.
Processes that run on Unipile
None published yet.