Skip to content
Data warehouse ⇄ Accounting and finance

Databricks to Pigment integration — real-time, two-way sync

Keep Databricks and Pigment 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 Databricks and Pigment

Land the financial records from Pigment in Databricks continuously, and write results back, without building or maintaining a pipeline.

Finance data belongs in the warehouse: revenue, invoices, payments, and customers joined with everything else the business measures. Getting it there usually means an extraction pipeline that breaks quietly and delivers yesterday's numbers.

Stacksync syncs Tables, Scenarios, Data imports, Users and permissions from Pigment into tables in Databricks in real time, and the connection works in both directions: values computed in Databricks can be written back to fields in Pigment where you want them operational. Schema changes are handled, API limits are managed, and the sync is something you configure rather than code you maintain.

Common use cases

  • Keep dimension lists such as departments and cost centers consistent with master data in the ERP.
  • Sync headcount and compensation data from an HRIS into workforce planning models.
  • Use Change Data Feed to propagate only changed rows to downstream apps instead of full-table scans.
  • Serve ML feature outputs computed in Databricks to production apps through a synced operational store.

Revenue joined with everything else

Analysts combine Pigment's financial records with product, marketing, or operational data already in Databricks for reporting the finance system cannot do alone.

Write-back of computed fields

Scores or segments computed in Databricks, like payment-risk flags or customer tiers, sync back onto records in Pigment where the finance team can act on them.

Queryable history for audit and reconciliation

A continuously synced copy in Databricks gives you a durable, queryable record of financial data for month-end and audit questions.

What you can sync between Databricks and Pigment

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.

Databricks objects Pigment objects
Catalogs Top level of the Unity Catalog namespace, scoping which schemas a sync can address. Metrics Multidimensional values holding plans and actuals; the main target for inbound data
Schemas Group tables and views; syncs typically target a dedicated schema per source system. Dimension lists Master data like accounts, products, or employees that metrics are sliced by
Delta Tables The primary read and write target; operational data lands here as managed or external tables. Tables Row-based transactional data loaded into models from source systems
Views Curated read-only projections used as sync sources for downstream tools. Scenarios Versions such as budget, forecast, and actuals that give exported figures their context
Materialized Views Precomputed results read on a schedule for reverse-ETL style syncs. Data imports Scheduled loads that bring actuals from ERPs, CRMs, and HRIS into the model
Volumes Unity Catalog file storage used for staging bulk loads. Users and permissions Access controls governing which model areas a sync can touch
What ships with Databricks ⇄ Pigment

Connect Databricks and Pigment for flexible, real-time data sync.

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

Real-time

Two-way sync

Changes in Databricks or Pigment instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Databricks or Pigment 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 Databricks or Pigment record.

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Databricks and Pigment.

How the Databricks and Pigment connectors work

Databricks

Integration surface
SQL over JDBC/ODBC via SQL warehouses, plus a REST API including statement execution
Authentication
Personal access tokens or OAuth machine-to-machine credentials for service principals
Change detection
Delta Lake Change Data Feed for row-level changes; otherwise incremental polling on watermark columns
Capabilities
read · write · CDC
Rate limits
Throughput depends on the SQL warehouse size; API calls are subject to workspace rate limits

Pigment

Integration surface
REST-based import and export API
Authentication
API keys, issued separately for import and export
Change detection
no change feed; syncs run scheduled imports and exports
Capabilities
read · write
Rate limits
subject to the platform's API rate limits
How it works

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

    Choose tables

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

Databricks and Pigment integration FAQ

SECURITY

Security teams love 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
CSA STAR
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 386 integrations available for Databricks and Pigment.

Popular · 8 of 386
Coworkers laughing in front of a laptop in a casual office setting

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