> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/activate/data-activations/receiving-data-from-chord-via-snowflake.md).

# Receiving data from Chord via Snowflake

## Overview

If you use Snowflake, receiving data from Chord via a Snowflake listing is an easy and secure way to access your raw and transformed data. Chord will own all the costs of replication and transformation, and customers will be responsible for one yearly maintenance fee to Chord.

## Provide your Snowflake account identifier

To utilize the Snowflake share, you'll need to provide Chord your \*data sharing account identifier. \*To generate your data sharing account identifier run the following in Snowflake:

```pgsql
SELECT CURRENT_ORGANIZATION_NAME() || '.' || CURRENT_ACCOUNT_NAME();
```

Please alert your account manager if this is of interest to you or email <help@chord.co> to get started!

## Accepting a Snowflake listing

Once Chord has established a listing with your Snowflake account, you will need to accept the listing in the Snowflake UI. To access a private listing that was shared with you, do the following:

1. Sign in to Snowsight.
2. In the navigation menu, select **Data sharing** » **External sharing**.
3. On the **Shared with you** page under **Privately shared listings**, select the listing you want to access.
4. Select **Get**.

Note: You must use the `ACCOUNTADMIN` role or another role with the `CREATE DATABASE` and `IMPORT SHARE` privileges to access a listing.


---

# 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.chord.co/activate/data-activations/receiving-data-from-chord-via-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.