Snowflake
Tables in your Snowflake database, authenticated with your Ingest workspace identity. No stored Snowflake key or password.
Ingest lands typed, deduplicated tables in Snowflake from any API it connects, including Abilene TX 311, Albany NY 311, Ann Arbor MI 311 and Anne Arundel County MD 311. You own the Snowflake account and the credentials; Ingest keeps no copy of the data.
Every destination receives the same layout; see the tables Ingest creates.
Setup
Before you start
You need a Snowflake administrator. No password or private key needed. Copy workspace-specific SQL from the signed-in Ingest panel. Public docs contain an AWS role placeholder. The panel fills your workspace's role. Setup uses ACCOUNTADMIN; Ingest receives only INGEST_ROLE.
1. Get your account identifier
- Run in Snowsight:
SELECT CURRENT_ORGANIZATION_NAME() || '-' || CURRENT_ACCOUNT_NAME();- Paste the result into Account identifier at the bottom.
2. Grant access
- Have your administrator run this. It creates the Service user, Database, Warehouse and Role named at the bottom; to use other names, click Change names there before you copy it. To use a database or warehouse you already have, enter its name there and leave out its CREATE statement. Ingest creates and owns its pipeline schemas.
USE ROLE ACCOUNTADMIN;
CREATE WAREHOUSE IF NOT EXISTS INGEST_WH
WAREHOUSE_SIZE = 'XSMALL' AUTO_SUSPEND = 60
AUTO_RESUME = TRUE INITIALLY_SUSPENDED = TRUE;
CREATE DATABASE IF NOT EXISTS INGEST;
CREATE ROLE IF NOT EXISTS INGEST_ROLE;
GRANT USAGE ON WAREHOUSE INGEST_WH TO ROLE INGEST_ROLE;
GRANT USAGE, CREATE SCHEMA ON DATABASE INGEST TO ROLE INGEST_ROLE;
CREATE USER INGEST_SVC
TYPE = SERVICE
WORKLOAD_IDENTITY = (TYPE = AWS, ARN = '<ingest-role-arn>')
DEFAULT_ROLE = INGEST_ROLE
DEFAULT_WAREHOUSE = INGEST_WH;
GRANT ROLE INGEST_ROLE TO USER INGEST_SVC;- User already exists? Verify its workspace identity and grants before reusing it. The service user must trust this workspace's AWS role. A matching user name alone is not sufficient.
3. Allow the connection
- If a network policy is enabled, allow 184.193.60.160/32 and 44.194.102.221/32.
4. Test the connection
- Click Test & configure at the bottom. Writes and reads temporary data, checks pipeline state, then attempts cleanup. Review any cleanup warning. If the test fails, fix the reported problem and choose Test again.
Staging
needs_staging: none. Parts are uploaded into an internal named stage that belongs to the dataset's own
schema, so nothing passes through an Ingest-owned bucket and no storage credentials are exchanged. The
stage is dropped with the schema.
Writes
Upserts use native MERGE, deduplicating inside the merge so a batch carrying several versions of one row
resolves to the latest rather than failing Snowflake's non-deterministic merge check. A full refresh loads
a shadow table and swaps it in, so readers see the previous contents until the swap commits, never a
half-loaded table.
Every COPY INTO runs with FORCE = TRUE. Snowflake otherwise remembers which files a table has already
loaded and skips them, which would make a retried load land nothing at all.
Conformance
Every adapter passes the same 15-case suite before it ships: a table with every canonical type, append, merge with in-batch duplicates, atomic replace under a concurrent reader, schema evolution, state and schema-version round-trips, count read-back, identifier folding and rollback. Snowflake's badge reflects that suite against a real account, not against a stand-in.
Questions
- Can Ingest load data into Snowflake?
- Yes. Snowflake is live on Ingest's hosted service: the adapter passes all 15 conformance cases against the real service, and the setup steps are on this page.
- Does Ingest merge into Snowflake, or only append?
- Snowflake merges on the resource's primary key, so re-running a sync updates existing rows rather than duplicating them. Append and full replace are available per resource.
- What does Ingest need to connect to Snowflake?
- Account identifier, Service user, Database and Warehouse. Secrets are entered in a form, never in a chat, and held in a secret store under your own path: only the key names ever reach Ingest's database.
- Which sources can Ingest load into Snowflake?
- Every connector Ingest has certified (Abilene TX 311, Albany NY 311, Ann Arbor MI 311, Anne Arundel County MD 311, Anthropic, Asana, Auburn WA 311, Aurora IL 311, Austin TX 311, Baltimore MD 311, Baton Rouge LA 311, Beaumont TX 311, Bellevue WA 311, Bellingham WA 311, Berkeley CA 311, Bethlehem PA 311, Bloomington IN 311, Boca Raton FL 311, Boston MA 311, Bridgeport CT 311, Brockton MA 311, Brookline MA 311, Buffalo NY 311, Burlington VT 311, Cambridge MA 311, Cambridge MA Open Data, Charleston County SC 311, Charlotte NC 311, Chula Vista CA 311, Cincinnati OH 311, Chicago IL 311, New York City NY 311, Clayton County GA 311, Cleveland OH 311, Cobb County GA 311, Columbus OH 311, Corona CA 311, Dallas TX 311, Davenport IA 311, Denver CO 311, Detroit MI 311, Elgin IL 311, Encinitas CA 311, Everett WA 311, Federal Way WA 311, Fort Lauderdale FL 311, Gilbert AZ 311, Google Ad Manager, Google Analytics 4, Greenwich CT 311, Hartford CT 311, Honolulu HI 311, Houston TX 311, Howard County MD 311, Huntington WV 311, Huntsville AL 311, Indianapolis IN 311, Jersey City NJ 311, Jira, Kansas City MO 311, Kent WA 311, Knox County TN 311, Los Angeles CA 311, Lexington KY 311, Lincoln NE 311, LinkedIn Ads, Livonia MI 311, Louisville KY 311, Lubbock TX 311, Macon-Bibb County GA 311, Manchester NH 311, Maui County HI 311, Medford MA 311, Memphis TN 311, Miami FL 311, Miami-Dade County FL 311, Minneapolis MN 311, Montgomery County MD 311, Multnomah County OR 311, Naperville IL 311, Nashua NH 311, Nashville TN 311, Newark NJ 311, NOAA, New Orleans LA 311, Norfolk VA 311, Oakland CA 311, Omaha NE 311, Open Brewery DB, Paterson NJ 311, Peoria IL 311, Philadelphia PA 311, Pinellas County FL 311, Pittsburgh PA 311, PokéAPI, Portland ME 311, PostgreSQL, Prince George's County MD 311, Provo UT 311, Raleigh NC 311, Ramp, Renton WA 311, The Rick and Morty API, Sacramento CA 311, Salesforce, San Antonio TX 311, San Francisco CA 311, San Gabriel CA 311, San Jose CA 311, San Mateo County CA 311, San Rafael CA 311, Santa Fe NM 311, Scottsdale AZ 311, Seattle WA 311, Shopify, Somerville MA 311, Springfield MO 311, St. Petersburg FL 311, Tacoma WA 311, Toledo OH 311, Topeka KS 311, Vallejo CA 311, Washington DC 311, Wayne County MI 311, West Des Moines IA 311, Wichita KS 311, Worcester MA 311 and Youngstown OH 311), plus any API it authors on request. The data lands in a destination you own, under credentials you control. Ingest keeps no copy of it.
What can land here, and where else it can go
Sources certified against a real API today: Abilene TX 311, Albany NY 311, Ann Arbor MI 311, Anne Arundel County MD 311, Anthropic, Asana, Auburn WA 311, Aurora IL 311, Austin TX 311, Baltimore MD 311, Baton Rouge LA 311, Beaumont TX 311, Bellevue WA 311, Bellingham WA 311, Berkeley CA 311, Bethlehem PA 311, Bloomington IN 311, Boca Raton FL 311, Boston MA 311, Bridgeport CT 311, Brockton MA 311, Brookline MA 311, Buffalo NY 311, Burlington VT 311, Cambridge MA 311, Cambridge MA Open Data, Charleston County SC 311, Charlotte NC 311, Chula Vista CA 311, Cincinnati OH 311, Chicago IL 311, New York City NY 311, Clayton County GA 311, Cleveland OH 311, Cobb County GA 311, Columbus OH 311, Corona CA 311, Dallas TX 311, Davenport IA 311, Denver CO 311, Detroit MI 311, Elgin IL 311, Encinitas CA 311, Everett WA 311, Federal Way WA 311, Fort Lauderdale FL 311, Gilbert AZ 311, Google Ad Manager, Google Analytics 4, Greenwich CT 311, Hartford CT 311, Honolulu HI 311, Houston TX 311, Howard County MD 311, Huntington WV 311, Huntsville AL 311, Indianapolis IN 311, Jersey City NJ 311, Jira, Kansas City MO 311, Kent WA 311, Knox County TN 311, Los Angeles CA 311, Lexington KY 311, Lincoln NE 311, LinkedIn Ads, Livonia MI 311, Louisville KY 311, Lubbock TX 311, Macon-Bibb County GA 311, Manchester NH 311, Maui County HI 311, Medford MA 311, Memphis TN 311, Miami FL 311, Miami-Dade County FL 311, Minneapolis MN 311, Montgomery County MD 311, Multnomah County OR 311, Naperville IL 311, Nashua NH 311, Nashville TN 311, Newark NJ 311, NOAA, New Orleans LA 311, Norfolk VA 311, Oakland CA 311, Omaha NE 311, Open Brewery DB, Paterson NJ 311, Peoria IL 311, Philadelphia PA 311, Pinellas County FL 311, Pittsburgh PA 311, PokéAPI, Portland ME 311, PostgreSQL, Prince George's County MD 311, Provo UT 311, Raleigh NC 311, Ramp, Renton WA 311, The Rick and Morty API, Sacramento CA 311, Salesforce, San Antonio TX 311, San Francisco CA 311, San Gabriel CA 311, San Jose CA 311, San Mateo County CA 311, San Rafael CA 311, Santa Fe NM 311, Scottsdale AZ 311, Seattle WA 311, Shopify, Somerville MA 311, Springfield MO 311, St. Petersburg FL 311, Tacoma WA 311, Toledo OH 311, Topeka KS 311, Vallejo CA 311, Washington DC 311, Wayne County MI 311, West Des Moines IA 311, Wichita KS 311, Worcester MA 311, Youngstown OH 311.
Other destinations Ingest writes to: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL.