CommsConnector
Zoho Desk
Read and write Zoho Desk tickets, reply threads, contacts and knowledge-base articles, from the same Claude or ChatGPT chat as the rest of your stack.
Official site: desk.zoho.com
What it can do
1 read/1 send
- 01Send
Read and write tickets and their reply threads
- 02Read
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.
Is there already a Zoho Desk connector for Claude?
Yes — Zoho's own MCP platform covers Desk alongside CRM, Mail and the rest of Zoho One. This card reaches the same surface — tickets and their reply threads, contacts, knowledge-base articles — through Tulina's own MCP session instead, so a support workflow that also touches your CRM or your inbox doesn't need a second connector switched on for it. Sending or reading on someone's behalf is easy to over-scope; access here sits behind vault-held credentials scoped to exactly what the task needs.
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 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 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 Zoho Desk 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 Zoho Desk returns something usable instead of something generic.
Processes that run on Zoho Desk
None published yet.