Skip to main content
Telara

Integrations / Snowflake

Snowflake logo

Snowflake

Cloud data platform

Basic auth
Indexes
Actions

What Telara does

Capability matrix

Indexes YesTracks spend NoDiscovers shadow AI NoRuns actions YesReal-time events No

Before you connect

Prerequisites

A Snowflake account locator, a warehouse Telara can use, and a user that can run queries.
Prefer a dedicated user. Key-pair is preferred over a password.

Vendor setup

Get the credential

1
Create the login Telara will use
In Snowflake, create a user (and optional role) that can query the objects this tenant should see. Attach a key pair when your org allows it.
2
Note the locator and warehouse
Copy the account locator (not the vanity URL alone), the warehouse name, and the default database name.
3
Paste in Telara
Settings → Integrations → Snowflake. Fill the connection fields Telara shows, then the username/password or key pair.

In Telara

Connect in Telara

Basic auth

In Telara, open Settings → Integrations, choose this connector, and enter the username and password (or key) Telara asks for.

Fields Telara asks for
  • Username
  • Password
  • Account
  • Warehouse
  • Database
  • Schema
  • Role
OAuth 2.0

In Telara, open Settings → Integrations, choose this connector, and click Connect. Telara sends you to the vendor to approve access, then returns you here. You do not create an OAuth app or paste a client secret.

Fields Telara asks for
  • Account
  • Warehouse
  • Database
  • Schema
  • Role
Key pair

In Telara, open Settings → Integrations, choose this connector, and paste the key pair Telara asks for.

Fields Telara asks for
  • Public Key
  • Private key
  • Account
  • Warehouse
  • Database
  • Schema
  • Role

Knowledge

What gets indexed

ResourceCoverage
DatabasePartial — not every record the vendor holds is synced
SchemaPartial — not every record the vendor holds is synced

Sync

Freshness & sync

ResourceLagDeletions
DatabaseUp to 1 dayRemoved records disappear on the next full sync
SchemaUp to 1 dayRemoved records disappear on the next full sync

Data handling

Permissions & data handling

Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.

Excluded from semantic search: Database, Schema.

After connect

Verify it worked

This connector does not declare a credential probe yet. A saved connection means Telara stored the credential, not that the vendor accepted it.

Honesty

Known limitations

The wrong account locator or region looks like a network failure.
A warehouse that is suspended, or a role that cannot use it, connects then returns nothing.