Snowflake is a cloud-based data warehouse offering elastic scaling, secure data sharing, and SQL analytics across multiple cloud environments
Snowflake is a cloud-based data warehouse offering elastic scaling, secure data sharing, and SQL analytics across multiple cloud environments On Nagent, Snowflake is exposed as a fully-configurable databases integration that any agent can call — 15 actions, and OAuth authentication. No code is required to wire Snowflake into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Snowflake to automate the kinds of tasks databases teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Snowflake into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Snowflake, with input parameters and output schema. Drop these into any step of an agent built in Helix.
SNOWFLAKE_CANCEL_STATEMENT_EXECUTIONCancels the execution of a running SQL statement. Use this action to stop a long-running query.
Input parameters
Unique ID (a UUID) of the API request. This is an optional parameter that can be used to track the request.
The handle of the statement to be cancelled. This can be obtained from the response of the execute_statement action.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SNOWFLAKE_CHECK_STATEMENT_STATUSRetrieves the status and results of a previously submitted SQL statement using its statement handle. Use this to poll async queries submitted via SNOWFLAKE_SUBMIT_SQL_STATEMENT; call repeatedly until status is no longer pending. Use SNOWFLAKE_CANCEL_STATEMENT to abort a hanging query.
Input parameters
The partition number to return. The size of each partition is determined by Snowflake.
Unique ID (UUID) of the API request for idempotency.
The handle of the statement to be checked.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SNOWFLAKE_EXECUTE_SQLExecute SQL statements in Snowflake and retrieve results. Supports SELECT queries for data retrieval, DDL statements (CREATE, ALTER, DROP) for schema management, and DML statements (INSERT, UPDATE, DELETE) for data modification. Returns comprehensive result metadata including column types, row counts, and execution status. Unquoted SQL identifiers are auto-uppercased by Snowflake — use matching case in `database`, `schema_name`, `warehouse`, and `role` parameters to avoid 'object not found' errors. Always apply explicit time-range filters and a LIMIT clause to unbounded SELECT queries to prevent large, slow result sets.
Input parameters
Role name to use for execution (case-sensitive). If not specified, uses the user's DEFAULT_ROLE setting.
Execution timeout in seconds. Set to 0 for maximum timeout (604800 seconds). If not specified, uses the default timeout.
Values of bind variables in the SQL statement. Use this for parameterized queries to prevent SQL injection.
Database name to use for execution (case-sensitive). If not specified, uses the user's DEFAULT_NAMESPACE setting.
SQL statement(s) to execute. Supports SELECT queries, DDL (CREATE, ALTER, DROP), and DML (INSERT, UPDATE, DELETE). Multiple statements can be separated by semicolons; they will be executed in sequence automatically. When querying INFORMATION_SCHEMA, always filter on both `table_schema` and `table_catalog` and wrap mixed AND/OR conditions in parentheses. For multi-statement batches, test critical sections in isolation first — a single failing statement obscures root cause.
Warehouse name to use for query execution (case-sensitive). Required for queries that need compute resources. If not specified, uses the user's DEFAULT_WAREHOUSE setting. Suspended or undersized warehouses cause high latency or timeouts; verify the warehouse is active and appropriately sized before execution.
Session parameters to set for the statement execution. These are Snowflake session-level parameters.
Schema name to use for execution (case-sensitive). If not specified, uses the user's DEFAULT_NAMESPACE setting.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SNOWFLAKE_FETCH_CATALOG_INTEGRATIONRetrieves detailed configuration and metadata for a specific catalog integration. Catalog integrations allow Snowflake to connect to external Apache Iceberg catalogs (AWS Glue, Snowflake Open Catalog/Polaris, or Apache Iceberg REST catalogs) to query Iceberg tables managed by those external systems.
Input parameters
The name (identifier) of the catalog integration to fetch details for. This is case-sensitive.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SNOWFLAKE_GET_ACTIVE_SCHEDULED_MAINTENANCESRetrieves a list of any active scheduled maintenances currently in the In Progress or Verifying state.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SNOWFLAKE_GET_ALL_SCHEDULED_MAINTENANCESRetrieves a list of the 50 most recent scheduled maintenances, including those in the Completed state.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SNOWFLAKE_GET_COMPONENT_STATUSRetrieves the status of individual components, each listed with its current status.
Input parameters
Limit number of components returned.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SNOWFLAKE_GET_STATUS_ROLLUPRetrieves the status rollup for the entire page, including indicators and human-readable descriptions of the blended component status.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SNOWFLAKE_GET_STATUS_SUMMARYRetrieves the current status summary from Snowflake's public status page (status.snowflake.com). Returns overall system status, operational status of all regional components (AWS, Azure, GCP regions), any unresolved incidents, and upcoming or in-progress scheduled maintenances. This is a public endpoint that provides global Snowflake service status, not account-specific information.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SNOWFLAKE_GET_UNRESOLVED_INCIDENTSRetrieves a list of any unresolved incidents from the Snowflake status page. This endpoint returns incidents currently in the Investigating, Identified, or Monitoring state. Returns an empty list if there are no active incidents. This is a public status page API that does not require authentication.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SNOWFLAKE_GET_UPCOMING_SCHEDULED_MAINTENANCESRetrieves upcoming scheduled maintenances from Snowflake's public status page. This action queries the Snowflake status API to get a list of any scheduled maintenance events that are still in the 'Scheduled' state (not yet started or completed). The response includes maintenance details such as impact level, scheduled time windows, incident updates, and direct links to the maintenance notices. Note: This uses Snowflake's public status API and does not require authentication.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SNOWFLAKE_SHOW_DATABASESLists all databases for which you have access privileges. Shows database metadata including name, creation date, owner, retention time, and more. Can filter results and include dropped databases within Time Travel retention period.
Input parameters
Role to use when executing the statement.
Maximum number of rows to return. Cannot exceed 10000.
If true, returns only a subset of output columns (created_on, name, kind, database_name, schema_name).
If true, includes dropped databases that are still within Time Travel retention period.
Timeout in seconds for statement execution.
Used with LIMIT for pagination. Returns results starting from databases whose names match this string.
Warehouse to use for the query (though SHOW DATABASES doesn't require a running warehouse).
Filters results by databases whose names start with this string. Case-sensitive.
Filters results by database name using SQL wildcard pattern (% and _). Case-insensitive.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SNOWFLAKE_SHOW_SCHEMASLists all schemas for which you have access privileges. Shows schema metadata including name, creation date, owner, database, retention time, and more. Can filter results and include dropped schemas within Time Travel retention period.
Input parameters
Role to use when executing the statement.
Maximum number of rows to return. Cannot exceed 10000.
If true, returns only a subset of output columns (created_on, name, kind, database_name, schema_name).
If true, includes dropped schemas that are still within Time Travel retention period.
Timeout in seconds for statement execution.
Database context for the query.
Scope for the command. Options: 'ACCOUNT', 'DATABASE', or a specific database name.
Used with LIMIT for pagination. Returns results starting from schemas whose names match this string.
Warehouse to use for the query (though SHOW SCHEMAS doesn't require a running warehouse).
Filters results by schemas whose names start with this string. Case-sensitive.
Filters results by schema name using SQL wildcard pattern (% and _). Case-insensitive.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SNOWFLAKE_SHOW_TABLESLists all tables for which you have access privileges. Shows table metadata including name, creation date, owner, database, schema, row count, size in bytes, clustering keys, and more. Can filter results and include dropped tables within Time Travel retention period.
Input parameters
Role to use when executing the statement.
Maximum number of rows to return. Cannot exceed 10000.
If true, returns only a subset of output columns (created_on, name, kind, database_name, schema_name).
Schema context for the query.
If true, includes dropped tables that are still within Time Travel retention period.
Timeout in seconds for statement execution.
Database context for the query.
Scope for the command. Options: 'ACCOUNT', 'DATABASE', 'SCHEMA', or specific database/schema names.
Used with LIMIT for pagination. Returns results starting from tables whose names match this string.
Warehouse to use for the query (though SHOW TABLES doesn't require a running warehouse).
Filters results by tables whose names start with this string. Case-sensitive.
Filters results by table name using SQL wildcard pattern (% and _). Case-insensitive.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SNOWFLAKE_SUBMIT_SQL_STATEMENTDEPRECATED: Use ExecuteSql instead. Submits a SQL statement for execution. Execution is asynchronous; monitor status with SNOWFLAKE_CHECK_STATEMENT_STATUS for long-running queries.
Input parameters
Role to use when executing the statement. The value in this field is case-sensitive. If you omit this field, the SQL API uses the value of the DEFAULT_ROLE property of the user.
Schema in which the statement should be executed. The value in this field is case-sensitive. If you omit this field, the SQL API uses the schema from the value of the DEFAULT_NAMESPACE property of the user.
Timeout in seconds for statement execution. If the execution of a statement takes longer than the specified timeout, the execution is automatically canceled. To set the timeout to the maximum value (604800 seconds), set timeout to 0. If this field is not set, the timeout specified by the STATEMENT_TIMEOUT_IN_SECONDS parameter is used.
Values of bind variables in the SQL statement. When executing the statement, Snowflake replaces placeholders ( ? and :name) in the statement with these specified values.
Database in which the statement should be executed. The value in this field is case-sensitive. If you omit this field, the SQL API uses the database from the value of the DEFAULT_NAMESPACE property of the user.
The SQL statement to execute. Unquoted identifiers are automatically uppercased by Snowflake; quote identifiers to preserve case. When querying INFORMATION_SCHEMA views, filter by both table_schema and table_catalog to avoid results from unintended databases or schemas.
Warehouse to use when executing the statement. The value in this field is case-sensitive. If you omit this field, the SQL API uses the value of the DEFAULT_WAREHOUSE property of the user.
Session parameters that you want to set for this request.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 30 agents privately built on Nagent that already use Snowflake.
Build on Nagent
Connect Snowflake to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Snowflake, and click "Connect Now." You'll authenticate with OAuth — Nagent handles credential storage and refresh automatically. Once connected, Snowflake is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Snowflake is connected, you configure its 15 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Snowflake steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Snowflake event fires, the agent kicks off automatically.
Every Snowflake action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Snowflake ships with 15 pre-built databases actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Snowflake together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Snowflake-based workflows tailored to your business.