OtherReal-timeUpdated May 2026

Snowflake

Snowflake cloud data warehouse

Snowflake is the cloud data warehouse — petabyte-scale SQL with auto-scaling compute, used by enterprise data teams for analytics, ML training data, and data lakes. Tiny Command exposes one action, no triggers (Snowflake supports streams and tasks for change-driven workflows; for HTTP-trigger-style automation, schedule periodic queries): Execute SQL Query (run a SQL statement against Snowflake; returns the result rows). The connection uses Snowflake credentials (account + user + password or key-pair auth). For workflows that need to pull data from Snowflake (nightly KPI digest, BI report generation, data-export workflows), this is the integration. Snowflake queries can be expensive (compute is billed per-second); design queries efficiently and use result caching where possible. For real-time query workloads, Tinybird/ClickHouse alternatives serve sub-second; Snowflake is batch-friendly.

Connect Snowflake

0triggers

1action

≈ 2 minto set up

Freetier · no card

Actions

Do anything Snowflake can do, from a workflow.

Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.

Action	What it does	Inputs
Snowflake Execute SQL	Executes a SQL query against Snowflake. Compute cost = warehouse-size × runtime, so tight queries on partitioned columns save real money. For nightly KPI rollups or for ad-hoc BI reports.	1 fields	View →

Recipes

Pre-built Snowflake workflows.

Clone any recipe and customize it in one click. Every recipe is fully editable.

Snowflake → Slack alerts

AI-triage every Snowflake event, ping the right channel only when it matters.

Snowflake → Google Sheets log

Every event matching a filter, appended to a running spreadsheet.

Snowflake → Notion database

Turn Snowflake into a Notion-backed source of truth, auto-tagged.

Before you build

Three things worth knowing.

Filter at the trigger

Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.

Authorize once, reuse anywhere

Connect Snowflake once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.

No JSON to read

Every Snowflake field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.

FAQ

Questions about the Snowflake integration.

If we missed yours, ping support. We usually reply within an hour.

How do I connect Snowflake to Tiny Command?

Open the Tiny Command workflow builder, drop in a Snowflake node, and click Connect. Authorize Snowflake once and any workflow on your account can use its triggers and actions. Most teams finish the connection in under two minutes.

What Snowflake triggers does Tiny Command support?

Tiny Command focuses on outbound actions for Snowflake today. Use Tiny Command's universal Webhook or Schedule trigger to start Snowflake workflows, then run any Snowflake action you need.

What Snowflake actions can I run from a workflow?

1 Snowflake action are available out of the box, covering other operations like "Snowflake Execute SQL". Every action accepts dynamic inputs from upstream nodes, whether that's a search result, an AI output, or a form field.

Is the Snowflake integration real-time?

Snowflake actions execute synchronously inside your workflow. Tiny Command waits for Snowflake's API to confirm before continuing to the next step, so downstream nodes can rely on the result.

Do I need to write code to use Snowflake with Tiny Command?

No. Every Snowflake trigger and action is fully configurable from the visual workflow builder. For edge cases that aren't covered, drop in a custom HTTP node and call any Snowflake API endpoint directly.

How much does the Snowflake integration cost?

There's a free tier you can start on without a credit card. Higher run volumes and team features come with paid plans. The Snowflake integration itself has no per-app surcharge.