Skip to content
ERP ⇄ Analytics

Brightpearl to Tableau integration — real-time data sync

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

Put Brightpearl's records into Tableau as live data for reporting and dashboards, without nightly exports, and send the segments and metrics Tableau computes back where Brightpearl can use them.

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

ERP data is some of the most requested data for analysis and some of the hardest to pull: the record types are many, the APIs are strict, and export jobs break on every upgrade. Whether Brightpearl carries financials, operations, workforce data, or all three, those numbers belong in Tableau, next to the product, behavioral, and web data the team already measures.

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 Push invoices and payments into an accounting platform for reconciliation.
  • 04 Keep the product catalog aligned between Brightpearl and e-commerce channels, including price list changes.

Common sync patterns

Write-back where Brightpearl exposes writable fields: segments and scores return

Segments, scores, or metrics computed in Tableau sync onto the matching records in Brightpearl, so operations act on what the analysis found.

Where Brightpearl holds the books: revenue and finance dashboards from live data

Financial records from Brightpearl land in Tableau as they change, so revenue, margin, and spend dashboards read current figures rather than last night's export.

Where Brightpearl runs order-to-cash: customer and account analytics

Orders, invoices, and account records from Brightpearl join the behavioral and usage data Tableau already tracks, so customer analysis spans activity and dollars in one view.

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

Brightpearl objects Tableau objects How this pairing syncs
Custom fields Per-object custom attributes included in field mappings. 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 fields is specific to Brightpearl and Fields and Columns to Tableau — each maps to any object or custom field on the other side.
Products SKU records with variants and price lists, synced with e-commerce and ERP catalogs. 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. Products is specific to Brightpearl and Published Data Sources to Tableau — each maps to any object or custom field on the other side.
Sales orders Orders from all channels; the central object for fulfillment and revenue syncs. Workbooks Workbook content and metadata read via the REST and Metadata APIs; create, update, and delete events fire webhooks for change detection. Sales orders is specific to Brightpearl and Workbooks to Tableau — each maps to any object or custom field on the other side.
Purchase orders Supplier orders synced with procurement or accounting systems. Views Worksheets and dashboards inside workbooks; their data and crosstab export as CSV via the REST query-view-data endpoint. Purchase orders is specific to Brightpearl and Views to Tableau — each maps to any object or custom field on the other side.
Contacts Customers and suppliers in one contact model, matched to CRM records by email or reference. Projects Folders that organize content and set permissions; listed via REST to mirror the site's content hierarchy into a catalog. Contacts is specific to Brightpearl and Projects to Tableau — each maps to any object or custom field on the other side.
Inventory and warehouses On-hand and allocated stock by warehouse, read for availability publishing. 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. Inventory and warehouses is specific to Brightpearl and Users to Tableau — each maps to any object or custom field on the other side.

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

Brightpearl Tableau Sub-second propagation

DetectionBrightpearl notifies Stacksync of record changes through webhook events. Webhooks for object created/updated events, with resource search polling as a fallback.

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

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

Rate-limit considerations

  • Brightpearl: Requests are throttled per account under Brightpearl's API usage policies; bulk operations should use batch endpoints.
  • 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 Brightpearl ⇄ Tableau

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

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

Real-time

Real-time sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Brightpearl and Tableau connectors work

Brightpearl

Integration surface
REST API, organized into services (order, product, contact, warehouse, accounting)
Authentication
OAuth 2.0 (authorization code grant) for current apps; legacy private and public apps authenticate with app reference and account token headers
Change detection
Webhooks for object created/updated events, with resource search polling as a fallback
Capabilities
read · write · webhooks
Rate limits
Requests are throttled per account under Brightpearl's API usage policies; bulk operations should use batch endpoints

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

    Choose tables

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

Brightpearl 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 439 integrations available for Brightpearl and Tableau.

Popular · 8 of 439
All Brightpearl 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