Skip to content
Database ⇄ Analytics

Couchbase to Tableau integration — real-time data sync

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

Give Tableau the users, events, and records that live in Couchbase in real time, and sync the cohorts and scores Tableau computes back into Couchbase where your applications read them.

Tableau is a read-only source: Stacksync reads its data in real time and delivers it into Couchbase, so Couchbase 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 Couchbase 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.

Common use cases

  • 01 Track Extract Refresh Tasks and DatasourceRefreshFailed webhook events to raise alerts in a database or ticketing system when refreshes fail.
  • 02 Read site Users and their site roles for periodic access reviews and to reconcile Tableau accounts against an HR or IdP source of record.
  • 03 Consolidate documents from multiple Couchbase clusters into a single analytical store.
  • 04 Write cleaned or enriched records from operational databases back into Couchbase collections that applications read.

Common sync patterns

Analytics on live operational data, minus the pipeline

The users, events, orders, and records stored in Couchbase land in Tableau as they change, so dashboards, funnels, and metrics run on current data instead of last night's extract.

One version of each user or account

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.

Filter and grouping dimensions kept fresh

Attributes teams slice by, such as plan, region, or account owner, stay current in Tableau because they sync from Couchbase as they change, instead of going stale after a one-time import.

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

Couchbase objects Tableau objects How this pairing syncs
Collections Table-like groupings of documents that syncs typically map one-to-one to destination tables. Extract Refresh Tasks Scheduled extract refreshes; status and history read via REST, with DatasourceRefreshSucceeded and Failed events delivered by webhooks. Collections is specific to Couchbase and Extract Refresh Tasks to Tableau — each maps to any object or custom field on the other side.
JSON Documents The core records; schemaless JSON keyed by document id, flattened or mapped to relational rows in syncs. 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 Documents is specific to Couchbase and Fields and Columns to Tableau — each maps to any object or custom field on the other side.
Global Secondary Indexes Indexes that make SQL++ query-based extraction efficient. 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. Global Secondary Indexes is specific to Couchbase and Published Data Sources to Tableau — each maps to any object or custom field on the other side.
XDCR replications Cluster-to-cluster replication streams, useful context when choosing a sync source cluster. Workbooks Workbook content and metadata read via the REST and Metadata APIs; create, update, and delete events fire webhooks for change detection. XDCR replications is specific to Couchbase and Workbooks to Tableau — each maps to any object or custom field on the other side.
Full-text search indexes Search indexes over documents, relevant when syncing searchable content. Views Worksheets and dashboards inside workbooks; their data and crosstab export as CSV via the REST query-view-data endpoint. Full-text search indexes is specific to Couchbase and Views to Tableau — each maps to any object or custom field on the other side.
Buckets Top-level data containers, roughly analogous to a database, that scope replication and memory quotas. Projects Folders that organize content and set permissions; listed via REST to mirror the site's content hierarchy into a catalog. Buckets is specific to Couchbase and Projects to Tableau — each maps to any object or custom field on the other side.

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

Couchbase Tableau Sub-second propagation

DetectionChanges in Couchbase are captured at the source via change data capture — no polling loop against its API. Database Change Protocol (DCP) streams document mutations.

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

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

Rate-limit considerations

  • Couchbase: Throughput is bounded by cluster sizing rather than 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 Couchbase ⇄ Tableau

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

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

Real-time

Real-time sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Couchbase and Tableau connectors work

Couchbase

Integration surface
SQL++ (N1QL) query service, key-value SDK APIs, and REST management APIs
Authentication
Database credentials with role-based access control, typically over TLS
Change detection
Database Change Protocol (DCP) streams document mutations; SQL++ polling on document fields as an alternative
Capabilities
read · write · CDC
Rate limits
Throughput is bounded by cluster sizing rather than API rate limits

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

    Choose tables

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

Couchbase 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 353 integrations available for Couchbase and Tableau.

Popular · 8 of 353
All Couchbase 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