Skip to content
Data warehouse ⇄ Analytics

MotherDuck to Tableau integration — real-time data sync

Keep MotherDuck and Tableau in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect MotherDuck and Tableau

Flow Tableau data into MotherDuck in real time — no exports, no schedulers, no custom scripts.

Tableau is a read-only source: Stacksync reads its data in real time and delivers it into MotherDuck, so MotherDuck always reflects the current state of Tableau — without exports, scripts, or schedulers.

Tableau is where teams explore, visualize, and report; MotherDuck is the store of record that holds the raw tables and full history behind those views. The two overlap wherever the same events, users, and metrics matter to both, and when the bridge between them is a nightly export or a hand-built extract, dashboards lag the warehouse and analysts spend the morning arguing over whose number is right.

Common use cases

  • 01 Read site Users and their site roles for periodic access reviews and to reconcile Tableau accounts against an HR or IdP source of record.
  • 02 Read Databases, Tables, and Fields from the Metadata API to populate a data catalog with Tableau lineage and column definitions.
  • 03 Land CRM and operational database records in MotherDuck so a small team gets warehouse-style analytics without cluster management
  • 04 Sync modeled MotherDuck tables outward to operational tools for activation

Common sync patterns

Corrections propagate instead of reloading

When a record is fixed or backfilled on one side, the change reaches the other without a full reload, keeping history consistent across both.

One number both sides agree on

Metrics and aggregates stay aligned between the two systems, so a figure shown in Tableau matches the MotherDuck table it was built from instead of drifting between refreshes.

Where MotherDuck holds the source tables: live data in the reporting layer

Records maintained in MotherDuck flow into Tableau as they change, so dashboards and reports read current rows rather than an overnight extract.

What you can sync between MotherDuck and Tableau

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

MotherDuck objects Tableau objects How this pairing syncs
Views Modeled projections used as outbound sync sources. Views Worksheets and dashboards inside workbooks; their data and crosstab export as CSV via the REST query-view-data endpoint. Same entity on both sides — records pair one-to-one and field-level changes reconcile in the writable direction.
Tables The main landing target for synced records and source for analysis. Published Data Sources Published data sources (.tdsx); their underlying rows are read via the VizQL Data Service, and refresh state is tracked through content webhooks. Tables is specific to MotherDuck and Published Data Sources to Tableau — each maps to any object or custom field on the other side.
Database Shares Read-only copies of a database shared with other users or teams. Workbooks Workbook content and metadata read via the REST and Metadata APIs; create, update, and delete events fire webhooks for change detection. Database Shares is specific to MotherDuck and Workbooks to Tableau — each maps to any object or custom field on the other side.
Attached Local DuckDB Databases Local files attached alongside cloud databases for hybrid queries. Projects Folders that organize content and set permissions; listed via REST to mirror the site's content hierarchy into a catalog. Attached Local DuckDB Databases is specific to MotherDuck and Projects to Tableau — each maps to any object or custom field on the other side.
Databases Cloud-hosted DuckDB databases that scope a sync's reads and writes. Users Site users with site roles and group membership; read via REST for access reviews and to reconcile identities against an HR or IdP source. Databases is specific to MotherDuck and Users to Tableau — each maps to any object or custom field on the other side.
Schemas Namespaces within a database used to organize synced tables. Databases and Tables External assets indexed by Tableau Catalog; queried via the Metadata API GraphQL endpoint for lineage and impact analysis. Schemas is specific to MotherDuck and Databases and Tables to Tableau — each maps to any object or custom field on the other side.

How changes propagate between MotherDuck and Tableau

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

MotherDuck Tableau Interval-based propagation

DetectionStacksync polls MotherDuck for changes on an incremental schedule, reading only records changed since the previous pass. Polling.

DeliveryTableau does not accept inbound record writes, so this direction carries requests rather than records: Tableau's output flows back as field updates on the originating MotherDuck records.

Tableau MotherDuck Sub-second propagation

DetectionTableau notifies Stacksync of record changes through webhook events. Webhooks fire on workbook and data source create/update/delete and extract refresh events.

DeliveryEach detected change is applied to MotherDuck as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • MotherDuck: Subject to the platform's compute and concurrency limits rather than per-request API rate limits.
  • Tableau: Tableau Cloud enforces per-site REST rate limits and returns HTTP 429; a PAT allows only one concurrent session and expires after 15 consecutive days of non-use.
What ships with MotherDuck ⇄ Tableau

Connect MotherDuck and Tableau for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every MotherDuck–Tableau connection.

Real-time

Real-time sync

Changes in MotherDuck or Tableau instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever MotherDuck or Tableau data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single MotherDuck or Tableau record.

Observability

Monitoring

Track your MotherDuck ⇄ Tableau sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between MotherDuck and Tableau.

How the MotherDuck and Tableau connectors work

MotherDuck

Integration surface
SQL through DuckDB clients and drivers using a MotherDuck (md:) connection
Authentication
Access token created in MotherDuck (Settings > General > Create Token), pasted into Stacksync; database name and schema configurable if not using defaults
Change detection
Polling; no log-based CDC or webhook surface is exposed
Capabilities
read · write
Rate limits
Subject to the platform's compute and concurrency limits rather than per-request API rate limits
MotherDuck setup guide

Tableau

Integration surface
REST API, Metadata API (GraphQL), and VizQL Data Service
Authentication
Sign-in via Personal Access Token (PAT) or username/password returns a credentials token sent as the X-Tableau-Auth header; Connected Apps issue JWTs for OAuth-style access. One active session per PAT.
Change detection
Webhooks fire on workbook and data source create/update/delete and extract refresh events; otherwise content and metadata are polled via REST list endpoints (updatedAt) and the Metadata API.
Capabilities
read · webhooks
Rate limits
Tableau Cloud enforces per-site REST rate limits and returns HTTP 429; a PAT allows only one concurrent session and expires after 15 consecutive days of non-use.
How it works

How to connect MotherDuck to Tableau — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate MotherDuck and Tableau with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    MotherDuck connected
    Tableau connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the MotherDuck and Tableau objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · MotherDuck ⇄ Tableau
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    MotherDuck Tableau
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

MotherDuck and Tableau integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 381 integrations available for MotherDuck and Tableau.

Popular · 7 of 381
All MotherDuck integrations All Tableau integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own