Skip to content
Accounting and finance ⇄ Database

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

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

Work with Pigment's financial data straight from TimescaleDB: read it with ordinary queries, write to it from your own code, and let Stacksync keep both sides consistent.

Engineers need finance data more often than finance systems make it easy to get: for internal tools, reporting services, or logic that reacts to invoices and payments. Working through the vendor API means rate limits, pagination, and glue code that has to be maintained forever.

Stacksync mirrors Metrics, Dimension lists, Tables, Scenarios from Pigment into Views, Schemas, Hypertables, Chunks in TimescaleDB and keeps the two in sync bi-directionally and in real time. Your services read finance records with normal queries against TimescaleDB, and rows your code writes or updates flow back into Pigment with validation, so the finance system stays the system of record.

Common use cases

  • Push CRM pipeline data (deals, stages, amounts) into Pigment for revenue and capacity planning.
  • Export approved budgets and forecasts back to a warehouse or Postgres for downstream reporting.
  • Sync product or IoT telemetry stored in TimescaleDB into a CRM so account teams see usage metrics next to the customer record.
  • Replicate subscription and billing events from operational Postgres tables into Timescale hypertables for time-series analysis.

Query finance data like any other data

Customers, invoices, and payments from Pigment live in TimescaleDB as regular tables or collections your team can join, index, and query.

Internal tools without API plumbing

Build dashboards and back-office tools directly on TimescaleDB; Stacksync handles the API calls, rate limits, and retries against Pigment.

Write back safely

Updates written to the synced tables in TimescaleDB propagate into Pigment, so automations can create or correct finance records without custom integration code.

What you can sync between Pigment and TimescaleDB

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.

Pigment objects TimescaleDB objects
Tables Row-based transactional data loaded into models from source systems Continuous Aggregates Incrementally maintained rollups that serve as pre-aggregated read sources for downstream systems.
Scenarios Versions such as budget, forecast, and actuals that give exported figures their context Regular PostgreSQL Tables Relational reference data such as devices, tenants, or accounts synced alongside the series data.
Data imports Scheduled loads that bring actuals from ERPs, CRMs, and HRIS into the model Views Standard SQL views used to shape or filter data for consumers.
Users and permissions Access controls governing which model areas a sync can touch Schemas Postgres namespaces used to separate synced datasets by team or environment.
Applications Planning models organized by domain such as finance, sales, or workforce Hypertables Time-partitioned tables that hold the main time-series data; the primary read and write target in syncs.
Metrics Multidimensional values holding plans and actuals; the main target for inbound data Chunks Time-bounded partitions of a hypertable; syncs read and write through the parent hypertable and never address chunks directly.
What ships with Pigment ⇄ TimescaleDB

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Pigment and TimescaleDB connectors work

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

TimescaleDB

Integration surface
SQL wire protocol (PostgreSQL)
Authentication
Database credentials
Change detection
Log-based capture via PostgreSQL logical decoding where the deployment allows it — hypertable changes surface on the underlying chunk tables and must be remapped to the parent — or timestamp-based polling on time columns; regular Postgres tables replicate through standard logical replication
Capabilities
read · write · CDC
Rate limits
No API rate limits; throughput is bounded by database resources and connection limits.
How it works

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

    Choose tables

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

Pigment and TimescaleDB 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 Pigment and TimescaleDB.

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.