Skip to content
Analytics ⇄ CRM

Tableau to Twenty CRM integration — real-time data sync

Keep Tableau and Twenty CRM 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 Tableau and Twenty CRM

Put live Twenty CRM data behind every dashboard and cohort in Tableau, and write the segments and scores Tableau computes back onto the Twenty CRM record — one connection, not a nightly export.

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

Tableau turns data into dashboards, cohorts, and metrics; Twenty CRM is where customers, contacts, deals, and activity actually live and change. The two meet wherever a number is really about a specific account, segment, or stage — yet most teams feed the CRM into analytics as a nightly extract or a hand-maintained connector, so the reporting lags the business and can't be sliced by the customers and segments that matter.

Stacksync syncs Custom Objects, Attachments, Workspace Members, People from Twenty CRM into Tableau field by field and within seconds, so every dashboard and cohort runs on current records instead of a stale copy. Because the connection runs both ways, the cohorts, scores, and metrics computed in Tableau write back to fields in Twenty CRM, landing where the people working accounts can see them. You decide which system owns which fields; Stacksync keeps every copy consistent and resolves conflicts by rules you set.

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 Opportunities into a finance system to keep revenue forecasts current.
  • 04 Mirror support tickets or tasks between Twenty and an operations tool.

Common sync patterns

Customer context in Tableau

Accounts, contacts, deals, and activity from Twenty CRM sync into Tableau, so metrics and dashboards group by real customers, segments, and stage instead of anonymous IDs.

Report on live CRM data

New records and status changes in Twenty CRM appear in Tableau within seconds, so dashboards and cohorts track the current pipeline rather than last night's export.

Where Twenty CRM accepts updates: segments and scores back on the record

Cohorts, scores, and computed metrics from Tableau sync onto fields in Twenty CRM, putting the analysis where reps and owners actually work the accounts.

What you can sync between Tableau and Twenty CRM

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.

Tableau objects Twenty CRM objects How this pairing syncs
Projects Folders that organize content and set permissions; listed via REST to mirror the site's content hierarchy into a catalog. Companies Account-level records that group people and opportunities. Projects is specific to Tableau and Companies to Twenty CRM — each maps to any object or custom field on the other side.
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. Opportunities Deal records tracked through pipeline stages, synced for forecasting. Users is specific to Tableau and Opportunities to Twenty CRM — each maps to any object or custom field on the other side.
Databases and Tables External assets indexed by Tableau Catalog; queried via the Metadata API GraphQL endpoint for lineage and impact analysis. Tasks To-dos linked to people, companies, or deals. Databases and Tables is specific to Tableau and Tasks to Twenty CRM — each maps to any object or custom field on the other side.
Extract Refresh Tasks Scheduled extract refreshes; status and history read via REST, with DatasourceRefreshSucceeded and Failed events delivered by webhooks. Notes Free-form notes attached to records, useful for mirroring activity from other tools. Extract Refresh Tasks is specific to Tableau and Notes to Twenty CRM — each maps to any object or custom field on the other side.
Fields and Columns Columns and calculated fields with their descriptions, exposed by the Metadata API; read to populate a data catalog with governed definitions. Custom Objects User-defined objects created in Twenty's data model settings, addressable through the same APIs as standard objects. Fields and Columns is specific to Tableau and Custom Objects to Twenty CRM — each maps to any object or custom field on the other side.
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. Attachments Files linked to records. Published Data Sources is specific to Tableau and Attachments to Twenty CRM — each maps to any object or custom field on the other side.

How changes propagate between Tableau and Twenty CRM

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.

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

Twenty CRM Tableau Sub-second propagation

DetectionTwenty CRM notifies Stacksync of record changes through webhook events. Webhooks on record create, update, and delete events, or polling on record update timestamps.

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 Twenty CRM records.

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.
  • Twenty CRM: Subject to the platform's API rate limits; self-hosted deployments control their own limits.
What ships with Tableau ⇄ Twenty CRM

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

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

Real-time

Real-time sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Tableau and Twenty CRM connectors work

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.

Twenty CRM

Integration surface
GraphQL and REST APIs
Authentication
API key
Change detection
Webhooks on record create, update, and delete events, or polling on record update timestamps
Capabilities
read · write · webhooks
Rate limits
Subject to the platform's API rate limits; self-hosted deployments control their own limits.
How it works

How to connect Tableau to Twenty CRM — 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 Tableau and Twenty CRM 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
    Tableau connected
    Twenty CRM connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Tableau and Twenty CRM 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 · Tableau ⇄ Twenty CRM
    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
    Tableau Twenty CRM
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Tableau and Twenty CRM 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.

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:

Related integrations

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

Popular · 7 of 367
Coworkers laughing in front of a laptop in a casual office setting

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