Skip to content
Accounting and finance ⇄ Data warehouse

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

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

Land the financial records from Pigment in Snowflake 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 Snowflake in real time, and the connection works in both directions: values computed in Snowflake 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 Sync headcount and compensation data from an HRIS into workforce planning models.
  • 02 Push CRM pipeline data (deals, stages, amounts) into Pigment for revenue and capacity planning.
  • 03 Activate modeled Snowflake tables by syncing scores and attributes back into CRM fields sales can act on
  • 04 Keep a customer 360 table aligned with its source systems in both directions instead of one-way reverse ETL

Common sync patterns

Queryable history for audit and reconciliation

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

Finance analytics without ETL

Invoices, payments, and customer records from Pigment arrive in Snowflake as queryable tables, current within seconds instead of a day behind.

Revenue joined with everything else

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

What you can sync between Pigment and Snowflake

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 Snowflake objects How this pairing syncs
Tables Row-based transactional data loaded into models from source systems Tables The main landing and activation target for synced records. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Users and permissions Access controls governing which model areas a sync can touch Virtual Warehouses The compute a sync's queries run on, sized independently of storage. Users and permissions is specific to Pigment and Virtual Warehouses to Snowflake — each maps to any object or custom field on the other side.
Applications Planning models organized by domain such as finance, sales, or workforce Databases Top-level containers that scope which data a sync can touch. Applications is specific to Pigment and Databases to Snowflake — each maps to any object or custom field on the other side.
Metrics Multidimensional values holding plans and actuals; the main target for inbound data Schemas Namespaces within a database used to organize synced tables. Metrics is specific to Pigment and Schemas to Snowflake — each maps to any object or custom field on the other side.
Dimension lists Master data like accounts, products, or employees that metrics are sliced by Views Modeled projections used as the source side of outbound syncs. Dimension lists is specific to Pigment and Views to Snowflake — each maps to any object or custom field on the other side.
Scenarios Versions such as budget, forecast, and actuals that give exported figures their context Materialized Views Precomputed results synced outward for low-latency reads. Scenarios is specific to Pigment and Materialized Views to Snowflake — each maps to any object or custom field on the other side.

How changes propagate between Pigment and Snowflake

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.

Pigment Snowflake 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 Snowflake as a row-level write, with types converted between the two schemas.

Snowflake Pigment Sub-second propagation

DetectionChanges in Snowflake are captured at the source via change data capture — no polling loop against its API. The setup script grants "create stream" on synced schemas (Snowflake streams), but the docs do not name the change-capture mechanism.

DeliveryEach detected change is written to Pigment through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Pigment: Subject to the platform's API rate limits.
  • Snowflake: No conventional API rate limits; cost and throughput are governed by virtual warehouse size and running time.
What ships with Pigment ⇄ Snowflake

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Pigment ⇄ Snowflake 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 Snowflake.

How the Pigment and Snowflake 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

Snowflake

Integration surface
SQL via JDBC/ODBC and native drivers, plus the Snowflake SQL REST API
Authentication
Dedicated Snowflake service user + role with RSA key-pair authentication (Stacksync-provided public key), created via a setup script requiring SECURITY_ADMIN and ACCOUNTADMIN roles
Change detection
Not explicitly stated; the setup script grants "create stream" on synced schemas (Snowflake streams), but the docs do not name the change-capture mechanism
Capabilities
read · write · CDC
Rate limits
No conventional API rate limits; cost and throughput are governed by virtual warehouse size and running time
Snowflake setup guide
How it works

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

    Choose tables

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

Pigment and Snowflake 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
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:

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 452 integrations available for Pigment and Snowflake.

Popular · 6 of 452
All Pigment integrations All Snowflake 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