Connect Google BigQuery to Pigment and plan from current actuals
Bring the data your teams already maintain in Google BigQuery into Pigment through a native connector, so planning models start from the latest warehouse data. Built for FP&A teams who want to stop exporting data by hand, and for IT teams who want planning to read from a governed warehouse.

Google BigQuery
Connect Google BigQuery to Pigment to load warehouse query results into your planning models
Category
Integration method
Best for
Actuals reporting · Variance analysis · Driver-based forecasting
What can you do with Google BigQuery and Pigment?
- Start variance analysis right after close. Import the monthly actuals your data team publishes in Google BigQuery and compare them to budget in Pigment.
- Build driver-based forecasts on operational data. Use operational metrics from BigQuery, such as orders or usage, as drivers for revenue and cost forecasts.
- Shape data before it reaches your model. Filter, join, and aggregate tables in SQL so results land in your Block at your model's grain.
- Extend the connection to new planning teams. Share an existing BigQuery connection with new Applications as HR or Supply Chain planning comes online.
How the Google BigQuery integration works
Setup starts in Google Cloud with a dedicated service account, which Pigment recommends for security. You grant it the BigQuery Job User role on its project and BigQuery Data Viewer on each dataset, then generate a JSON key.
In Pigment, a Workspace Admin adds a BigQuery connection in the Integrations library, pastes the JSON key, and chooses which Applications can use it. A modeler then selects the connection in a Block’s import panel, enters a SQL query, and starts the import. Pigment loads the query result into the Block, and you can schedule that import to run automatically.
Key capabilities
- Limit access to the datasets you choose. Pigment’s service account gets BigQuery Data Viewer only on the datasets IT grants, so planning teams can’t query the rest of the warehouse.
- Reach datasets across Google Cloud projects. Grant the service account access to datasets in other projects, and one connection reads from all of them.
- Set imports to run on their own. Schedule each import up to 4 times, and get notified by email, in-app, or in Slack if a run fails or only partly completes.
- Run imports when your pipeline finishes. Trigger an import through Pigment’s import API once upstream jobs complete, then check whether it succeeded.
- Control who builds and runs imports. The Configure Imports and Run Imports permissions separate who can create import configurations from who can run existing ones.
Frequently Asked Questions
What data can I import from Google BigQuery into Pigment?
You can import the result of any SQL query on datasets the service account can read, including datasets in other Google Cloud projects, into a Pigment Block such as a Transaction List, Dimension List, or Metric.
Can planners use Google BigQuery data without accessing Google BigQuery themselves?
Yes. The connection authenticates with a service account, so planners work with the imported data in Pigment Blocks. What each person can see and edit follows their Pigment access rights.
Can Pigment send data back to Google BigQuery?
Not through the BigQuery connector, which only imports data. Pigment can export data to Google Cloud Storage through the Pigment REST API, and your team can load it into BigQuery from there.
Related integrations
See Pigment in action
The fastest way to understand Pigment is to see it in action. Sign up today and explore how agentic AI can transform the way you plan.

From 8 days to 4 min
Update P&L actuals & financial forecasting
80%
Time cut on data aggregation
12 hours
Saved per month on executive reporting
6 days faster
For scenarios creation and analysis