> For the complete documentation index, see [llms.txt](https://docs.couchdrop.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.couchdrop.io/integrations/data-analytics-and-bi/snowflake.md).

# Snowflake

Learn about streaming data into snowflake using Couchdrop.

<div align="left"><figure><img src="https://391958821-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FpokYqd27yrOUxIBhyvbF%2Fuploads%2Fg2RFFRdNfvjAb0nWm4Qu%2Fsnowflake.webp?alt=media&amp;token=05ed1f94-6d2f-4b3f-b9e7-03bd6c209cf6" alt=""><figcaption></figcaption></figure></div>

## Overview

Couchdrop can insert data into Snowflake through file actions, allowing you to ingest data from cloud storage, SFTP or FTP servers, APIs, and inbound webhooks into your Snowflake tables.

Rather than maintaining separate file-transfer and ingestion infrastructure, you can use Couchdrop to receive files and pass their contents into Snowflake as part of an Automation. This provides a way to connect existing file-based workflows with your Snowflake data warehouse.

### How Snowflake works with Couchdrop

Snowflake is configured in Couchdrop as a **platform integration**. Unlike storage connections, a Snowflake integration does not appear as a virtual folder because Couchdrop needs information about the destination table and how the incoming data maps to it.

The setup has two parts:

1. Create the Snowflake connection as a system integration in Couchdrop.
2. Use that connection in a file action within an Automation.

When configuring the Snowflake file action, you provide information about the Snowflake table and how the incoming data should be inserted.

## How to connect Snowflake to Couchdrop

{% hint style="warning" %}

#### Before you start

To connect Snowflake to Couchdrop, you will need:

* A Snowflake account with access to the table you want Couchdrop to use
* Your Snowflake Account ID
* A Snowflake programmatic access token
* The name of the destination Snowflake table
* A location or inbound method in Couchdrop that provides the data you want to ingest

Depending on your Snowflake configuration, you may also need the database, schema, warehouse, and role.
{% endhint %}

{% stepper %}
{% step %}

### Create a Snowflake integration

Log in to Couchdrop and add a new system integration.

Select **Snowflake** from the list of available integrations.
{% endstep %}

{% step %}

### Configure the Snowflake connection

Enter the required Snowflake connection details.

<table data-search="false"><thead><tr><th>Setting</th><th>Description</th></tr></thead><tbody><tr><td><strong>Integration name</strong></td><td>A name used to identify the Snowflake connection within Couchdrop.</td></tr><tr><td><strong>Snowflake Account ID</strong></td><td>The Account ID for the Snowflake account Couchdrop will connect to.</td></tr><tr><td><strong>Snowflake Table Name</strong></td><td>The Snowflake table Couchdrop will use for the integration.</td></tr><tr><td><strong>Snowflake Access Token</strong></td><td>The programmatic access token Couchdrop uses to authenticate to Snowflake.</td></tr><tr><td><strong>Snowflake Database</strong></td><td>Optional. Defaults to the <code>DEFAULT_NAMESPACE</code> user property in Snowflake if empty.</td></tr><tr><td><strong>Snowflake Schema</strong></td><td>Optional. Defaults to the <code>DEFAULT_NAMESPACE</code> user property in Snowflake if empty.</td></tr><tr><td><strong>Snowflake Warehouse</strong></td><td>Optional. Defaults to the <code>DEFAULT_WAREHOUSE</code> user property in Snowflake if empty.</td></tr><tr><td><strong>Snowflake Role</strong></td><td>Optional. Defaults to the <code>DEFAULT_ROLE</code> user property in Snowflake if empty.</td></tr></tbody></table>

Click **Add System Integration** and follow the wizard to save the connection.
{% endstep %}

{% step %}

### Use Snowflake in an Automation

Create an Automation or file action and select **Snowflake** as the platform type.

Use the Snowflake connection you created, then configure the file action with the Snowflake table schema and how the incoming data maps to the destination table.
{% endstep %}
{% endstepper %}

{% hint style="success" %}

### Next Steps

Once the Snowflake system integration is connected, you can select it as the platform for a file action within a Couchdrop Automation. The Automation can then use data arriving through the configured Couchdrop inbound method as input for the Snowflake workflow.
{% endhint %}

## Creating a Snowflake programmatic access token

Couchdrop uses a Snowflake programmatic access token to authenticate the connection.

Snowflake can generate a token for a user with:

```
ALTER USER IF EXISTS <example_user>
ADD PROGRAMMATIC ACCESS TOKEN example_token;
```

Snowflake returns the token secret when the token is created. This is the only time the token secret is displayed, so copy and store it securely before closing the result.

{% hint style="info" %}
For a comprehensive guide on generating an access token, see  <https://docs.snowflake.com/en/user-guide/programmatic-access-tokens>&#x20;
{% endhint %}

## Common issues connecting to Snowflake

The network policy setup for your user in Snowflake can block us from authenticating and connecting to your Snowflake account. The authentication policy setup for your user in Snowflake can prevent the network policy from blocking us, if it is an issue, by running

```
CREATE|ALTER AUTHENTICATION POLICY <my_policy_name>
  PAT_POLICY=(
    NETWORK_POLICY_EVALUATION = NOT_REQUIRED
  );
```

The authentication policy can also block us from connecting if the authentication methods have been configured, and do not include `PROGRAMMATIC_ACCESS_TOKEN` in the available authentication methods. To see if this is the case you can run&#x20;

```
DESCRIBE AUTHENTICATION POLICY <authentication_policy_name>;
```

To add the authentication method to your authentication policy, you can run&#x20;

```
ALTER AUTHENTICATION POLICY <authentication_policy_name>
  SET AUTHENTICATION_METHODS = ('PROGRAMMATIC_ACCESS_TOKEN');
```

To generate the programmatic access token

```
ALTER USER IF EXISTS <example_user> ADD PROGRAMMATIC ACCESS TOKEN example_token;
```


---

# 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.couchdrop.io/integrations/data-analytics-and-bi/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.