Real-time sync
Changes in MySQL or Tableau instantly reflect in both systems. No stale data, no manual imports.
Keep MySQL 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.
Tableau is a read-only source: Stacksync reads its data in real time and delivers it into MySQL, so MySQL always reflects the current state of Tableau — without exports, scripts, or schedulers.
A database holds the rows your business runs on: the users, events, orders, and records that every service reads and writes. Tableau is where people make sense of them, as dashboards, funnels, cohorts, and metrics. Moving the data from MySQL into Tableau usually means a hand-built extract or a change-data-capture pipeline that breaks the moment a column is renamed, and reporting that always trails last night's load.
A user, account, or record corrected in either system updates the other, so the identity your reports group by matches the identity your database stores.
Attributes teams slice by, such as plan, region, or account owner, stay current in Tableau because they sync from MySQL as they change, instead of going stale after a one-time import.
Signup, usage, and lifecycle events captured in Tableau sync into MySQL as rows, so applications and internal tools can read behavioral data next to the records they already keep.
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.
| MySQL objects | Tableau objects | How this pairing syncs | |
|---|---|---|---|
| Views Read-side 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. | |
| Primary and Unique Keys Match keys for idempotent upserts and conflict handling. | Extract Refresh Tasks Scheduled extract refreshes; status and history read via REST, with DatasourceRefreshSucceeded and Failed events delivered by webhooks. | Primary and Unique Keys is specific to MySQL and Extract Refresh Tasks to Tableau — each maps to any object or custom field on the other side. | |
| JSON Columns Validated semi-structured payloads for nested SaaS data. | Fields and Columns Columns and calculated fields with their descriptions, exposed by the Metadata API; read to populate a data catalog with governed definitions. | JSON Columns is specific to MySQL and Fields and Columns to Tableau — each maps to any object or custom field on the other side. | |
| Stored Procedures Server-side logic that can post-process synced rows. | 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. | Stored Procedures is specific to MySQL and Published Data Sources to Tableau — each maps to any object or custom field on the other side. | |
| Triggers An alternative change-capture mechanism when binlog access is unavailable. | Workbooks Workbook content and metadata read via the REST and Metadata APIs; create, update, and delete events fire webhooks for change detection. | Triggers is specific to MySQL and Workbooks to Tableau — each maps to any object or custom field on the other side. | |
| Databases (Schemas) Top-level namespaces that scope a sync's reads and writes. | Projects Folders that organize content and set permissions; listed via REST to mirror the site's content hierarchy into a catalog. | Databases (Schemas) is specific to MySQL and Projects to Tableau — each maps to any object or custom field on the other side. |
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.
DetectionChanges in MySQL are captured at the source via change data capture — no polling loop against its API. Database triggers — Stacksync creates deterministic triggers for internal logging and syncing (requires log_bin_trust_function_creators=ON when.
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 MySQL records.
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 MySQL as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every MySQL–Tableau connection.
Changes in MySQL or Tableau instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever MySQL or Tableau data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single MySQL or Tableau record.
Track your MySQL ⇄ Tableau sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between MySQL and Tableau.
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.
Authenticate MySQL 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.
Pick the MySQL 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time integration between MySQL and Tableau — Tableau is a read-only source, so data flows from it into the other system: authenticate both systems, choose the objects to sync, map fields visually, and changes propagate in milliseconds — no code required.
Common patterns for MySQL and Tableau: One version of each user or account; Filter and grouping dimensions kept fresh; Where Tableau tracks product events: behavior onto stored records. A user, account, or record corrected in either system updates the other, so the identity your reports group by matches the identity your database stores.
MySQL: SQL wire protocol (MySQL client/server protocol). Authentication: Database credentials entered as a connection string or parameters, with optional SSL root certificate upload and optional SSH tunnel (SSH user + SSH host). Tableau: 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. Stacksync manages authentication, retries, and rate limits on both sides.
Tableau: REST API calls are versioned (e.g. 3.x) and tied to the Tableau Server or Cloud release; older servers cap the available API version and endpoints. MySQL: The binary log in ROW format records every row-level change, enabling log-based CDC without adding triggers to user tables. Stacksync's field mapping accounts for these differences between MySQL and Tableau without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means MySQL and Tableau records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed MySQL and Tableau connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom MySQL–Tableau integration in-house.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 478 integrations available for MySQL and Tableau.