> For the complete documentation index, see [llms.txt](https://docs.zingg.ai/zingg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zingg.ai/zingg/connect-your-data/connect-cloud-warehouses.md).

# Connect Cloud Warehouses

Connect Zingg to cloud warehouses and analytics databases including Databricks, Snowflake, BigQuery, Redshift, Fabric, and Exasol.

{% hint style="success" icon="right-long" %}
Snowflake on this page means Snowflake as a DATA SOURCE, available in all editions. This is different from Snowflake as a COMPUTE ENGINE, which is Enterprise only and does not require Spark. For the Enterprise native Snowflake run, see [Install Zingg](/zingg/running-zingg/install-zingg.md)
{% endhint %}

Zingg connects to cloud warehouses using the Zingg pipe abstraction.

{% hint style="success" icon="right-long" %}
New to Zingg pipes? Understand how pipes work before configuring them - [Pipes and data connections](/zingg/connect-your-data/pipes-and-data-connections.md)
{% endhint %}

Select your platform from the sub-pages below. Each page shows the Python API and JSON config for that platform, plus the supported file formats. Python and JSON produce identical results, use whichever matches your setup.


---

# 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.zingg.ai/zingg/connect-your-data/connect-cloud-warehouses.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.