CommunityHire an ExpertSign Up
Data SourcesSnowflake
Data Sources

Snowflake

Use Snowflake as a data source for your Softr app or dashboard.

Snowflake is a cloud data platform that stores and queries large analytical datasets. Connecting it to Softr lets you build dashboards, reports and internal tools on top of warehouse data, without exporting it anywhere first.

You connect Snowflake once at the workspace level, then point individual blocks at the tables you want to show.

Before you start

Have these ready from your Snowflake account:

  • Your account identifier, in orgname-account_name form — for example myorg-myaccount. To find it in Snowsight, open the account selector and choose View account details. See Snowflake’s account identifiers reference if yours is in the older account-locator format.
  • The user Softr should authenticate as.
  • A programmatic access token for that user. In Snowsight, go to Governance & security → Users & roles, select the user, open Programmatic access tokens and choose Generate new token. Tokens expire after a maximum of 365 days, and your admin may have shortened that with an authentication policy.
  • A network policy that permits the connection. Snowflake requires one to use a token, and requires one up front for service users. Your Snowflake admin can attach it to the account or to the single user — see network policy requirements.

Connect Snowflake to Softr

Open Integrations

In the Softr dashboard, select Integrations in the left sidebar, then click Connect new.

The Softr dashboard Integrations page with the Connect new button highlighted

The Integrations page, where all external data sources are managed.

Choose Snowflake

Pick Snowflake from the Select an integration list.

The Select an integration dialog with the Snowflake tile outlined in red

Snowflake in the integration picker.

Enter your connection details

Fill in the connection form:

FieldRequiredWhat to enter
NameYesA label for this connection inside Softr.
Account identifierYesYour Snowflake account, in orgname-account_name form.
WarehouseNoThe warehouse to run queries against.
RoleNoThe role Softr should assume.
DatabaseNoThe database to scope the connection to.
UserYesThe Snowflake user Softr authenticates as.
Programmatic access tokenYesThe token you generated in Snowsight.

Leaving Warehouse, Role and Database empty uses the defaults configured for the user in Snowflake.

The Connect to Snowflake dialog with the User and Programmatic access token fields outlined in red

The Snowflake connection form. User and Programmatic access token are both required.

Connect

Click Connect. The button stays disabled until every required field is filled. Once the connection succeeds, Snowflake appears in your Integrations list and is available to blocks across your apps.

Show Snowflake data in your app

Point a block at a Snowflake table

Add a dynamic block — a List, Table or Chart — then open its Block source tab and select your Snowflake connection. Choose the database, schema and table you want to display.

Map fields

Choose which Snowflake columns map to which fields in the block, the same way you would for any other data source. See Visualize data with building blocks for the mapping options each block type offers.

Troubleshooting

Authentication fails with a valid token

The usual cause is a missing network policy. Snowflake requires one before a programmatic access token can be used, and requires one up front for service users. Ask your Snowflake admin to confirm a policy is attached to the account or to the user Softr connects as.

Also check the token has not expired — 365 days is the maximum, and an authentication policy can shorten it.

The connection succeeds but no tables appear

If you left Warehouse, Role or Database empty, Softr falls back to the user’s defaults in Snowflake. If that user has no default warehouse or role, set them explicitly on the connection.

The account identifier is rejected

Softr expects the orgname-account_name form, not the legacy account locator and not a full URL. Open the account selector in Snowsight and choose View account details to read the current identifier.

Use these docs with your AI tools

An AI agent can read this documentation directly. You do not need an account or an API key. Everything here is public and read-only.

Query these docs via MCP

Recommended

Add this server to Claude, Claude Code, Cursor, Mistral, or any tool that supports MCP. Your agent can then search Softr Documentation documentation and read it in full, instead of answering from memory.

https://docs.softr.io/mcp
  • searchFind the passages that answer a question.
  • fetchRead one page in full, as Markdown.
  • list_pagesSee every page in this documentation.

Query these docs over HTTP

The same tools also work as plain web requests. Use this for scripts, or for any tool that does not support MCP. There is one endpoint per tool. Arguments go in the query string, and the answer comes back as JSON.

https://docs.softr.io/api/docs/search?query=custom+domain

Read the OpenAPI description. It is built from the same definitions as the tools, so it always matches what the endpoints do.

Read these docs as Markdown

Add .md to any page URL to get its Markdown source. You can also send the headerAccept: text/markdown to the page URL itself.

To read the whole documentation in one file, open llms-full.txt. For a short index of every page, open llms.txt.