ToolsConnector
Zoho Analytics
Read Zoho Analytics workspaces and views, and run SQL queries against them, from the same Claude or ChatGPT chat as the rest of your Tulina-connected MCP stack.
Official site: analytics.zoho.com
What it can do
2 read
- 01Read
Read workspaces and views
- 02Read
Run SQL queries and export results
Access runs through fields held in the vault rather than a shared password, and can be revoked without touching code. A knowledge base often holds more than the task at hand needs; access should track the task, not the whole store.
Is there already a Zoho Analytics connector for Claude?
Yes — Zoho ships an official Zoho Analytics MCP Server, with its own Claude Desktop connector for a local install. This card reaches the same ground — workspaces, views, SQL queries and their exported results — through Tulina's own MCP session instead, so a workflow that also reads your CRM or your support desk doesn't need a second connector switched on for it. A knowledge base often holds more than a given task needs; access here tracks the task rather than the whole store.
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 Analytics 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 Analytics 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 Analytics returns something usable instead of something generic.
Processes that run on Zoho Analytics
None published yet.