Comms
Zoho Desk
Support tickets, threads, contacts and knowledge-base articles.
Official site: desk.zoho.com
What it does
- Read and write tickets and their reply threads
- Read contacts and knowledge-base articles
Access runs through fields held in the vault rather than a shared password, and can be revoked without touching code. Sending or reading on someone's behalf is easy to over-scope; the right default is exactly what the task needs, no more.
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 Zoho Desk 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 Zoho Desk 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 Zoho Desk returns something usable instead of something generic.
Processes that run on Zoho Desk
None published yet.