A data warehouse built for the cloud
9 actions Leo can use in the apps and agents it builds for you: 3 that read Snowflake data, 6 that create or update it.
Retrieves available options for the Warehouse Name field.
Retrieves available options for the User Name field.
Retrieves available options for the Database field.
Start a Snowflake session and return it in serialized form, so subsequent Snowflake actions can run in the same session (preserving temporary tables, USE context, and session parameters) by passing it to their Session prop. The returned value contains session auth tokens — treat it as sensitive. Sessions expire server-side after ~4 hours or your account's idle timeout.
Insert a row into a table
Insert multiple rows into a table
Execute a custom Snowflake query. See our docs to learn more about working with SQL in Pipedream.
Execute a Snowflake query inside a session started by the Start SQL Session action, so it shares that session's state — temporary tables, USE context, and session parameters — with the other queries in the same session. Pass the serialized session from Start SQL Session to the Session prop. Note: to preserve the session this query runs on a direct connection and therefore does NOT egress from the shared static IP (use_pd_sql_proxy); if your Snowflake network policy allowlists only the static IP, use Execute SQL Query instead. See our docs to learn more about working with SQL in Pipedream.
Execute a SQL Query. See our docs to learn more about working with SQL in Pipedream.
Leo connects Snowflake to the ERP your business already runs on: the records it reads in Snowflake land in your ERP, and what changes in the ERP flows back.
Authorize Snowflake once, in a couple of clicks. Leo only gets the permissions you grant.
In plain language: the dashboard, portal or agent you want across Snowflake and your ERP. No code, no mapping spreadsheets.
Leo builds it, you review, it goes live. Agents run on a schedule or on events, under the guardrails you set.
