Skip to content
Data warehouse ⇄ Analytics

ClickHouse to Tableau integration — real-time data sync

Keep ClickHouse 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 ClickHouse and Tableau

Flow Tableau data into ClickHouse 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 ClickHouse, so ClickHouse always reflects the current state of Tableau — without exports, scripts, or schedulers.

Tableau is where teams explore, visualize, and report; ClickHouse 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 Mirror the Projects and Workbooks content hierarchy into an internal catalog so teams discover dashboards from a central index.
  • 02 Track Extract Refresh Tasks and DatasourceRefreshFailed webhook events to raise alerts in a database or ticketing system when refreshes fail.
  • 03 Sync aggregated ClickHouse query results back into operational tools, such as account-level usage metrics into a CRM.
  • 04 Consolidate logs and business records from multiple sources into MergeTree tables for retention and reporting.

Common sync patterns

Where Tableau produces segments or scores: results back to the warehouse

Cohorts, segments, and computed metrics defined in Tableau write to ClickHouse as tables the rest of the stack can query and join.

Shared user and account keys

Users and accounts tracked in Tableau line up with the customer or user rows in ClickHouse on a stable key, so both sides count the same population.

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.

What you can sync between ClickHouse 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.

ClickHouse objects Tableau objects How this pairing syncs
Views Saved queries used as curated, read-only 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.
Distributed tables Query-routing tables over cluster shards in self-managed deployments. Projects Folders that organize content and set permissions; listed via REST to mirror the site's content hierarchy into a catalog. Distributed tables is specific to ClickHouse and Projects to Tableau — each maps to any object or custom field on the other side.
Dictionaries In-memory lookup structures refreshed from external sources, sometimes fed by syncs. 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. Dictionaries is specific to ClickHouse and Users to Tableau — each maps to any object or custom field on the other side.
Tables (MergeTree family) Columnar, append-optimized tables that serve as the destination for high-volume sync loads. Databases and Tables External assets indexed by Tableau Catalog; queried via the Metadata API GraphQL endpoint for lineage and impact analysis. Tables (MergeTree family) is specific to ClickHouse and Databases and Tables to Tableau — each maps to any object or custom field on the other side.
Databases Namespaces that group tables and scope permissions for sync users. Extract Refresh Tasks Scheduled extract refreshes; status and history read via REST, with DatasourceRefreshSucceeded and Failed events delivered by webhooks. Databases is specific to ClickHouse and Extract Refresh Tasks to Tableau — each maps to any object or custom field on the other side.
Materialized views Insert-time transformations that reshape incoming synced rows into aggregates. Fields and Columns Columns and calculated fields with their descriptions, exposed by the Metadata API; read to populate a data catalog with governed definitions. Materialized views is specific to ClickHouse and Fields and Columns to Tableau — each maps to any object or custom field on the other side.

How changes propagate between ClickHouse 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.

ClickHouse Tableau Interval-based propagation

DetectionStacksync polls ClickHouse for changes on an incremental schedule, reading only records changed since the previous pass. No log-based CDC for consumers.

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 ClickHouse records.

Tableau ClickHouse 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 ClickHouse as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • 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 ClickHouse ⇄ Tableau

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

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

Real-time

Real-time sync

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

No-code + pro-code

Workflow automation

Trigger automated workflows whenever ClickHouse 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 ClickHouse or Tableau record.

Observability

Monitoring

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

Trading partners

EDI

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

How the ClickHouse and Tableau connectors work

ClickHouse

Integration surface
Native TCP protocol and HTTP interface; standard SQL dialect, with MySQL and PostgreSQL wire compatibility available
Authentication
Database credentials (username/password); ClickHouse Cloud issues per-service credentials over TLS
Change detection
No log-based CDC for consumers; incremental reads use polling on monotonic columns, and ClickHouse is usually the destination rather than the source
Capabilities
read · write

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 ClickHouse 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 ClickHouse 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
    ClickHouse connected
    Tableau connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the ClickHouse 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 · ClickHouse ⇄ 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
    ClickHouse Tableau
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

ClickHouse 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 472 integrations available for ClickHouse and Tableau.

Popular · 8 of 472
All ClickHouse 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