Real-time
Two-way sync
Changes in Firebolt or Pigment instantly reflect in both systems. No stale data, no manual imports.
Data warehouse ⇄ Accounting and finance
Firebolt to Pigment integration — real-time, two-way sync
Keep Firebolt 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 Firebolt and Pigment
Land the financial records from Pigment in Firebolt 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 Firebolt in real time, and the connection works in both directions: values computed in Firebolt 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
- 01 Export approved budgets and forecasts back to a warehouse or Postgres for downstream reporting.
- 02 Keep dimension lists such as departments and cost centers consistent with master data in the ERP.
- 03 Keep dimension tables aligned with source systems while high-volume event data loads through separate batch pipelines.
- 04 Sync aggregated results from Firebolt back to operational tools that need computed metrics (reverse ETL).
Common sync patterns
Revenue joined with everything else
Analysts combine Pigment's financial records with product, marketing, or operational data already in Firebolt for reporting the finance system cannot do alone.
Write-back of computed fields
Scores or segments computed in Firebolt, 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 Firebolt gives you a durable, queryable record of financial data for month-end and audit questions.
What you can sync between Firebolt 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.
| Firebolt objects | Pigment objects | How this pairing syncs | |
|---|---|---|---|
| Tables Managed columnar tables written with SQL; the main sync destination. | Tables Row-based transactional data loaded into models from source systems | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Aggregating indexes Precomputed rollups maintained at write time; incremental loads update them automatically. | Scenarios Versions such as budget, forecast, and actuals that give exported figures their context | Aggregating indexes is specific to Firebolt and Scenarios to Pigment — each maps to any object or custom field on the other side. | |
| Engines Compute resources that must be running for a sync to read or write. | Data imports Scheduled loads that bring actuals from ERPs, CRMs, and HRIS into the model | Engines is specific to Firebolt and Data imports to Pigment — each maps to any object or custom field on the other side. | |
| Databases Logical containers holding the tables a sync targets. | Users and permissions Access controls governing which model areas a sync can touch | Databases is specific to Firebolt and Users and permissions to Pigment — each maps to any object or custom field on the other side. | |
| External tables References to files in object storage used to stage bulk loads. | Applications Planning models organized by domain such as finance, sales, or workforce | External tables is specific to Firebolt and Applications to Pigment — each maps to any object or custom field on the other side. | |
| Views Curated query surfaces commonly used as sources for reverse ETL. | Metrics Multidimensional values holding plans and actuals; the main target for inbound data | Views is specific to Firebolt and Metrics to Pigment — each maps to any object or custom field on the other side. |
How changes propagate between Firebolt and Pigment
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.
Firebolt Pigment Interval-based propagation
DetectionStacksync polls Firebolt for changes on an incremental schedule, reading only records changed since the previous pass. Polling.
DeliveryEach detected change is written to Pigment through its API, with automatic retries and rate-limit backoff.
Pigment Firebolt Interval-based propagation
DetectionStacksync polls Pigment for changes on an incremental schedule, reading only records changed since the previous pass. No change feed.
DeliveryEach detected change is applied to Firebolt as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- Firebolt: No fixed request quota; throughput depends on the engine size attached to the workload.
- Pigment: Subject to the platform's API rate limits.
What ships with Firebolt ⇄ Pigment
Connect Firebolt and Pigment for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Firebolt–Pigment connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Firebolt 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 Firebolt or Pigment record.
Observability
Monitoring
Track your Firebolt ⇄ Pigment sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Firebolt and Pigment.
How the Firebolt and Pigment connectors work
Firebolt
- Integration surface
- SQL over a REST API, with JDBC, Python, and Node.js SDKs
- Authentication
- Service account credentials (client ID and secret) exchanged for OAuth 2.0 tokens
- Change detection
- Polling; Firebolt is an analytics destination and does not expose a change feed
- Capabilities
- read · write
- Rate limits
- No fixed request quota; throughput depends on the engine size attached to the workload
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 Firebolt 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.
- 01
Connect your apps
Authenticate Firebolt 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.
Firebolt
connected
Pigment
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Firebolt 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.
objects · Firebolt ⇄ PigmentCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Firebolt PigmentCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Firebolt and Pigment integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Firebolt and Pigment: authenticate both systems, choose the objects to sync (such as Firebolt's Tables and Aggregating indexes), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Pigment side: Tables, Scenarios, Data imports, Users and permissions, plus custom fields where Pigment exposes them. On the Firebolt side: Views, Aggregating indexes, Engines, Databases. Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
-
Common patterns for Firebolt and Pigment: Revenue joined with everything else; Write-back of computed fields; Queryable history for audit and reconciliation. Analysts combine Pigment's financial records with product, marketing, or operational data already in Firebolt for reporting the finance system cannot do alone.
-
Firebolt: SQL over a REST API, with JDBC, Python, and Node.js SDKs. Authentication: Service account credentials (client ID and secret) exchanged for OAuth 2.0 tokens. Pigment: REST-based import and export API. Authentication: API keys, issued separately for import and export. Stacksync manages authentication, retries, and rate limits on both sides.
-
Pigment: Scenario versioning (budget versus forecast versus actuals) is native to the model, so exports need a scenario context to be meaningful. Firebolt: Compute is organized into engines that start and stop independently of storage, so sync schedules interact with engine availability and cost. Stacksync's field mapping accounts for these differences between Firebolt and Pigment without custom code.
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 348 integrations available for Firebolt and Pigment.
Popular · 4 of 348
No integrations match .
