Claude Omni Analytics connectorWhat Claude can do in your Omni Analytics account.
The Claude Omni Analytics connector exposes 3 tools. All 3 read your data, 0 write, 0 stay undocumented. Below: how Claude turns a plain question into an Omni query, which settings an admin has to switch on, and what stays out of reach.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when a numbers question is waiting on you
You ask Claude in plain language, without writing SQL or digging through dashboards. The Omni Analytics connector has Claude follow the semantic model your data team built in Omni, with the same logic and the same permissions, and the numbers come back in the conversation.
Aim at the right dataset. pickModel lists the Omni models you can access, with their IDs, so Claude knows which one to query. If a model ID is set in the configuration, that step can be skipped.
Land in the right scope. pickTopic shows the topics inside that model and picks the one that best fits your question. If the AI is allowed to query any view in the model, that topic step becomes optional.
Get the answer. getData runs the query on that model and topic and returns the rows. Claude can chain several queries and, as Omni points out, bring in context such as a web search result before querying.
What Claude won't do: edit the model, build a dashboard or write to your data, since no source describes a tool for that. It only sees what your Omni permissions show you. And nothing fires on its own: no report unless you ask. Scheduled delivery is a job for an automation platform, covered in the Integrations hub.
The vocabulary, in one minute
Five words you will see while connecting Omni to Claude.
- Connector
- The link you set up once between Claude and an account you already own, so Claude can work on it while answering.
- Tool
- One named capability a connector gives Claude. Claude decides which ones to call; the directory lists each by name.
- Authorization
- Omni's own sign-in screen, where you give Claude the access it will use. Granted once per person, and revocable.
- Approval
- The confirmation Claude waits for in the chat before any action that would change your account on your behalf.
- MCP
- The shared standard behind connectors: it is what lets an assistant talk to an outside service such as Omni.
Connect the Claude Omni Analytics connector in three steps
- 01
Find Omni Analytics
In Claude's settings, open Customize, then Connectors, and look for Omni Analytics. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable it for the organization first.
- 02
Sign in to Omni
Click Connect on its row, then sign in through the window Omni opens itself. If the connection ever breaks, Disconnect and a fresh connection sort it out.
- 03
Confirm the access
Read Omni's authorization screen before you accept: Omni, not Claude, sets what the access covers. You can withdraw it later, either from Claude or from Omni's side.
The 3 tools in the Claude Omni Analytics connector
Omni Analytics gives Claude 3 tools: 3 that read your account, 0 that change something in it.
Three reading tools that run in sequence: model, topic, data. Names stay exactly as Claude shows them.
- 3 read
What Claude reads (3)
3 toolsThree lookup steps, with nothing changed on the Omni side.
pickModel
Lists the Omni models available to you with their IDs, so Claude knows which one to query. Omni notes that a model ID set in the configuration lets you skip this step entirely.
pickTopic
Shows the topics in the chosen model and picks the one closest to your question. Omni says this step becomes optional when the AI is allowed to query any view in the model.
getData
Executes the query against the selected model and topic, or a view when that's allowed, and brings the results back into the chat.
What Claude asks before it acts
By default, Claude stops and asks for your go-ahead before every action it takes on an account for you.
No source describes a confirmation specific to the three Omni tools, so the general rule applies. Omni adds the part that matters most: every query runs with the permissions of the authenticated user, and interactions stay scoped to the model, plus the topic when one is supplied. On Claude's side, Team and Enterprise owners decide whether a member may let some actions through, and they can limit the connector for the whole organization.
Which plans include it
None of the 819 sheets in the official directory shows availability by plan: for Omni Analytics, that answer isn't published anywhere.
The general rule is public: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables the connector for the organization before each member connects. For the current state, the Omni Analytics sheet in the official directory is the reference.
Where the Omni Analytics connector stops
A connector isn't an automation: Claude queries Omni while it is answering you, and no report goes out by itself.
By default the sheet only exposes reading, an observed floor and not a guarantee: an admin can open actions that appear on no public sheet. The partner badge isn't a security audit, and Anthropic doesn't vouch for how a publisher's tools behave. Only Omni documents this connector; no Claude help page covers it. The limits below come from Omni's own pages. Other connectors the team has gone through sit in the Claude connectors hub.
Need help connecting Omni Analytics to Claude?
A person reads every message.