> For the complete documentation index, see [llms.txt](https://doc.thordata.com/doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.thordata.com/doc/scraping/web-scraper-api/integrations/snowflake-integration.md).

# Snowflake Integration

**Snowflake Integration Feature Description**

With the Snowflake integration feature, you can automatically upload the results of your Web Scraper tasks to a specified system, facilitating data backup, sharing, or further processing and analysis.

**Integration Configuration:**

1. **Integration Name**\
   Customize a name for the integration task for easy management and identification later. It is recommended to name it based on the purpose or scraping target, e.g., “Product Reviews Upload to Snowflake”.
2. **Event Type Settings**\
   You can choose one of the following two ways to trigger data sending according to your needs:

* **Specify Task IDs**\
  Suitable for sending results of known specific scraping tasks to Snowflake.\
  Ideal for handling multiple task IDs results from one scraper tool.\
  Use English commas to separate multiple task IDs.\
  Supports up to 10 task IDs.
* **Follow Task**\
  Automatically upload all subsequent results generated by the scraper tool to Snowflake.\
  Configured once and effective continuously unless manually disabled or deleted.\
  More suitable for continuous scraping or periodic tasks for automated data archiving.

3. **Snowflake Parameter Configuration**\
   Fill in the following information to complete the data upload setup:

<details>

<summary><code>account_identifier</code> <strong>, Account Identifier (Required)</strong></summary>

Typically in the format `<account_name>.<region_id>` or `<org_name>-<account_name>`, used to uniquely identify a Snowflake instance.

</details>

<details>

<summary><code>database</code> <strong>, Database (Required)</strong></summary>

The name of the target database, serving as the logical container for data storage and queries.

</details>

<details>

<summary><code>role</code> <strong>, Role (Required)</strong></summary>

The name of the user's access role in Snowflake, used to define the scope of permissions.

</details>

<details>

<summary><strong><code>user</code> , User (Required)</strong></summary>

The username used to log in to Snowflake.

</details>

<details>

<summary><code>pwd</code> <strong>, Password (Required)</strong></summary>

The user’s password, used for authentication.

</details>

<details>

<summary><code>schema</code> <strong>, Schema (Required)</strong></summary>

A structured namespace within the database used to organize tables, views, and other objects.

</details>

<details>

<summary><code>stage</code> <strong>, Stage (Required)</strong></summary>

The name of the internal stage, which Snowflake uses to temporarily store files.

</details>

<details>

<summary><code>warehouse</code> <strong>, Warehouse (Required)</strong></summary>

Virtual compute resources used to execute SQL queries and data loading tasks.

</details>

<details>

<summary><code>file_type</code> <strong>, File Type (Required)</strong></summary>

Amazon product results can be sent in either JSON or CSV format. YouTube product results can only be sent using the file format.\
Parameter values: `JSON`, `CSV`, `Download Link`

</details>

If you need more assistance, please contact us via email at <support@thordata.com>.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://doc.thordata.com/doc/scraping/web-scraper-api/integrations/snowflake-integration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.