Short answer: Drop the "Snowflake → Snowflake Execute SQL" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
SQL Statement statement | string | Required | SQL Statement. e.g. "SELECT * FROM my_table LIMIT 10" |
{"statement": "SELECT * FROM my_table LIMIT 10"}
{"data": [[1,"John","john@example.com"]],"statementHandle": "stmt123","resultSetMetaData": {"numRows": 1,"rowType": [{"name": "ID"},{"name": "NAME"},{"name": "EMAIL"}]}}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.