Search Snowflake with SQL

The Search Snowflake with SQL action lets Glean agents run direct, read-only SQL against Snowflake and return the results to downstream steps.

Use this action when you want full control over the SQL being executed while still composing the response in a Glean agent (for example, summarizing the data, sending a message, or updating another system).

Limitations

• The action validates SQL to prevent writes and relies on Snowflake role permissions.

• If no warehouse is provided and the user has no default warehouse, the action fails.

• Missing privileges return authorization or object does not exist errors.

• Snowflake errors surface back to the agent run and this is dependent on Snowflake service health.

Prerequisites

• An admin has enabled and configured the Snowflake Actions action pack in the Glean Admin Console.

• Snowflake role and permissions

  • A Snowflake role, for example, GLEAN_QUERY_SNOWFLAKE_ROLE with at least:

    • USAGE on target databases and schemas.

    • SELECT on the tables or views referenced in your SQL.

    • USAGE on the warehouse used by the action.

• User authentication

  • Users who run this action have authenticated to Snowflake via OAuth from Glean.

Supported parameters

Parameter	Type	Required	Recommended source	Description
Query	String	Yes	Dynamic (user input or step)	Full read-only SQL statement to execute (for example, SELECT COUNT(*) FROM ANALYTICS.CUSTOMERS LIMIT 5).
Warehouse	String	Yes	Fixed in step configuration	Snowflake warehouse to execute the SQL.

Usage example

Scenario: Simple reporting query

Goal: run a fixed report query and present results in the agent response.

Setup in Agent Builder:

• Add a trigger step, for example, an input form with a query in the text field.

• Add the Search Snowflake with SQL action and configure:

  • Query: a fixed SQL statement, for example, SELECT COUNT(*) AS customer_count FROM ANALYTICS.CUSTOMERS.

  • Warehouse: a reporting warehouse your role can use.

• Add a Respond step to display the results as a table or summary.

Resulting behavior:

• The action executes the SQL in Snowflake and returns the result set.

• The Respond step formats or summarizes the output.

Troubleshooting

• Possible cause: The warehouse field is empty, or the role does not have USAGE on the warehouse.
• Fix: Set the warehouse in the action configuration and grant USAGE to the integration role.

• Possible cause: Database, schema, or table names are missing, misspelled, or not visible to the role.
• Fix: Use fully qualified names, for example, DATABASE.SCHEMA.TABLE and grant USAGE/SELECT privileges.

• Possible cause: The Snowflake Actions pack is misconfigured (account identifier mismatch).
• Fix: Copy the account identifier from the Snowflake OAuth URLs into the action pack configuration and re-authenticate.

• Possible cause: The role lacks USAGE/SELECT on referenced objects.
• Fix: Restrict queries to allowed objects or update grants for the integration role.

FAQs

No. The action validates SQL as read-only and uses Snowflake roles scoped for reporting access.

The action uses the warehouse set in the action configuration. If none is set and the user has no default, Snowflake returns an error.

Use Search Snowflake with SQL when you want direct SQL control. Use Search Snowflake with Cortex when you want natural language questions and generated SQL.