Pigment + Snowflake
Connect Pigment and Snowflake to Power Smarter Business Planning
Sync your financial and operational planning data with your cloud data warehouse for faster, more accurate decisions.
Why integrate Pigment and Snowflake?
Pigment is a modern business planning platform built for FP&A, revenue, and workforce planning teams who need agility and collaboration at scale. Snowflake is the leading cloud data warehouse, centralizing large volumes of enterprise data from across the business. Together, they give you a solid planning and analytics backbone — Pigment consumes datasets stored in Snowflake to build dynamic models, while actuals and outputs from Pigment can flow back into Snowflake for broader reporting and analysis.
Automate & integrate Pigment & Snowflake
Use case
Automated Actuals Ingestion for Financial Planning
Pull the latest actuals from Snowflake — including revenue, expenses, and COGS — directly into Pigment on a scheduled basis to keep financial models current. FP&A analysts no longer need to manually export and upload data at the start of every planning cycle. Plans and variance analyses are always built on fresh, warehouse-verified numbers.
Use case
Headcount and Workforce Data Sync
Automatically sync employee records, department hierarchies, and compensation data from Snowflake into Pigment to keep workforce plans accurate. HR and FP&A teams can collaborate on headcount models without waiting for data refreshes from the People team. Any changes to org structure or compensation in the source systems show up in Pigment automatically.
Use case
Revenue Actuals from CRM and ERP via Snowflake
Many organizations centralize CRM (Salesforce, HubSpot) and ERP (NetSuite, SAP) data in Snowflake before it flows into planning tools. This integration uses Snowflake as the single source of truth to push curated, cleansed revenue actuals into Pigment's revenue planning models. Teams get a consistent view of bookings, recognized revenue, and pipeline without reconciling data from multiple systems.
Use case
Push Pigment Planning Outputs Back to Snowflake
Once finance teams finalize budgets, forecasts, or scenarios in Pigment, this integration writes those outputs back to Snowflake so BI tools, data teams, and downstream systems can pick them up. That means company-wide reporting can blend actuals with plans in a single warehouse layer. Tableau, Looker, or Power BI dashboards can then surface plan-vs-actual comparisons without any manual data movement.
Use case
Product and Usage Metrics for SaaS Planning Models
SaaS companies tracking product usage, customer health, and expansion metrics in Snowflake can feed those signals directly into Pigment's revenue and capacity planning models. Revenue teams can factor in churn signals, upsell potential, and seat expansion data when building forecasts — moving away from static spreadsheet assumptions toward projections grounded in real product data.
Use case
Supply Chain and Cost Data for Operational Planning
Operations and supply chain teams storing procurement, inventory, and COGS data in Snowflake can pull those datasets into Pigment for operational and margin planning. When supplier costs or inventory levels change in Snowflake, Pigment models update automatically — so gross margin re-forecasting doesn't require a manual data refresh. Particularly useful for retail, manufacturing, and e-commerce companies with complex cost structures.
Use case
Scheduled Data Refresh for Rolling Forecasts
Rolling forecast models in Pigment need continuous data freshness to stay useful. Tray.ai orchestrates scheduled pulls from Snowflake — daily, weekly, or on a custom cadence — to refresh all underlying datasets that Pigment models depend on. Finance teams set the schedule once and every planning session starts with current data.
Get started with Pigment & Snowflake integration today
Pigment & Snowflake Challenges
What challenges are there when working with Pigment & Snowflake and how will using Tray.ai help?
Challenge
Schema Drift Between Snowflake Tables and Pigment Datasets
Snowflake schemas change over time as data engineers add, rename, or deprecate columns. When that happens without a matching update to Pigment's dataset structure, data loads break silently or load incorrect values — and nobody notices until a planning meeting surfaces bad numbers.
How Tray.ai Can Help:
Tray.ai workflows can include schema validation steps that compare incoming Snowflake data against expected column mappings before loading into Pigment. If there's a mismatch, the workflow stops and alerts the data team rather than quietly loading corrupt data.
Challenge
Volume and Latency When Loading Large Snowflake Datasets
Financial actuals and operational datasets in Snowflake can contain millions of rows spanning multiple fiscal years. Pushing that volume through API calls to Pigment without careful handling leads to timeouts, rate limit errors, or incomplete loads that are hard to track down.
How Tray.ai Can Help:
Tray.ai handles large data volumes through batching and chunking logic built into workflow steps, so records load into Pigment in appropriately sized increments. Retry logic and error handling within workflows mean partial failures recover automatically without restarting the entire load.
Challenge
Keeping Pigment Models in Sync Across Multiple Snowflake Sources
Enterprise planning models in Pigment often draw from many different Snowflake tables — finance, HR, sales ops, and product analytics — each owned by different teams running on different update schedules. Coordinating all those sources so Pigment always has a coherent, consistent view is genuinely hard to manage by hand.
How Tray.ai Can Help:
Tray.ai lets teams build orchestrated multi-step workflows that sequence data pulls from multiple Snowflake sources before triggering a consolidated load into Pigment. You can enforce dependencies between datasets so Pigment only updates once all upstream sources have successfully refreshed.
Challenge
Maintaining Data Governance and Access Control Across Both Platforms
Snowflake holds sensitive financial, compensation, and customer data subject to strict access controls. Making sure only permissioned, transformed data flows into Pigment — with raw sensitive fields masked or excluded — requires careful handling that manual processes often get wrong.
How Tray.ai Can Help:
Tray.ai workflows apply transformation and field-filtering logic before data ever reaches Pigment, so sensitive columns are excluded or masked in transit. Credentials for both Snowflake and Pigment are stored securely in tray.ai's credential management layer, and all data flows are logged for audit purposes.
Challenge
Lack of Real-Time Feedback When Data Loads Fail
When a scheduled Snowflake-to-Pigment sync fails silently, planning teams can spend an entire day — or longer — working with stale data before anyone realizes the refresh didn't complete. Without alerting and observability, pipeline failures go unnoticed until they cause real planning errors downstream.
How Tray.ai Can Help:
Tray.ai workflows include configurable error handling and notification steps that immediately alert the right team via Slack, email, or PagerDuty when a sync fails or returns unexpected results. Full execution logs are available in the tray.ai platform, giving data teams complete visibility into every run so they can diagnose and fix issues fast.
Start using our pre-built Pigment & Snowflake templates today
Start from scratch or use one of our pre-built Pigment & Snowflake templates to quickly solve your most common use cases.
Pigment & Snowflake Templates
Find pre-built Pigment & Snowflake solutions for common use cases
Template
Daily Actuals Sync from Snowflake to Pigment
This template runs on a daily schedule to query the latest financial actuals from a designated Snowflake table or view, transform the data to match Pigment's expected schema, and load it into the corresponding Pigment dataset — so every planning model wakes up refreshed.
Steps:
- Trigger workflow on a scheduled daily cadence (e.g., 6 AM local time)
- Execute a parameterized SQL query in Snowflake to fetch actuals for the current period
- Transform and map Snowflake column names and data types to Pigment dataset schema
- Load transformed records into the target Pigment dataset via the Pigment API
- Send a Slack or email notification confirming successful sync or flagging errors
Connectors Used: Snowflake, Pigment
Template
Write Pigment Approved Forecast to Snowflake
When a finance team marks a forecast version as approved in Pigment, this template pulls the finalized forecast data from Pigment and writes it into a dedicated Snowflake table, making it immediately available for BI reporting and downstream consumption.
Steps:
- Trigger on a Pigment webhook event when a forecast or budget version is approved
- Fetch the relevant forecast data from Pigment using the Pigment API
- Format and stage the data for insertion into Snowflake
- Insert or upsert records into the designated Snowflake forecast output table
- Log the sync event and notify the data team via email or messaging tool
Connectors Used: Pigment, Snowflake
Template
Headcount Roster Sync from Snowflake to Pigment
This template queries the employee roster and compensation data from Snowflake on a recurring basis and updates the Pigment workforce planning dataset, so headcount models always reflect current org structure and salary data.
Steps:
- Run on a weekly or bi-weekly schedule aligned with HR data refresh cycles
- Query Snowflake for active employee records including role, department, cost center, and compensation
- Apply transformation logic to normalize fields to Pigment's headcount schema
- Upsert records into the Pigment workforce planning dataset
- Flag any anomalies (e.g., missing cost centers) and route alerts to the FP&A team
Connectors Used: Snowflake, Pigment
Template
Snowflake Revenue Actuals to Pigment Revenue Model
This template pulls cleansed, aggregated revenue actuals — sourced from CRM and ERP data already centralized in Snowflake — and loads them into Pigment's revenue planning model, so revenue forecasts stay reconciled against real bookings and recognized revenue.
Steps:
- Trigger on a scheduled cadence or on-demand via an API call
- Run a Snowflake SQL query to aggregate bookings, recognized revenue, and ARR by segment and period
- Map aggregated revenue fields to Pigment's revenue model dimensions
- Load data into the Pigment revenue actuals dataset
- Trigger a Pigment model recalculation if supported by the API to reflect new actuals
Connectors Used: Snowflake, Pigment
Template
Snowflake Product Usage Metrics to Pigment SaaS Planning
This template syncs product usage signals — active users, feature adoption rates, and expansion triggers — from Snowflake into Pigment, so SaaS revenue teams can build planning models on live product data rather than stale assumptions.
Steps:
- Schedule trigger aligned with product analytics refresh cadence
- Query Snowflake for usage metrics segmented by account, product tier, and time period
- Transform usage metrics to match Pigment's planning model input format
- Load metrics into a dedicated Pigment dataset for SaaS revenue and capacity planning
- Alert revenue operations team if key metrics fall outside expected thresholds
Connectors Used: Snowflake, Pigment
Template
Bi-Directional Data Reconciliation Between Pigment and Snowflake
This template runs a reconciliation check by comparing data loaded in Pigment against source records in Snowflake, flagging discrepancies in row counts, totals, or key figures so data integrity issues get caught before they affect planning decisions.
Steps:
- Run reconciliation workflow after every major data load into Pigment
- Query Snowflake for expected record counts and aggregated totals per dataset
- Fetch corresponding summary metrics from Pigment via the API
- Compare values and calculate variance between source and target
- Generate a reconciliation report and route discrepancies to the data governance team
Connectors Used: Pigment, Snowflake