Load Tableau data to DuckDB
Build a Tableau to DuckDB pipeline with your coding agent. One prompt scaffolds it with the dltHub AI harness, plus the Tableau API base URL, auth, endpoints, and incremental loading.
The Tableau REST API provides programmatic access to manage Tableau Server and Tableau Cloud resources such as data sources, workbooks, sites, and users. Everything needed to build a working Tableau → DuckDB pipeline is on this page: the API's base URL, authentication, endpoints, pagination and incremental field — plus a prompt that hands the whole job to your coding agent.
Build your Tableau to DuckDB pipeline
Paste this prompt into Claude, Codex, or Cursor. The agent does the rest.
PromptRunuvx dlthub-init@latestto build a pipeline from Tableau to DuckDB and run it on dltHub
That scaffolds a dltHub workspace and installs the dltHub AI harness — the project rules, the secrets-management skill, and the dlt MCP server your agent needs to work safely. From there it reads the Tableau API, proposes the endpoints to load, then writes, runs and validates the pipeline while you review rather than type. Credentials are inspected through MCP tools, so your agent never reads secrets.toml itself. How the LLM-native workflow works →
Prefer to write it yourself? Every fact the agent uses is below.
Tableau API at a glance
| Base URL | https://your-server/api/api-version |
| Example endpoint | GET sites/{siteId}/datasources |
| Records found at | datasources |
| Authentication | all requests except sign-in require an X-Tableau-Auth header containing the token — sent in the X-Tableau-Auth header |
| Pagination | Page-number page size via pageSize |
| Incremental field | pageNumber |
| Record id | id |
| API reference | https://help.tableau.com/current/api/rest_api/en-us/REST/rest_api_ref_authentication.htm |
These values come from the Tableau API reference — the authoritative source if anything here looks out of date.
How do I authenticate with the Tableau API?
Authentication requires sending a credentials token in the X-Tableau-Auth header for all requests following the initial sign-in. The token is obtained from the sign-in response body.
1. Get your credentials
- Log in to your Tableau Server or Tableau Cloud account. 2. Navigate to your 'My Account Settings' page. 3. Scroll down to the 'Personal Access Tokens' section. 4. Enter a name for your token and click 'Create new token'. 5. Copy the 'Token Secret' immediately, as it will not be displayed again. Store it securely.
2. Add them to .dlt/secrets.toml
[sources.tableau_source] tableau_server_url = "https://your-server-url" pat_name = "your-token-name" pat_secret = "your-token-secret" site_content_url = "your-site-id"
dlt reads this file automatically at runtime. With the harness, the setup-secrets skill prompts you for the values and never handles the raw credential in chat. For production, see setting up credentials with dlt.
What Tableau data can I load into DuckDB?
These are the Tableau endpoints dlt can load into DuckDB:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| datasources | sites/{siteId}/datasources | GET | datasources | Retrieves all data sources on a site. |
| workbooks | sites/{siteId}/workbooks | GET | workbooks | Retrieves all workbooks on a site. |
| projects | sites/{siteId}/projects | GET | projects | Retrieves all projects on a site. |
| users | sites/{siteId}/users | GET | users | Retrieves all users on a site. |
| groups | sites/{siteId}/groups | GET | groups | Retrieves all groups on a site. |
How do I load only new Tableau records?
Tableau exposes pageNumber on sites/{siteId}/datasources, so dlt can request only the records that changed since the last run. Set it as the cursor_path and dlt tracks the high-water mark for you between runs.
{"name": "datasources", "endpoint": { "path": "sites/{siteId}/datasources", "data_selector": "datasources", "incremental": {"cursor_path": "pageNumber", "initial_value": "2024-01-01T00:00:00Z"}, }}
On the first run dlt loads everything from initial_value; on every run after that it requests only what changed and appends with write_disposition="merge" if you set a primary key. See incremental loading.
What does the generated Tableau pipeline look like?
A standard dlt REST API pipeline — the same code you would write by hand, loading workbooks and datasources from the Tableau API into DuckDB:
import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def tableau_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://your-server/api/api-version", "auth": {"type": "api_key", "api_key": api_key, "name": "X-Tableau-Auth"}, }, "resources": [ {"name": "datasources", "endpoint": {"path": "sites/{siteId}/datasources", "data_selector": "datasources"}}, {"name": "workbooks", "endpoint": {"path": "sites/{siteId}/workbooks", "data_selector": "workbooks"}} ], } yield from rest_api_resources(config) def load_tableau_to_duckdb() -> None: pipeline = dlt.pipeline( pipeline_name="tableau_pipeline", destination="duckdb", dataset_name="tableau_data", ) load_info = pipeline.run(tableau_source()) print(load_info) if __name__ == "__main__": load_tableau_to_duckdb()
Run it with python tableau_pipeline.py. The agent iterates on this until it loads cleanly — you review and approve, rather than write it from scratch.
How do I query Tableau data in DuckDB?
dlt creates one table per resource. Query the loaded data with Python or SQL — or ask your agent to, through the MCP server's execute_sql_query tool.
Python (pandas DataFrame):
import dlt data = dlt.pipeline("tableau_pipeline").dataset() df = data.datasources.df() print(df.head())
SQL:
SELECT * FROM tableau_data.datasources LIMIT 10;
See querying your data with dataset and exploring it in marimo notebooks.
How do I deploy the Tableau to DuckDB pipeline in production?
The pipeline runs locally, which is ideal for prototyping and one-off analysis. When you need it on a schedule, monitored on every load, and shared with your team, deploy the same dlt code on the dltHub platform — no infrastructure to maintain. The prompt above already ends with "run it on dltHub", so your agent can take it there directly.
- Deploy & schedule — run the pipeline as a managed job with automatic retries.
- Monitor — observable job queues, alerting, and load metrics for every run.
- Transform — promote raw Tableau loads into governed, documented models.
- Visualize & share — explore data in notebooks and publish live dashboards instead of static screenshots.
What other destinations can I load Tableau data to?
dlt loads into any of these — only the destination argument changes:
| Destination | Example value |
|---|---|
| PostgreSQL | "postgres" |
| BigQuery | "bigquery" |
| Snowflake | "snowflake" |
| Redshift | "redshift" |
| Databricks | "databricks" |
| Filesystem (S3, GCS, Azure) | "filesystem" |
Set dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. On the dltHub platform the same pipeline runs against a managed Iceberg lakehouse. See the full destinations list.
Next steps
Was this page helpful?
Community Hub
Need more dlt context for Tableau to DuckDB?
Request dlt skills, commands, AGENT.md files, and AI-native context.