Data & Storage · Integration
Tableau
Add Tableau to your product for your customers, and give your AI agents governed access to it.
Tableau puts the analysis a customer's own analysts built inside your product, which is a different job from querying a warehouse yourself. The hierarchy is the thing to get right: an instance holds sites, sites hold projects, and projects hold workbooks, the views inside them and the published data sources they draw on. Three details govern the build. The site is the isolation boundary, so a token authenticated against one site cannot reach another, which happens to map neatly onto a tenant. Extracts refresh on a schedule or on request and the refresh is asynchronous, so a view can be showing yesterday's numbers while looking perfectly current. And embedding a view needs a signed token naming the person looking at it, or the workbook filters its rows for the wrong user. fastn holds each site's credentials and follows the API version.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Tableau site so your product lists the workbooks and views their analysts publish.
Embed a view with a signed token naming the viewer, so the workbook's row level security filters to what that person may see.
Trigger an extract refresh after your product loads new data, then read the task history to confirm it completed.
Read project and data source metadata at connect time, so your screens reflect that site rather than a fixed list.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reports which extracts failed their last refresh and which views depend on them.
An agent answers a question from a published view's data for one site, with the view it read recorded.
An agent checks when a data source was last refreshed before it quotes a figure from it.
Example prompt
Which workbooks on this Tableau site are showing data from a failed extract refresh?
Set up Tableau in 4 steps
- 01Enable the Tableau connector in your fastn dashboard.
- 02Have each customer authorise their own site, whether that is Tableau Cloud or a server they run, since the site scopes what a token reaches.
- 03Map the projects, workbooks, views and data sources your product uses, and decide which identity your embed tokens carry.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Tableau integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Tableau integration without building it. Your customers connect their own Tableau account inside your product and work their records, datasets and fields there, with no per-customer code on your side.
- Handle the part that actually costs time: schemas differ per customer and change without notice, and volumes can be large. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Tableau update is not your on-call problem.
- One integration serves your product and your agents. The same governed Tableau connection powers in-product features and gives AI agents scoped, audited access, so you read and write your customers' data where it already lives without wiring it twice.
Used by these teams
Compare with
Power BI
Looker
SnowflakeOften used alongside
Tools the same teams tend to run next to Tableau, across other categories.
Anthropic Claude
OpenAI
Hugging FaceTableau integration FAQ
How do I add a Tableau integration to my product?
Enable the Tableau connector in your fastn dashboard, then let each customer authenticate their own Tableau account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Tableau client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Tableau account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Tableau account and only ever sees their own records, datasets and fields. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Tableau integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reports which extracts failed their last refresh and which views depend on them.
Who maintains the Tableau integration?
fastn does. When Tableau changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Does the Tableau integration adapt when a customer's schema changes?
Schema and field mapping is configuration per customer, so a change on their side is a mapping update rather than a code change and a release on yours.
How are large Tableau reads handled?
Pagination and throttling are handled for you, and initial backfills are rate-limited so a large import does not exhaust a customer's API allowance.
What can I build with the Tableau integration?
A common starting point: let each customer connect their own Tableau site so your product lists the workbooks and views their analysts publish. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Tableau integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Tableau does not change your per-connector cost. You can start free with 3 connected accounts.
Add Tableau to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.