Skip to content
Database ⇄ Analytics

Neo4j to Tableau integration — real-time data sync

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

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

Tableau is a read-only source: Stacksync reads its data in real time and delivers it into Neo4j, so Neo4j 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 Neo4j 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 Read Databases, Tables, and Fields from the Metadata API to populate a data catalog with Tableau lineage and column definitions.
  • 02 Mirror the Projects and Workbooks content hierarchy into an internal catalog so teams discover dashboards from a central index.
  • 03 Keep a customer-360 graph continuously updated from ERP, CRM, and support sources.
  • 04 Mirror CRM accounts and contacts into a graph to model buying-group and referral relationships.

Common sync patterns

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 Neo4j as they change, instead of going stale after a one-time import.

Where Tableau tracks product events: behavior onto stored records

Signup, usage, and lifecycle events captured in Tableau sync into Neo4j as rows, so applications and internal tools can read behavioral data next to the records they already keep.

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

Neo4j objects Tableau objects How this pairing syncs
Labels Node type markers used to map source tables or objects onto the graph. Fields and Columns Columns and calculated fields with their descriptions, exposed by the Metadata API; read to populate a data catalog with governed definitions. Labels is specific to Neo4j and Fields and Columns to Tableau — each maps to any object or custom field on the other side.
Indexes & Constraints Uniqueness constraints and indexes that make MERGE-based upserts reliable and fast. 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. Indexes & Constraints is specific to Neo4j and Published Data Sources to Tableau — each maps to any object or custom field on the other side.
Databases Named databases in a single instance that scope multi-tenant or multi-domain syncs. Workbooks Workbook content and metadata read via the REST and Metadata APIs; create, update, and delete events fire webhooks for change detection. Databases is specific to Neo4j and Workbooks to Tableau — each maps to any object or custom field on the other side.
Users & Roles Security principals controlling what an integration credential can query or modify. Views Worksheets and dashboards inside workbooks; their data and crosstab export as CSV via the REST query-view-data endpoint. Users & Roles is specific to Neo4j and Views to Tableau — each maps to any object or custom field on the other side.
Nodes Entity records (customers, products, accounts) written from source systems as labeled nodes. Projects Folders that organize content and set permissions; listed via REST to mirror the site's content hierarchy into a catalog. Nodes is specific to Neo4j and Projects to Tableau — each maps to any object or custom field on the other side.
Relationships Typed, directed edges that carry the connections syncs exist to model. 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. Relationships is specific to Neo4j and Users to Tableau — each maps to any object or custom field on the other side.

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

Neo4j Tableau Sub-second propagation

DetectionChanges in Neo4j are captured at the source via change data capture — no polling loop against its API. Neo4j Change Data Capture on Enterprise and Aura streams graph changes.

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

Tableau Neo4j 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 written to Neo4j through its API, with automatic retries and rate-limit backoff.

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 Neo4j ⇄ Tableau

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

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

Real-time

Real-time sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Neo4j and Tableau connectors work

Neo4j

Integration surface
Bolt binary protocol with Cypher via official drivers, plus an HTTP query API
Authentication
Username/password (basic auth); enterprise deployments add SSO options
Change detection
Neo4j Change Data Capture on Enterprise and Aura streams graph changes; otherwise Cypher polling on timestamp properties
Capabilities
read · write · CDC

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

    Choose tables

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

Neo4j 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 449 integrations available for Neo4j and Tableau.

Popular · 8 of 449
All Neo4j 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