Comms
Your own WhatsApp conversations — read them, and reply as yourself.
Official site: www.whatsapp.com
What it does
- List your conversations and read a thread
- Send a message, or reply in an existing thread
- Summarize a thread over a date range
This connects as a linked device, the same way WhatsApp Web does, except the session runs on a hosted browser rather than your laptop. Which means the phone stays the master of the account: unlink the device there and the session dies, the card goes back to unconnected, and any workflow leaning on it stops rather than half-works.
Not the WhatsApp Business API, and not a shared bot number — it is your account, acting as you.
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 WhatsApp 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 WhatsApp 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 WhatsApp returns something usable instead of something generic.
Processes that run on WhatsApp
None published yet.