> For the complete documentation index, see [llms.txt](https://docs.appmixer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmixer.com/connector-configuration/snowflake.md).

# Snowflake

## Account

You'll need a Snowflake account. If you don't have one, you can sign up for a free trial on the [Snowflake website](https://www.snowflake.com/).

## Obtain Credentials and Configuration

You will need the following details to connect to your Snowflake database:

* **Account Name**: This is often part of your Snowflake URL. You can find it in the Snowflake web interface after logging into your account.
* **Username**: The username of the Snowflake user account you wish to use.
* **Password**: The password for that Snowflake user.
* **Database Name**: The name of the database you want to connect to.
* **Warehouse**: The name of the virtual warehouse to use for running queries.

## How to Find This Information:

* **Account**:
  * Your account identifier is usually part of your Snowflake URL.
  * When you log into Snowflake, the URL looks like `https: //abc12345.us-east-1.snowflakecomputing.com`.
  * Here, `abc12345.us-east-1` is your account identifier.
* **Username and Password**:
  * The credentials you use to log into the Snowflake web interface.
* **Database and Warehouse**:
  * After logging into Snowflake, navigate to the **Databases** and **Warehouses** tabs to see available options.
  * Choose the appropriate database and warehouse for your needs.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.appmixer.com/connector-configuration/snowflake.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.