Close the loop on the AI Data Cloud
Read from Snowflake, and write plan data back
Pull query results from Snowflake into Nexadata, shape them for planning, and write forecasts, allocations and plan versions back to Snowflake tables, run by the finance team rather than a data engineering queue.
At a glance
Two-way connectorOut of Snowflake
- Your own SQL statement
- Run on a warehouse you choose
Back into Snowflake
- Append
- Upsert on a business key
- Overwrite
- Create the table on first run
Authentication
OAuth sign-in or a key pair, under a role your admin limits.
- SOC 2 Type II
- Zero data retention
- SSO / SAML / RBAC
- Cloud-agnostic
The platform processes your data. An LLM never touches it.
The connector
What the Snowflake connector does
Plan data belongs next to your actuals
Snowflake records what happened. A planning system holds what the business intends: forecasts, allocations and plan versions the model calculates, plus the assumptions planners enter by hand. That data exists nowhere else. Writing it back puts plan next to the actuals it is measured against, governed the same way and ready for every report, model and AI workload that already reads from Snowflake.
Let the warehouse do the filtering
Run your own SQL statement on a warehouse you choose, so you filter, join and aggregate inside Snowflake before anything moves. Nexadata reads only what its role has been granted.
Write back with Append, Upsert, or Overwrite
Append adds the rows on each run. Upsert updates the rows that match a business key you choose and inserts the rest, so a plan restated each cycle updates in place rather than piling up duplicates. Overwrite replaces the table's rows. Nexadata can create the table on the first run and add new columns as your output evolves.
Totals that tie to the cent, and rows you can trace
Amounts land as exact decimals, so totals in Snowflake match the source to the cent. Column names arrive exactly as your team wrote them. Every row is stamped with the ID of the Workflow run that wrote it.
No storage of your own to set up
Results load in bulk through a temporary stage inside Snowflake, so there is no external stage or cloud storage bucket to create, secure or clean up.
Two ways to connect, both under your control
Sign in through a Snowflake OAuth integration your admin creates, so Nexadata acts as you, or connect as a service user with a key pair. Either way, the role your admin grants limits what Nexadata can reach, and credentials are encrypted and stored server-side.
Sources
Connect what feeds it
Snowflake is rarely the only system in a plan. Join it to whatever else the answer needs: if a system has an OpenAPI or OData spec, the Connector Copilot reads it and builds a working connection, with no prebuilt connector to wait on.
How it works
From source system to Snowflake
Connect, transform, map, review. Each step is guided by a no-code copilot, and you approve the plan before anything runs.
- 01
Connect
Connect through a Snowflake OAuth integration or with a key pair, under a role your admin limits to the schemas Nexadata needs. One connection covers reading and write-back.
- 02
Transform
Push filtering and aggregation into the SQL statement, then join, reshape and restate the result in Nexadata by describing it to the Transform Copilot.
- 03
Map
Line warehouse codes up with the dimension members your planning model uses on the way in, and map plan output back to the keys your Snowflake tables expect on the way out.
- 04
Review
Approve the plan before it runs, and keep the record of who changed a mapping group, what changed, how and when.
Use cases
What people run through it
Land plan data back in Snowflake
Write forecasts, allocations and plan versions to a Snowflake table on a schedule, upserting on a business key so each cycle's restatement replaces the last.
Try the round tripFeed planning from curated tables
Read the actuals your data team already curates in Snowflake into the model your plan runs on, without a second copy of the logic in a spreadsheet.
See the use caseLet the warehouse do the heavy lifting
Filter, join and aggregate in a SQL statement on your own warehouse, so only the rows the plan needs leave Snowflake.
Read the guidePartnership
A Snowflake technology partner
Nexadata is a Snowflake technology partner and a member of the Snowflake Partner Network.
See all partnersSet it up
Step-by-step documentation
Every screen, in order, with screenshots.
Setting up a Snowflake connection
Choose OAuth or Key-pair, and run the SQL your admin needs.
Read the guideUsing a Snowflake connection
Read with a SQL statement, then write outputs back.
Read the guideRound trip between Snowflake and Nexadata
Read a fact table, write it back, and confirm the totals tie.
Read the guideTroubleshooting the Snowflake connector
Connection, authorization, dataset and write-back errors.
Read the guideQuestions
Snowflake integration FAQ
- Can Nexadata write data back to Snowflake?
- Yes. Any Workflow output can be written to a Snowflake table with Append, which adds the rows; Upsert, which updates rows matching a business key and inserts the rest; or Overwrite, which replaces the table's rows. Nexadata can create the table on the first run and add new columns as the output changes.
- How does Nexadata read from Snowflake?
- Run your own SQL statement on a warehouse you choose, so filtering and aggregation happen in Snowflake before the data moves.
- How does Nexadata authenticate to Snowflake?
- Two ways. Sign in through a Snowflake OAuth integration your admin creates, so Nexadata acts as you, or connect as a service user with a key pair. Both run under a role your admin limits.
- Does Nexadata need access to my whole account?
- No. Nexadata can do only what its role is granted. A common setup grants read-only access to the source schemas and write access to a separate schema for results.
- Will rerunning a Workflow create duplicate rows?
- Not with Upsert, which updates the rows that match the business key, so the same Workflow run twice leaves the same number of rows. Use Append for data that only ever grows, such as a daily log.
More integrations
Other ways to connect
Pigment
Read from and write to Pigment blocks, views and lists, with column validation on every writeback.
ExploreAnaplan
Reach past your models into Anaplan's own tenant data, and load results back through the actions your model already runs.
ExploreSalesforce
Pull via SOQL or saved reports, tune extract mode for volume, and write back with insert, update, upsert or delete.
ExploreHubSpot
Read any standard or custom object with its associations, and write results back with upsert, create or update.
ExploreDatabricks
Read through an OpenSharing share or a SQL statement, then write results back to Databricks tables with Append or Upsert.
ExploreConnector Copilot
Load a spec, authenticate, describe the data you want, and get a typed dataset. Over 20,000 public APIs are documented in OpenAPI.
ExplorePDF documents
Detect and curate the tables inside a document, then reuse that configuration on every later file in the same layout.
ExploreSpreadsheets
Point at the sheet and the cell where the real data starts, and load a clean typed table out of a messy workbook.
ExploreSee the round trip on your own Snowflake account
Read a table from Snowflake, run it through Nexadata, and write plan data back, with totals that tie to the cent.