Snowflake Workflows

Documentation Index

Fetch the complete documentation index at: https://docs.duvo.ai/llms.txt

Use this file to discover all available pages before exploring further.

​

Why Use Snowflake with Duvo?

• Deliver scheduled KPI summaries before your team’s Monday standup
• Get a Slack alert the moment inventory falls below a reorder threshold
• Pull a fresh data extract into Google Sheets for a stakeholder who needs it in minutes
• Monitor for anomalies across large datasets and escalate exceptions automatically

​

Before You Start

• Snowflake connection — follow the Snowflake connection guide to configure key-pair authentication and add the connection on the Connections page
• Slack connection (optional) — for threshold alerts and summaries. Click Enable on the Connections page and authorize with your Slack workspace
• Gmail or Outlook connection (optional) — for email distribution of reports
• Google Sheets connection (optional) — for writing query results to a spreadsheet

​

Use Case 1: Scheduled KPI Report from Warehouse Data

​

Step 1: Create Your Assignment

1. Click ”+ Create Assignment” from your dashboard
2. Select “Use Assignment Builder”

​

Step 2: Paste This SOP

Every Monday at 7:00 AM, generate a weekly business metrics summary.

Step 1: Query Snowflake for last week's metrics (Monday–Sunday).

Run these queries and collect the results:
- Total revenue: SELECT SUM(order_total) FROM orders WHERE order_date BETWEEN [last Monday] AND [last Sunday] AND status = 'completed'
- Order count: SELECT COUNT(*) FROM orders WHERE order_date BETWEEN [last Monday] AND [last Sunday]
- Average order value: calculate from the above
- Exception count (failed or refunded orders): SELECT COUNT(*) FROM orders WHERE order_date BETWEEN [last Monday] AND [last Sunday] AND status IN ('failed', 'refunded')

Step 2: Compare to the prior week by running the same queries for the previous Monday–Sunday period.

Step 3: Calculate week-over-week change as a percentage for each metric.

Step 4: Format a short summary message:
"Weekly Metrics — [date range]
- Revenue: $[value] ([+/-X%] vs prior week)
- Orders: [count] ([+/-X%])
- Avg order value: $[value] ([+/-X%])
- Exceptions: [count] ([+/-X%])

[If exceptions increased more than 20%, add: 'WARNING: Exception rate up — check the Orders table for details.']"

Step 5: Post the message to the #data-ops Slack channel.

​

Step 3: Connect Required Integrations

• Snowflake — required
• Slack — for posting the summary (or substitute Gmail/Outlook for email delivery)

​

Step 4: Schedule the Assignment

1. Go to Assignment Settings > Triggers
2. Select Schedule
3. Set to Weekly on Monday at 7:00 AM in your timezone

​

Expected Results

• A Slack summary appears in your channel before your Monday standup
• Week-over-week comparisons show at a glance whether things are trending better or worse
• Anomaly flags are surfaced automatically so the team knows when to dig deeper
• No one needs to open Snowflake or write a query to get the numbers

​

Use Case 2: Threshold Alert When a Metric Breaches a Limit

​

Step 1: Identify Your Threshold Condition

• Which table and column holds the metric you want to watch (e.g., inventory.quantity_on_hand)
• What value triggers an alert (e.g., less than 100 units, more than 5% error rate)
• What context to include in the alert (e.g., which SKU, which region, current value, historical average)

​

Step 2: Paste This SOP

Every hour, check for inventory levels that require attention.

Step 1: Run this query in Snowflake:
SELECT sku, product_name, quantity_on_hand, reorder_point, warehouse_location
FROM inventory.stock_levels
WHERE quantity_on_hand < reorder_point
ORDER BY quantity_on_hand ASC

Step 2: If the query returns no rows, stop — no action needed.

Step 3: If any rows are returned:
- For each row, format a line: "• [product_name] (SKU [sku]) — [quantity_on_hand] units remaining at [warehouse_location] (reorder point: [reorder_point])"
- Assemble a Slack message:
  "Inventory Alert — [count] SKUs below reorder point:
  [lines from above]

  Action: Check your replenishment queue or place restock orders."

Step 4: Post the message to the #supply-chain Slack channel.
Step 5: Do not send a duplicate alert if the same SKUs were already alerted in the last 4 hours.

​

Step 3: Connect Required Integrations

• Snowflake — required
• Slack — for posting the alert

​

Step 4: Schedule the Assignment

1. Go to Assignment Settings > Triggers
2. Select Schedule
3. Set to Every hour (or every 15 minutes for time-critical metrics)

​

Expected Results

• Alerts fire only when a threshold is actually breached — no noise when things are fine
• Each alert names the specific SKUs or records requiring attention
• Your team can act immediately instead of learning about the problem in a weekly report
• The deduplication instruction prevents the same alert from firing repeatedly before anyone has had a chance to act

​

Use Case 3: Export Query Results to Google Sheets

​

Step 1: Create Your Assignment

1. Click ”+ Create Assignment” from your dashboard
2. Select “Use Assignment Builder”

​

Step 2: Paste This SOP

When started, export a fresh customer account list from Snowflake to Google Sheets.

Step 1: Run this query in Snowflake:
SELECT
  account_id,
  account_name,
  industry,
  annual_revenue,
  country,
  account_owner,
  created_date,
  last_activity_date
FROM crm.accounts
WHERE status = 'active'
ORDER BY annual_revenue DESC

Step 2: Write the results to the "Customer Accounts" Google Sheet:
- Use the first sheet ("Sheet1")
- Clear the existing content from row 2 downward (preserve the header row)
- Write the query results starting from row 2, with one row per account
- Use these column headers (already in row 1): Account ID, Account Name, Industry, Annual Revenue, Country, Account Owner, Created, Last Activity

Step 3: Add a note at the top of the sheet (cell A1 comment or a dedicated "last updated" cell):
"Last refreshed: [current date and time] — [row count] accounts"

​

Step 3: Connect Required Integrations

• Snowflake — required
• Google Sheets — for writing results

​

Step 4: Run On Demand or Schedule It

• On demand: click Start Work whenever you need a fresh pull
• Scheduled: set a daily or weekly trigger under Assignment Settings > Triggers if the sheet needs to stay current automatically

​

Expected Results

• The Google Sheet is populated with fresh data each time the assignment runs
• Stakeholders can filter, sort, and share the sheet without touching Snowflake
• The “last refreshed” cell makes it clear how current the data is
• Large result sets are handled automatically — when results are too large to return inline, they may be provided as a CSV that the assignment can upload directly to the sheet

​

Tips for Better Results

​

Troubleshooting

​

Assignment cannot connect to Snowflake

• Re-open the Snowflake connection on the Connections page and verify the account identifier, username, warehouse, database, schema, and role
• Check that the RSA public key is still registered in Snowflake under ALTER USER ... SET RSA_PUBLIC_KEY = '...'
• Confirm the Snowflake user’s role has USAGE on the warehouse and SELECT on the target tables

​

Queries are returning no rows unexpectedly

• Run the same query manually in Snowflake’s worksheet UI to confirm the result
• Check that the warehouse is not suspended — if it cannot auto-resume (or resume is slow), queries may fail or time out rather than return results
• Verify that the date range in the SOP is computing correctly; add a line asking the assignment to log the computed date range before querying

​

Report numbers look wrong

• Check for timezone differences: Snowflake stores timestamps in UTC by default. If your SOP says “last week” without specifying a timezone, add one (e.g., “last Monday to last Sunday, US Eastern time”)
• Look for duplicate rows: if your table has one row per event and the query isn’t aggregating correctly, add SELECT DISTINCT or a GROUP BY
• Confirm the Snowflake role can see all the rows you expect — row-level security policies can silently filter results

​

Large result sets are not appearing in Google Sheets

• When results are too large to return inline, they may be provided as a CSV file. The assignment can upload the CSV directly to Google Sheets — update your SOP to say: “If the query result is a CSV file, upload it to the Google Sheet”

​

Scheduled Jobs are not running

• Confirm the trigger is set to Active under Assignment Settings > Triggers
• Check the assignment’s Job history to see whether previous scheduled Jobs succeeded or failed
• If Jobs are failing, open the failed Job and read the run log to identify the error

​

Related Resources

• Snowflake Connection
• Scheduling Assignments
• Event-Driven Triggers
• Google Sheets Connection
• Slack Connection
• Human-in-the-Loop
• Files