Ask what a Tableau dashboard currently shows, who owns a workbook, and which views get used.
Connect Tableau Cloud or Tableau Server with a personal access token and Memtro reads workbooks, views with how often each is viewed, published data sources, projects and users on a site, and the data behind a view as rows. User email addresses are never returned. The hourly sync writes changes into memory. When asked, and once an administrator has granted the action by name, it can tag items, refresh extracts now, which uses the site's refresh capacity, cancel jobs, rename, move, re-own or certify workbooks and data sources, create and change projects, and permanently delete a workbook or data source.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Tableau tool, reads what it needs, and answers with the source cited.
These tools change something in Tableau. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Tableau for you. Each event can start a job, with the event as its input. Tableau signs nothing, so the long random address is the only check: treat it as a password.
Events and webhooksOnce Tableau is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
What does the weekly sales dashboard show right now?
Who owns the Northwind pipeline workbook?
Which dashboards are used most, and which has nobody opened?
Which published data sources are certified?
Refresh the sales data source extract now
Before the board call the founder asks what the revenue dashboard shows for October. Memtro reads the rows behind the view and answers with the monthly total, the split by region and when the workbook was last updated by Priya Nair.
Ten minutes before the pipeline review, Dan Fletcher at Acme asks Memtro to refresh the CRM data source. Memtro starts a full extract refresh in Tableau as a background job, and every workbook using the source shows the new data once it finishes.
The teams that lean on Tableau most, a question each of them asks, and what they connect beside it.
A record in Tableau is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
CallRail
Fullstory
WhatConverts
Lightdash
Microsoft Clarity
Eppo
Holistics
MouseflowIn Tableau open your avatar → My Account Settings → Personal Access Tokens, create a token and copy its name and secret. The token acts as you, so Memtro reads and changes what you can, and users, jobs and projects need a site administrator
Type the host from your browser's address bar, including the pod, such as 10ay.online.tableau.com, or your Tableau Server's host name, with no https:// or path
In Connections → Tableau in Memtro fill in Tableau host, Personal access token name and Personal access token secret, add the Site URL name (the part after /site/), and connect. A token expires after 15 consecutive days unused
Ask which dashboards were viewed most this month
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Tableau tools are the same everywhere.
Only when you ask, and only what it has been granted: add tags to a Tableau workbook or view; remove a tag from a workbook or view; refresh a workbook's extracts now; refresh a published data source's extract now; cancel a queued or running job; rename, move, re-own or describe a workbook; rename, move, re-own or certify a data source; create a project; rename, describe or move a project; delete a workbook with its views (permanent); delete a published data source (permanent). Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded. An hourly sync anchors recently changed Tableau records into memory as entities.
Tableau host, Personal access token name and Personal access token secret. In Tableau open your avatar → My Account Settings → Personal Access Tokens, create a token and copy its name and secret. The token acts as you, so Memtro reads and changes what you can, and users, jobs and projects need a site administrator.
Yes. Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Tableau for you. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time
