Input node
Snowflake input
Read a table or SQL query from Snowflake. Picking a table shows its columns without a run, and without waking a warehouse.
What it does
Runs a query in Snowflake through a saved Connection and streams the result into the pipeline. Pick a table with the live schema and table browser, or write your own SQL. Picking a table shows its columns in the builder WITHOUT a run: Snowflake answers that from its metadata layer, so it needs no running warehouse and costs nothing. Credentials live on the Connection.
Inputs and outputs
| Inputs | None. This node starts a pipeline. |
| Outputs | One. |
When to use it
- Pull a warehouse table or a curated query into a pipeline
- Push filtering and aggregation down to Snowflake so less data crosses the wire
- Blend warehouse data with files, databases or an API in one flow
Examples
Whole table
PUBLIC.EVENTS
Columns appear immediately, with no warehouse running.
Your own SQL
SELECT id, total FROM PUBLIC.ORDERS WHERE created_at >= '2026-01-01'
Aggregate in the warehouse
SELECT region, SUM(total) FROM PUBLIC.ORDERS GROUP BY region
Tips
- Press ⤢ beside SQL query for the SQL Studio: a full-screen editor that browses the connection's schemas, tables and columns and runs your query with Run to here without closing.
- A typed query wins over a picked table when both are filled in.
- A typed query's columns only appear after a Test run: the warehouse has no way to describe a query without executing it, and executing one would resume (and bill for) a warehouse just because you opened this panel.
- The Connection needs a warehouse before anything actually runs. Browsing and reading a table's columns don't.
- Results arrive in pages of up to 10,000 rows, fetched in order. That's the API's own limit, not a setting.