Claude Tableau connectorWhat Claude can do in your Tableau account.
The Claude Tableau connector exposes 35 tools. 23 read data sources, workbooks, views and Pulse metrics, 3 change something, and 9 are listed without a description, including three deletes. Below: what Claude can answer, what it can touch, and where the docs disagree.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when Tableau answers in plain words
Tableau's own tagline for this connector is helping agents see and understand data. In practice, you ask Claude a business question and it finds the right published data source, queries it and answers, or pulls the numbers and image of a view you already use. The connector is a desktop extension, so it lives in Claude Desktop rather than in the browser.
Answer a business question from published data. A sales director asks which region grew fastest this quarter. Claude finds the data source with list-datasources, checks its fields with get-datasource-metadata and runs query-datasource, which sends a VizQL query to Tableau.
Reuse the dashboards people trust. get-view-data returns the data behind a view and get-view-image an image of it, so Claude can comment on the chart your team already reviews every Monday.
Follow the metrics that matter. For Pulse users, generate-pulse-insight-brief produces conversational insights on your metrics from a plain question.
What it will not do: delete with a documented tool. Three delete tools sit on the sheet, but Tableau's docs describe a single deletion tool under another name. Nothing runs by itself either: no tool reacts when a refresh fails. For that, a scenario tool fits better, and the Tableau Make integration page covers it. They do different jobs.
The vocabulary in one minute
Five words you will meet while plugging Tableau into Claude.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
- Tool
- One named action the connector opens to Claude. Claude picks the ones it needs by itself; the directory lists them by name.
- Authorization
- The sign-in screen of Tableau itself, where you hand Claude the access it will use. Given once per person, and you can take it back.
- Approval
- The confirmation Claude waits for before it finishes something that changes your account, shown right in the conversation.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as Tableau.
Connect Tableau to Claude in three steps
- 01
Find Tableau in Claude
In Claude's settings, open Customize, then Connectors, and look for Tableau in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to switch the connector on before each member can sign in.
- 02
Start the connection
Click Connect on its row and sign in to Tableau in the window the service opens itself. If the link breaks one day, use Disconnect, then plug it back in from the same row.
- 03
Read the authorization screen
Read the service's screen before you accept. It belongs to Tableau, not Claude, and it decides what the access covers. You can also withdraw that access later from your Tableau account.
The 35 tools, grouped by what they do
Tableau gives Claude 35 tools: 23 that read your account, 3 that change something in it, and 9 no official source describes.
Three groups: what Claude reads, what it changes, and nine names Tableau's docs do not cover. Names stay in English, as Claude shows them.
- 23 read
- 3 write
- 9 not documented
What Claude reads (23)
23 toolsTwenty-three tools that search, query and read your Tableau content without changing it.
list-datasources
Retrieves the published data sources Claude can work with, before it queries one of them.
list-extract-refresh-tasks
Lists the extract refresh tasks of the Tableau site, the jobs that keep extracts up to date.
list-jobs
Returns the list of background jobs running on the Tableau site.
list-users
Retrieves the list of users on the Tableau site.
list-workbooks
Retrieves the workbooks on the site, the files that hold your dashboards and sheets.
list-projects
Returns the projects of a Tableau site with their name, description, parent project, content permissions, owner and dates.
list-views
Returns the views of the site, one page of up to 1000 per call.
list-custom-views
Retrieves the custom views of a given workbook, the saved versions people made with their own filters.
query-datasource
Runs VizQL queries against a published data source to answer a business question directly from the data.
get-datasource-metadata
Fetches the metadata of a data source, so Claude knows which fields it can use.
get-workbook
Retrieves information about a workbook, including the views it contains.
get-view-data
Retrieves the data behind a view in a workbook, the figures the chart is drawn from.
get-view-image
Retrieves an image of a view, so Claude can look at the chart as people see it.
get-custom-view-data
Exports a custom view's figures as comma-separated values, with the filters its owner saved.
get-custom-view-image
Captures a custom view as an image: a saved or personalised state of a published sheet, user filters included.
list-all-pulse-metric-definitions
Retrieves every published Pulse metric definition, the templates Pulse metrics are built on.
list-pulse-metric-definitions-from-definition-ids
Retrieves specific Pulse metric definitions from a list of definition IDs, when Claude already knows which ones you mean.
list-pulse-metrics-from-metric-definition-id
Collects the published Pulse metrics built from one metric definition ID.
list-pulse-metrics-from-metric-ids
Retrieves published Pulse metrics from a list of metric IDs.
list-pulse-metric-subscriptions
Retrieves the Pulse metric subscriptions of the current user, the metrics you chose to follow.
generate-pulse-metric-value-insight-bundle
Generates an insight bundle for the current aggregated value of a Pulse metric, the explanation around today's number.
generate-pulse-insight-brief
Generates AI-powered conversational insights on Pulse metrics from a natural-language question.
search-content
Searches every supported content type on the Tableau site for objects that match your question.
What Claude changes (3)
3 toolsThree tools that change a refresh schedule or your sign-in state. No source describes a confirmation specific to them: the general rule below applies.
update-cloud-extract-refresh-task
Approval: see the ruleChanges the schedule of an extract refresh task on Tableau Cloud. The task stays; only when it runs changes.
revoke-access-token
Approval: see the ruleRevokes the access token of the current session, which signs you out of the connection.
reset-consent
Approval: see the ruleResets the saved sign-in consent for you on Tableau's authorisation server, so the next sign-in asks for consent again.
Not documented (9)
9 toolsThe directory publishes these nine names. Tableau's tool pages describe other names instead, and this page will not guess from a label.
delete-datasource
The directory lists this name and nothing else. Tableau's tool pages do not describe it, no Claude page does either, and this page will not fill the gap with a guess. No official source documents its behaviour today. Tableau documents deletion under a different tool name.
delete-extract-refresh-task
Here, only the name is public. No sentence from Tableau or from Anthropic says what the tool does, reads or changes, so this note stops at that. No text from the publisher describes it in any detail.
delete-workbook
Nothing official explains this one. The directory sheet shows the label, Tableau's tool pages skip it, and a name alone is not a description. The gap sits in the documentation, not in this page.
get-oauth-token
This tool appears on the sheet without a word of explanation. Whether it reads or changes anything in Tableau, no source says. No help centre article covers it either.
get-view
No source covers it. Tableau's tool pages name other capabilities, but none is tied to this label, and Anthropic publishes nothing tool by tool. No description exists anywhere public for now.
query-admin-insights-ts-events
Listed, not documented. The only thing anyone can check is that the name exists on the directory sheet for Tableau. The directory sheet adds no wording beyond the name.
query-admin-insights-site-content
Silence again from the sources: Tableau's tool pages and Claude's pages both leave this name unexplained, so this page does too. No official source documents its behaviour today.
query-admin-insights-job-performance
Of this one, the public record holds a label and no behaviour. Guessing from the wording would be exactly the mistake this page avoids. No text from the publisher describes it in any detail.
get-stale-content-report
A name on the sheet, and that is all. Whether it touches your Tableau data or only looks at it is not documented anywhere. The gap sits in the documentation, not in this page.
What Claude asks before acting
By default, Claude stops and asks for your go-ahead before each action it carries out on an account for you. The request shows up in the conversation, at the moment it matters.
On Team and Enterprise, workspace owners decide whether a member can let some actions through without being asked every time. They can also cap what a connector may do for the whole organisation, keeping reading open and closing writing, for example. That setting applies to everyone and nobody gets around it from their own account. And Claude works with your rights, nothing more: what you cannot reach in Tableau stays out of its reach too.
Which plans it works on
None of the 819 sheets in the official directory shows availability by plan. The answer, connector by connector, is not published anywhere: it is a real gap in the catalogue.
The general rule is published: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, and desktop extensions install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner turns the connector on for the organisation before members can connect. For the current state, check the connector's sheet in the official directory.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing starts when a refresh fails, a metric moves or a view is published.
The tool list is an observed floor, not a promise: an administrator can open actions that no public sheet shows. The partner badge in the directory is not a security audit either, and Anthropic says so on every sheet: it does not choose the tools a publisher exposes and does not guarantee they behave as described. Everything below comes from Tableau's documentation, since neither Claude's help centre nor Anthropic's docs have a page on this connector. For a connector built on shared sheets, compare with the Claude airtable connector.
Need help connecting Tableau to Claude?
A person reads every message.
