Cortex Search
snowflake.cortex_search
ActionDatabases & warehousesconnection required
Calls the Snowflake REST / SQL API with the connection's bearer token.
Query a Cortex Search service.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- Bearer token
- Providers
- Snowflake
- Secret shape
- the token, or {"token": "…"}
- Config it needs
- account, warehouse, database, schema, role, token_type
- Resolved by
- config.connection_id, else node.connection_id
Configuration
6 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
database Database (defaults to the connection's). | string | No | — | — | — |
schema Schema (defaults to the connection's). | string | No | — | — | — |
name Cortex Search service name. | string | Yes | — | — | — |
query Search query. | string | Yes | — | — | — |
columns Columns to return (JSON array). | array | No | — | array of string | — |
limit How many results one call returns; blank uses Snowflake's own default. | number | No | — | ≥ 1 | — |
Output
One shape.
result
The provider's response object, as returned.
Extra keys beyond the ones listed can appear.
{}See Cortex Search run in a workflow.
In a technical demo we add the Snowflake connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.