> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/destinations/categories/database.md).

# Data warehouses

- [BigQuery](https://docs.coupler.io/destinations/categories/database/big_query.md): Send data to BigQuery with automatic schema detection and append mode via Coupler.io.
- [How to generate a BigQuery schema to define column types manually?](https://docs.coupler.io/destinations/categories/database/big_query/how-to-generate-bigquery-schema-to-define-column-types-manually.md)
- [PostgreSQL](https://docs.coupler.io/destinations/categories/database/postgresql.md): Send data to PostgreSQL with Coupler.io for SQL-native analysis, type enforcement, and direct querying without exports.
- [Redshift](https://docs.coupler.io/destinations/categories/database/redshift.md): Send data to Amazon Redshift automatically with Coupler.io. Centralize analytics data from any source without ETL scripting or manual exports.
- [Snowflake](https://docs.coupler.io/destinations/categories/database/snowflake.md): Send data to Snowflake with Coupler.io. Centralize multi-source data in a cloud data warehouse with automatic type detection and SQL-native analytics.
- [Connection Setup](https://docs.coupler.io/destinations/categories/database/snowflake/connection-setup.md): How to setup Coupler.io to Snowflake connection using different types of authentication
- [Supabase](https://docs.coupler.io/destinations/categories/database/supabase.md)


---

# 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.coupler.io/destinations/categories/database.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.